Disinformation & The Murder Of Michael Hastings

At around 4:25 am on the morning of Tuesday, June 18th, 2013, investigative journalist, Michael Hastings met an untimely end in a fiery one car crash just south of Hollywood. On the face of it, the crash would be another automobile tragedy by some drunken reporter high on meth.

Because of the types of stories and very important people Mr. Hastings researched, wrote about and were threatened by, the inevitable conspiracy “theories” sprang forth in the world of cyberspace after his death. Then the Mainstream Media (MSM) could easily pat themselves on the back and chortle at the poor folks whose headgear consisted of tin foil. Meanwhile, the conspiracy forums would explode with in-fighting about which agency did what to who for how much money and why. The facts that emerged, however, had enough red flags to show a concerted disinformation campaign was in effect to help cover-up the murder of Mr. Hastings.

The day after the crash, a video from a Loudlabs stringer’s dash cam was released and voraciously eaten up by both the MSM and alternative press. Why? Because the video purported to show Mr. Hastings’ silver colored Mercedes blowing a red light at the intersection of Santa Monica Blvd. and Highland Avenue. Furthermore, that car supposedly crashed into a palm tree and “blew up” just south of Melrose Avenue on Highland Avenue, and inside that car, was the body of journalist Michael Hastings.

According to an MSM article by Dylan Stableford, a witness to the car running the red light, Michael Carter, posted what he saw to his Facebook page. He described a “pearl white Mercedes” that went by his car so fast that, “it shook my car like a freight truck going by.” He then goes on to describe that, “No telling how fast the driver was going. A taxi driver was in the far right lane and we looked at each other, both saying, “What the hell was that?”… By the time the light changed, I could only see the tail lights of the white Mercedes — it was probably past Willoughby by then which was the next red light that I got stopped at. The Mercedes was flying down Highland. The same cab driver pulled up to the light at Willoughby and I looked over at him again in disbelief. Right as I did, the cab driver said something to the effect of, “He didn’t make it.” The [car] was all the way south of Melrose at this point. I looked down Highland and saw a giant fireball at the base of one of the palms that line the medians on Highland. It was surreal.” It was also a perfect story for the official narrative.

The video from Loudlabs does indeed show a white or light colored car blowing the red light at a high rate of speed. About 90 seconds later the Loudlabs stringer’s car pulls away from the parking lot but does not go directly down Highland Avenue and instead travels down Santa Monica Blvd. because there hasn’t yet been a police scanner report of the crash/explosion. A car going in excess of 100 mph, which is the preferred MSM estimate, would take approximately 19 seconds¹ to travel from Santa Monica Blvd. to the crash site just south of Melrose Avenue, a distance of nearly 2,900 feet. An anonymous witness said her husband was running down the stairs while calling 911 about 30 seconds after the explosion/crash. He can be seen in the video attempting to douse the car fire with a garden hose. Two and-a-half minutes after the car ran the red light, the first call comes over the scanner about the explosion/crash at Highland and Melrose. There’s a lot of extra time laying around there. The car that ran the red light, if it was Mr. Hastings’ Mercedes, slowed down considerably by the time it approached Melrose Avenue.

Disinformation helps killers by allowing such inconvenient facts, for example, that Mr. Hastings was afraid to drive his Mercedes and wanted to borrow his neighbor’s car, emerge as mere coincidences. Disinformation wants folks to ignore that this article, about how terrorists [and, of course the military/industrial complex] can easily hack into a car’s computer control, came out the day before the explosion/crash. Yep. Take over the steering, control the speed, set off a couple of explosions. Just another pesky coincidence. Even a study by the University of Washington warned of the dangers of the ever-computerized automobile. Meanwhile, several witnesses to the explosion/crash described the car going off “like a bomb”. A witness told Loudlabs the car was on fire before it hit the palm tree. People in their homes heard the loud explosion which shook their houses and rattled their windows.

Then a restaurant camera video was released which showed a silver Mercedes driving down Highland Avenue and it is clearly not going in excess of 100 mph. The distance between the restaurant camera and the point of the car exploding is approximately 180 feet. The time between the car next to the camera and the point of the car exploding is 3 seconds. This results in a speed of about 41 mph², less than half the speed of the car running the red light up on Santa Monica. The posted speed on Highland is 35 mph.

The video shows two small explosions before the car comes to a stop in a huge fiery blast. 9–11 callers used words like “explosion” and an anonymous witness claimed that she was awoke by a loud explosion that rattled her windows and her entire bedroom was bathed in light even though her drapes were closed. As we can see in the video, the third explosion is huge and very bright.

Photos from the explosion site and published evidence show that something blew off the front of the entire left side of the car. The passenger compartment is hardly damaged due to the collision (something we’d expect to see in a collision of over 100 mph) and the engine and transmission were found intact about 250 feet down the street from the point at where the car stopped. What forces could propel the engine and transmission that far? The most obvious answer comes from what is seen on the video and what is described by various witnesses — an explosion.

Two months after the car explosion, the autopsy report was released. The coroner made his conclusions based on the false premise, aka the official narrative, that the decedent was involved in a high speed crash with a “fixed object” (the palm tree). In the report, the toxicology screen revealed that Mr. Hastings had trace amounts of marijuana and an amphetamine in his system which were both ingested several hours before the crash and were not contributing factors to the so-called accident. Predictably, the Mainstream Media (MSM) pounced on these trace amounts in their headlines essentially making Mr. Hastings a meth head in the eyes of the public and accommodatingly tamped down the many inconsistencies in the official narrative. Indeed, the release of the autopsy report, coupled with previously released witnesses accounts and videos, makes these many inconsistencies even more glaring and the obvious “blame the victim” meme even more disturbing. Unusually, the autopsy report even mentions the discovery of two empty alcoholic bottles “near” the crash site not once, but twice, even though the report states there was no alcohol in his blood.

Reading the autopsy findings in this new light would give the antemortem injuries a different interpretation. Mr. Hastings suffered several injuries that in and of themselves would be fatal. He received a “massive displaced modified basal skull fracture”, a common injury among race car drivers that hit a stationary object at 200+ mph. It’s the type of injury that killed race car driver Dale Earnhardt, among others, but not something one would expect to see in a 41 mph collision even with a fixed object. So, how did that injury occur? Mr. Hastings suffered an “avulsion of the base of the heart with complete transverse avulsion of the atria and superior and inferior vena cava.” Again, another injury compatible with sudden deceleration due to a high speed collision with a fixed object, but completely at odds with a low speed collision. Mr. Hastings also suffered “(H)emorrhagic traumatic transection of the descending thoracic aorta at T-6.” How did those injuries occur? Mr. Hastings also suffered numerous non-fatal injuries, the most curious being his multiple fractures of the right arm and leg that were described as antemortem as opposed to the fractures on his left arm and leg which were the result of postmortem thermal fractures.

Mr. Hastings also suffered a fatal wound that some might believe to be caused by an explosion, as opposed to a high speed crash, that of, “a displaced fracture of the skull extending from the right brow down to the left inferior occipital area.” However, the coroner makes no mention of any foreign (i.e., shrapnel) material or explosive residue in any of the open wounds. Yet, there is also described, “obvious open fractures were also observed to the right arm and both lower extremities.”

Mr. Hastings obviously suffered wounds compatible with a high speed crash, but the video shows the car to be going about 41 mph. The fire that engulfed the car after the final large explosion is entirely compatible with his postmortem injuries. Given the lower than official narrative speed of his car, his fatal antemortem injuries must have occurred before he was put into the car. This narrow conclusion, that Mr. Hastings was fatally injured before he was place into the car, is the only one that can reconcile all of the contradictory accounts of this so-called fatal car crash. Mr. Hastings’ car was hacked to deliberately “crash” into a palm tree while explosions went off. He was already dead when the “accident” happened. The hacking in this case would be a remote control operation of getting his car, with his body inside, to a point where the explosives could go off and then the disinformation official narrative could then be ascribed to another drug addled youngster driving too fast too late at night.

* * * * *

---

[1] time = distance/speed, of course the faster the car is speeding the less time elapses

[2] speed = distance/time, some have argued that the restaurant video frames per second (fps) may be slower than the standard 30 fps, which would mean the car is traveling much slower than 41mph

Portland Knife Killer Was Apparently Bernie And Trump Supporter

In a not unlikely turn of events, the Portland man who stabbed to death two men and injured another on a MAX train last Friday, portrayed himself on social media as both a Bernie supporter and a Trump supporter. Twitter people were lighting up their accounts with posts of screenshots of the knife-wielding killer on Facebook. Mostly, they had an agenda by pointing out the killer posted pro-Bernie comments and such. However, they are wrong, as are the media.

The killer, er, suspect, has a long history in Portland of causing trouble at not only pro-Trump rallies but also pro-Bernie/democracy rallies. He was well-known to police. The media is playing up his posts on social media about pro-Nazi this and pro-Trump that while completely ignoring his pro-Bernie sympathizes. He also has an extensive criminal history, again known to the police. Here is a screenshot of a post showing one of the suspect's, er, killer's, pro-Bernie militant rants.

Seems a bit unhinged, doncha think? Especially compared to another post of the killer's which is certainly not pro-Trump as well. In fact, it is downright scary.

What is going here? In my long history as a Progressive in Portland, the police have been known to infiltrate groups, some to which I belonged to at the time, and to also illegally surveille said groups and to also send agent provocateurs to rallies to disrupt them with outrageous and media sexy antics. It appears to me, that this knife killer was likely such an agent. Both pro-Bernie and pro-Trump rally organizers complained to police about this man and they say nothing was done about him. Why would the police do so, if he was on their payroll? Just a question to ponder.

In the above post, the killer's rantings make the Cascadia and State Of Jefferson movements look bad, too. That's a classic psy-op tactic: guilt by association. It makes no sense on the surface given the brutal nature of this person's crimes. But, as far as you know, the killer was a wild-eyed Trump supporter and for some of you that's just peaches and cream. Any other narrative is simply going to be ignored by you otherwise, of course, your head might literally explode in a JFK kinda way.

The end result was tragic. Two men dead and another one injured. The killer spewed racial hatred at two women on the MAX train. Three men decided to call him on his bigotry and the killer reacted by pulling a knife.
It is a sad truth that in the headlong rush to achieve an agenda, deaths occur. Families suffer. Fear is stoked. Truth is buried.

Is Newly Released Photo Of George Zimmerman Faked?

It's a tale of two noses folks!
One of these photos cannot be an accurate representation of George Zimmerman's nose the night he shot and killed Trayvon Martin (see my blog post here).

The newly released photo taken by Sanford Police the night of the crime shows Zimmerman with a bloody nose and/or lip and obvious swelling on the right side of his nose. However, a photo also taken by the Sanford Police at the police station later, shows no swollen nose and all that icky blood gone. Certainly the blood could have been cleaned off but swollen, so-called broken noses do not magically lose the swelling in less than 45 minutes. One of these photos cannot be a true representation.

(This photo taken at the scene of the shooting shows obvious swelling on the right side of Zimmerman's nose. Source: Sanford Police Department)

(This photo was taken at the police station less than 45 minutes later. The swelling has miraculously disappeared! Source: Sanford Police Department)

So, I tend to believe that the second photo taken at the police station is the accurate one. There is no way a broken nose's swelling could have disappeared in less than 45 minutes. The truth is out there - right in front of your nose!