Tag Archives: Michael Hastings

Windbag Alex Jones Parroting Hastings Engine Lie

On June 18, 2013, a Mercedes C250 crashed and burned on a median of North Highland Avenue in LA. There was a palm tree in its path. The fire was suspicious because Mercedes automobiles do not just burst into flames, much less infernos, upon frontal impact with a tree. They are not Pintos. They are engineered for maximum safety.

Buzzfeed and Rolling Stone promptly announced that the deceased driver was journalist Michael Hastings. The coroner, oddly enough, needed more time.

The damage to the vehicle was far more extensive than would be possible from a classic, straight-on collision with a tree. Furthermore, the engine and transmission were found thrown around 130 feet in front of the wreck. That is conceivable if the engine retained its forward momentum while the rest of the car suddenly stopped, and it’s the same physics that throws people through windshields when they don’t wear their seatbelts.

In this case, I think the engine had a little help in its flight down the street, in front of the wreck. More on that below.

It is not physically possible for a car to throw its engine backward, behind itself, when it crashes into something head-on.

Yet that is exactly what Kimberly Dvorak has been claiming on TV, and Alex Jones parrots this nonsense in the following video, at the 40-second mark:


Is Alex really stupid enough to think that the engine could be thrown backward? Are all his staff that dumb?

At around the 2:50 mark, he starts melodramatically hinting that he might get whacked for his intrepid disinfo propagation.

The only thing that’s going to kill Alex Jones is that 9th slice of bacon on his Mossad-comped breakfast platter.

Soon he’ll be taking his magical mystery parade all the way over to North Highland Avenue, where he will attempt to cement into the minds of those who still trust him an entirely distorted version of what happened there.

If Jones does not physically go here and here with a camera crew demanding answers, then you can be sure (if still in doubt) that he is not the patriot that he claims to be.

That last sentence was an exercise in restraint. I am putting things very, very politely.

At the very least, giving him the benefit of the doubt, if Alex Jones honestly believes that Hastings’ Mercedes C250 crashed nose-first into a tree and the engine was thrown behind the wreck, then he lacks a schoolboy’s intuitive grasp of physics and is therefore too dumb to be trusted as a source of reliable information.

Now for a bit of a rant.

We are in a transitional period. Big “alternative media” juggernauts like Infowars are merging with the mainstream, leading their disaffected followers into a controlled section of the fold. Millions of people with an honest hatred for tyranny unwittingly waste their attention and their energy squatting in tyrant-controlled limited hangouts, consuming feedbag after feedbag of carefully mixed truth and disinformation.

Meanwhile, the mainstream media outlets increasingly report information that is “shocking” and “incriminating”, such as Wikileaks’ “revelations” of U.S. war atrocities (yawn) that were “broken” by the Zionist New York Times — or, most recently, Snowden’s “revelations” (yawn) of the NSA’s domestic spying programs.

People who watch CNN and Fox are already paralyzed, so what difference do such “revelations” make?

They gradually “normalize” the unacceptable. The sheeple in the Jones pen will go on baah-ing their told-you-so’s to those in the MSM pastures, who will blink and wonder why, until there’s no distinction anymore, just idiotic bleating, just incoherent noise — a brave new world of cognitive dissonance in which many people will trade in their common sense for some relief, and go along with such idiotic nonsense as the engine landing behind the wreck. For many who have their hearts and minds heavily invested in Alex Jones, it would be too painful to listen to their common sense, and stop listening to him.

Meanwhile, a few brave sites will continue exposing the juggernauts and doing their best to report truthful information. May God preserve them in the times ahead.

Those who pursue total control of finance, total control of food, total control of breeding, total control of me and you, total control of our thoughts and feelings, total control of mind, of culture, of spirit, of biology, of creation itself — in short, the luciferian rebels who are insane enough to pursue what is ultimately impossible — the would-be gods whose most sophisticated creations even a little insect puts to shame — the psychopathic control freaks that create the currency and run the world’s financial system like a circuitboard — the lizard-brained “elite” class that make and break the plastic people, the perverts and miscreants put up before the public as their “leaders” — the gangsters in three-piece suits, the cruellest, most heartless, most hellishly bloodthirsty gangsters in the world — they will stop at NOTHING to achieve total control of information, and they do NOT tolerate dissent that presents a genuine threat to them.

If you want to see where the engine really landed, and how it probably got there, please review my analysis of the crash scene. It is the only analysis I have seen which explains the wreck’s caved-in roof:

https://farganne.wordpress.com/2013/06/28/two-car-bombs-at-the-hastings-crash-the-evidence/

For the one crash scene detail which proves beyond all doubt that the car came apart before striking the tree:

https://farganne.wordpress.com/2013/07/02/proof-hastings-car-exploded-before-hitting-tree/

______________

Appendix 1: Engine Location

engine_loc_llabs

The streetlight, manhole cover, and leaning trees can all be seen from above:

Highland-Clinton

The distance:

engine_loc_maps

Below, the white arrow represents the trajectory of Hastings’ car. The yellow flash represents an explosion.

Highland-Clinton2

Appendix 2: Intact Front Bumper Panel

With a 2013 Diamond Silver Metallic Mercedes-Benz C 250 Coupe superimposed:

Advertisements

Kimberly Dvorak Spreads Ridiculous Claim About Hastings Engine

In more than one appearance on San Diego’s Channel 6 News, “investigative” journalist Kimberly Dvorak has stated that the engine from Michael Hastings’ Mercedes c250 landed behind the wreck — defying, in her own words, the laws of physics.

She even claims to have consulted university professors. Here she commences dispensing this rank nonsense at the 2:00 mark:


I am astonished that such statements can be received with straight faces. Yes, the crash did happen in Hollywood, but only in cinematic productions are the laws of physics defied.

I will now show you where the engine really landed.

Here is a screenshot from the Loudlabs footage, taken at the scene after the crash:

engine_loc_llabs

Note the streetlight pole to the left. Note also the manhole cover and the concrete slab it sits in, as well as the trees leaning over the sidewalk.

All of these are clearly visible in the following aerial shot from Google Maps —  click to enlarge:

Highland-Clinton

That is the northeast corner of the intersection of North Highland Avenue and Clinton Street.

Zooming out — again, click to enlarge:

Highland-Clinton2

The car was speeding south on Highland as indicated by the white arrow.

The yellow flash indicates an explosion that took place. This explosion demolished the front end of the car and threw the engine southeast.

That is the only way the engine could have reached its final position.

Had the car hit the tree fully intact, the engine could not have passed through the tree, much less flown down the block.

I think two bombs were involved: one that destroyed the front end and threw the engine, and one that blew the gas tank, which could account for the massive fire. My analysis leading to this conclusion takes into account and matches up the damage to the car and to the tree:

https://farganne.wordpress.com/2013/06/28/two-car-bombs-at-the-hastings-crash-the-evidence/

Long story short, the Mercedes was already a wreck when it hit the palm tree, rotated, and landed, burning, in its final position facing slightly southeast.

There were many long days when outside of eating, sleeping, and answering to Nature, my sole activity was studying the details of that crash scene and deducing a scenario that explains all its oddities.

I’m glad I wasn’t trying to swallow food when I saw Kimberly Dvorak on TV telling the world that the engine landed north of the wreck, behind it.

I sent a “friend request” to Kimberly on Facebook. She accepted it. I did not complain publicly on her timeline. I figured she had just gotten it backward somehow and decided to give her the benefit of the doubt. So I sent her private messages politely pointing out her error, providing a link where she could see for herself where the engine really landed, and asking that she correct it.

In Facebook, when you send a private message to someone, and they click in the message window, you are notified that the message has been seen.

Kimberly Dvorak saw my messages, and she never did respond.

Next thing I knew, I was watching a video of her up on RT news, spouting the same utter nonsense about university professors declaring that the laws of physics had been violated by the engine landing behind (north of) the wreck.

I have not yet seen Kimberly Dvorak retracting these ridiculous statements.

If she really did consult “university professors”, and they corroborated her nonsense, then they did not take the time to become familiar with the crash scene.

If she truly believes that the engine landed behind the wreck, then she should not be trusted as a source of information, especially when she ignores reliable sources of it.

Two Car Bombs at the Hastings Crash — The Evidence

Two Car Bombs at the Hastings Crash — The Evidence

[NOTE: If you read this article a few days ago, please consider re-reading, as it has been substantially updated, and now includes a mathematical analysis of the engine/tranny throw. Also, there is one detail that absolutely proves the car did not hit the tree intact. This detail is found in the update at the end of the main body of the article below.]

First, in case you are unfamiliar with the crash scene, a brief orientation.

The car crashed into a palm tree on the median adjacent to 621 North Highland Avenue (west side). It was traveling due south. An aerial shot from Google Maps:

aerial_crash_bearings(Click to enlarge)

The red arrow represents the car’s trajectory until it swerved eastward onto the median. The indicated palm tree is the one it struck. The red ‘A’ thumbtack is 621 North Highland.

The car struck the tree on its north-by-northwest side — that is, if you were to face the tree looking due south, the initial impact zone on the trunk would be slightly off-center to the right. That is where the bark is cleanly chewed away. In the following photo provided by Jim Stone forum member Doug, you can see that the impact damage extends around the west side of the trunk, dissipating as it goes:

trunk_nw

Note that to the extreme right of the trunk (southwest side) you can see the end of impact damage and after that there is only charred bark. This damage pattern indicates that the car struck the tree and rotated counterclockwise if seen from above. It ended up facing just south of due east. Yet there are no skid marks on the grass or asphalt from the back tires, indicating that they were airborne during the rotation.

Here is another shot provided by Doug showing scorched grass and asphalt but no skid marks on either. Doug took it from the west side of the avenue, in front of 621 N. Highland, facing east. The swath of scorched grass tells us the car’s orientation as it burned.

impactedtree_doug

So, it is established that the car struck the tree slightly to the west on its north side and rotated with rear wheels airborne to the position indicated by the scorched grass area.

How and why did that happen? I’ll call this The Rotation Question, and I will answer it below.

First, we need to look at the engine, which was thrown 130 feet to the southeast and landed near the northeast corner of Highland Ave. and Clinton Street. First, a view from the ground, grabbed from the Livelabs footage appended at the end of this article:

[Note: Some guys have jumped on me — “That not the engine, that the transmission, your a moron!” — okay, I’m not a car guy. Whatever. That thing is heavy and it flew a long way.]

engine_loc_llabs

You can see the streetlight (left of engine), the concrete area with manhole it sits on, and the two leaning trees (right of engine) both in the following aerial shot and from Maps street view:

engine_loc_maps(Click to enlarge)

The car hit the tree on its north-by-northwest side. The engine ended up 130 feet southeast of the tree. Even assuming that no bombs were involved, the obvious question is, how did the engine clear the tree? It could never have flown through it!

I’ll call this the Magic Engine Question. Again, I’ll answer it below.

[Update: After reading this report, my engineer friend Bruce got curious and did some calculations on the engine flight, proving that even if the tree weren’t in the way, the car would have had to be going 250 mph to throw the engine that far — and that doesn’t even factor in the bolts fastening the engine to the car. His presentation is here: Simple Physics Calculation]

Next, I direct your attention to the debris field extending from the wreck area in a southeasterly spray pattern toward the blown-out engine.

On the east side of the avenue, facing southwest, engine down the road, off-screen, to the left:

debrisfield_sw

Facing northwest, toward the wreck:

debrisfield_nw

The debris field is extensive and far-reaching. I cannot consider it consistent with a mere high-speed impact.

Had it just been a high-speed impact, the front end ought to have been “wrapped around” the trunk of the tree, as you’ll see below.

But all that debris came from somewhere, and here it is — a mostly missing front end:

frontendgone2

The sheet of metal to the left of the tree is the Mercedes’ hood, wrapped around its south side. Here’s a due-south grab from the median:

frontendgone3

Now think about this for a minute. Take a good, hard look, and THINK.

Is there some quality about palm trees that makes them incredibly destructive to the front end of an impacting vehicle?

For quick reference, here are some shots of high-speed front-end impacts. Click on them for the sources.

truck_tree
cartree2

car_crash_tree

The person who posted this next one claims the driver was an uncle going 200 kilometers per hour, or 125 mph:
large_crash

Click on this next one and you’ll see an assortment of similar photos, non of the wrecks burned, and none with detached hoods:

OLYMPUS DIGITAL CAMERA

Based on this evidence alone, I am convinced  there was a bomb in the engine compartment that destroyed the Mercedes’ front end and threw the engine. Since the cab was not destroyed, it was a directional bomb designed and placed to project the force of the explosion toward the front of the car.

Whiz kid Jim Stone forum member Glitch had this to say on the subject:

@Farganne Excluding the impossibility of the engine clearing the tree, the engine would not have gone 130 feet away from a collision alone. First, the engine would have to break free of its mounts, which are by no means weak. Then it would have to rip through the hood&frame in order to exit the engine compartment. After all of that, it would have to still have enough force from the momentum to travel 130 feet. Now, the engine in a Mercedes-Benz is not big, and weighs around 800-1200 lbs, and after ripping through the frame, it would not go very far. I don’t include math in this one as there are so many factors that are difficult to mathematically quantify, (the force to bust through the frame) and I don’t want to sit here all day doing it.

Moving on, here is a view of the wreck from the east side of Highland, facing due west:

crash_eastside

Note that the top of the cab is caved in. Again, there’s the hood, twisted around the left (south) side of the tree.

The right front wheel looks to have been blown forward and cocked at an angle almost perpendicular to the rest of the car. It didn’t appear that way before the 2:00 mark of the Loudlabs footage, but it did afterward. There were secondary explosions during the time the car sat burning, so this bit of damage may have resulted from one of those.

Either that, or the wheel we see in this shot is actually the left front wheel blown over and obscuring the right front wheel from this angle.

Next, we need to take a look at the fire.

hastingsfire

Many have been quick to point out that a Mercedes is not a Pinto. It doesn’t just burst into flames on impact with a tree. The gas tank in this vehicle is situated at its rear anyway. I think Jim Stone was correct in his assessment of the fire. It was instantly all-engulfing and incredibly intense. Such a fire could only have been initiated by a gas tank bomb, and I am taking that as a given.

I will close the focus on the fire by noting that Jose, the Spanish-speaking witness in the Loudlabs footage, though struggling to express himself in English, clearly indicated (3:45 – 3:48) that the car was on fire before it hit the tree. That tells me the gas tank bomb went off before the car hit the tree.

Now, after spending probably dozens of hours squinting at this scene from all angles, and visualizing scenerios to find one that explains all the observations I have made thus far, I am going to tell you what I think happened.

As it passed the two closely-spaced palm trees to the north of the impact palm, the car swerved left onto the median.

At that moment, both the gas tank bomb and an engine compartment bomb simultaneously went off.

Now for some Newtonian physics — equal and opposite reactions. The gas tank bomb caused the rear end of the car to lift. At the same time, the kick-back from the bomb in the engine compartment provided a counteracting “downward-and-backward” force.

The car flew toward the tree at reduced speed with its rear end raised and nose lowered.

Going in slow motion now. The blast threw the hood into the tree. It threw the engine down the street. At this point, there would still have been sufficient distance between car and tree for the bomb to throw the engine past the tree and down the street. This would be the point of origin of the debris field.

The hood hit the tree and wrapped around it.

At that point, before the hood fell, the car hit the tree with two impact points: first, whatever forward-projecting metallic scraps remained of the lower chassis (base of the trunk), followed by the upper edge of the windshield (higher up the tree).

The wrapped-around hood shielded the tree from surface abrasion at the upper impact point.

The Mercedes hit the tree slightly to the left of its own center. Forward momentum made it rotate counterclockwise (viewed from above) while falling to its final position, rear wheels airborne the whole time.

As it rotated, the wrapped hood went with it and ended up curved around the tree’s south side.

It fell in a heap where you see the scorched grass.

Loudlabs arrived, and I have had a headache ever since.

I believe that the car was remotely controlled.

And that is how I see it having happened.

Here is the Loudlabs footage:

Update:

Jim Stone forum member tigerwolfe made this valuable observation:

I believe I have identified a piece of the debris field from the limplobs video at around the 4:50 mark. While viewing the vid, I’d seen this peice many times, Like I’m certain many others have too. Could not ID it, so I ignored it.

It turns out to be from the nose of the Mercedes. The part of the front bumper to which the front license plate attaches. The front California license plate is NOT in the bracket, and could NOT get out without removing the white plastic trim.

This piece found on the road is NOT a piece from a car that hit a tree head-on at 100mph. And this piece did NOT come from a car that was currently licensed in CA.

A frame taken from the video:

And close-ups with a 2013 Diamond Silver Metallic Mercedes-Benz C 250 Coupe superimposed.

I will add this to tigerwolfe’s observation:

Q.E.D.

_____________

Addendum 1:

Was there a driver in the car?

I offer for your inspection these two shots. Is that a crash dummy head?

head_side

head_front

_____________

Addendum 2:

There has been some confusion about this shot. At first glance, it doesn’t seem to match the crash scene, but actually it does.

telescopic

The denser, more crowded appearance of palm trees is due to telephoto lens distortion. The sign with the arrow above the car is way down at the intersection with Clinton Street. The telephoto lens magnified it.

From this shot it is also obvious that they shifted the wreck and removed the driver’s door after they extinguished the fire. Why, I don’t know.

___________

Addendum 3:

In my humble opinion, anyone claiming the Mercedes was hit by a Hellfire missile is either deliberately or mistakenly full of it. For reasons that should be obvious by way of the preceding analysis.

Over and out.

Hastings Did Not Die in the Hollywood Crash. Period.

Jim Stone Forum member Paul Short posted this expert analysis of the following video.

The upshot: there was no dead body or even body parts at the scene. The wreckage is consistent with eyewitness testimony, and this analysis explains the gushing plume of water on the median.

The most likely explanation is that the car was steered by remote control.


The following is what myself and a relative who spent 25 years as a fireman have concluded after combing through the video above.

The video gives us a near 360° perspective of the accident scene, from the dashcam footage at the beginning that gives us the same view as one would have if they were inside the car before it crashed, to the all-around panorama of the crashed car as it’s on fire, to after the fire is out and the cops are standing there with firefighters and witnesses.

The witness, Jose, the spanish guy in the blue mechanic’s shirt, says the car came fast down the street and he indicates by slapping his hands that the car bounced several times, bottoming out the suspension and causing “fire” or sparks on the road. This is because when traveling at a high rate of speed on a level straight street, intersecting streets have their own road crown. You don’t notice the road crown when you’re going slow, but cross an intersection fast and it’s like launching off a ramp. When the car crossed the intersection approaching it’s final resting place, the suspension hits the road crown of the intersection causing the wheels to leave the pavement momentarily. With no rubber on the road for a split second at a high rate of speed the car is essentially flying and cannot be steered. Wheels touch down again, bounce the suspension, several times and the car is out of control.

The car then mounts the curb and hits the fire hydrant head near the driver’s side front bumper. The hydrant, even though it’s sheered off by the lateral force of the speeding 3,000+lb car is essentially still a stationary chunk of metal. The hydrant cuts a swath through the car, taking the front driver’s side wheel with it back through the car and dislodging the engine/tranny. That stuff is passing through the car and some of it rips into the gas tank, but the tank, the gas, is all in forward motion with the rest of the mass of the car.

Now, with all that mass still in motion, but starting to slow down from meeting all the resistance of the curb, hydrant and whatever else it hit … the car hits the tree, with the tree basically being inserted into the the space formerly occupied by the engine and front wheel. Coming to a sudden stop like that causes some of the gas, still in motion and wanting to stay in motion due to the laws of physics, the gas sprays forward through the swath cut through the car by the hydrant and catches fire from sparks generated by a frenzy of scraping metal all in motion at different speeds.

At the same time all this is happening, the engine ejects down the street taking a bunch of debris with it, which can be seen on the street in the video above.

All that explains what happened and it’s all clear when watching that video above.

My fireman friend, however, has a question, and he pointed out that everyone in that video have the same question…

Where is the body? Where are the body parts?? Why are the cops standing there scratching their heads???

Think about it – a fire hydrant, front wheel and attached suspension components cutting a swath back through a vehicle’s firewall into the driver’s compartment would have shredded the driver into pieces and those pieces would have ended up among the debris that got sprayed down the street along with all the other stuff we see in the video.

Yet there are no hands, feet, legbones, organs, skin… nothing, no evidence of a body or body parts and everyone in the video is asking and wondering where the driver is???

IMPOSSIBLE.

MICHAEL HASTINGS WAS NOT IN THAT WRECK.

NO ONE DIED IN THAT CRASH.

Paul Short’s website: www.paulshort.com

______________________

UPDATE:

There was no fire hydrant. The following screenshot from Google Maps is just a few blocks south of the crash scene, and in it can be seen the source of the gushing water, because the fixture for the pipe is found on Maps at the actual crash scene.

crashscenenot

Here is the real crash scene, with pipe fixture. Between the time Google shot this avenue and the crash, a pipe was obviously installed:

crashscene

So, no fire hydrant. But also no dead body, or body parts.

The mystery continues …..

Proof That A Car Bomb Killed Michael Hastings?

Disclaimer: When I first posted this, I was excited and maybe too sure of myself. I am not an expert in these matters. So I offer the following evidence to support my current thesis that a car bomb in the engine compartment destroyed the front end of the Mercedes and lobbed the engine down the street. I have been alerted to at least one precedent for engine ejection upon impact, so I wonder what a bomb could do.
________________

Note: Jim Stone has stated that the following image is from a photo op scene with a switched car at a switched location. I don’t know. Even if that is true, the footage showing the obliteration of the car’s front end was taken at the scene, when it was still dark.

When I first saw this tableau, I immediately wondered: WHY THE BLANKET?

0:59

Now I know. It’s because the front end of the car is almost completely GONE.

Check out these still shots, taken from Loudlabs News footage (posted below):

blownapart

The carriage and rear end are cocked back from a blast that cleared the engine compartment. The right front wheel and part of the front bumper are about all that’s left, and they are cocked forward.

Now from the driver’s side angle:

frontendgone2

Note what looks to be the hood twisted around the left side of the palm tree.

Now, a direct side shot:

frontendgone3

The blanket was there to hide the fact that almost the entire front end of the car is gone.

Only a bomb could have done that.

Perhaps this explains the flight of the engine down the street. I leave that to the more technically-minded to decide.

Jim Stone’s analysis: http://www.jimstonefreelance.com/hastingsmurdered.html

Update:

A member at the Jim Stone Forum argues that such damage is consistent with a normal high-speed tree impact. That may very well be. But Stone’s analysis has already shown that this was no ordinary car fire.

That raging fire, in my opinion, would not happen from a bomb-free impact. Car experts agree.

Consider, too, the eyewitness testimony at 1:11 of the Loudlabs footage below, where she states that the car “exploded upon impact” with the tree.

Also the other eyewitness who told the local news reporter that her house shook and her windows rattled — that it sounded, and felt, like a bomb had exploded.

Then there’s the engine down the street.

Finally, I went to Google Images and looked up some high-speed vehicle-tree collisions. They are indeed incredibly destructive.

But look at that last photo again:

frontendgone3

Seems to me that there is a lot of “gap” between the tree and the cab of the car, and no wreckage in there — just empty space.

Had the car hit the tree at high speed, causing all that damage, I think the cab would be scrunched right up against the trunk. Like when they say that Jed “wrapped his Camaro around” a telephone pole.

It looks to me like the car bumped into the tree and that triggered a detonation.

Here is the Loudlabs footage:

____________

Appendix:

Note: Unless you are a Jim Stone Forum reader, this will not be significant to you.

blownoutsctn blownoutsection

Questions about the Death of Michael Hastings

According to the following article from the Los Angeles Times, Buzzfeed and Rolling Stone announced Hastings’ death on Tuesday:

http://www.latimes.com/local/lanow/la-me-ln-coroner-no-identification-michael-hastings-20130618,0,5825533.story

Yet, as the very URL of that article makes clear, the coroner had yet to identify the body. Absent a positive identification, how were Buzzfeed and Rolling Stone confident enough to make that official announcement?

The rest of this article will focus on a single newscast, which yields enough incoherent information to indicate that Hastings’ death was not the result of an accident. All subsequent still shots are taken from it, except for those from Google Maps.


First, according to all accounts, the car was a brand-new Mercedes.

No car will blow up from getting run into a tree, least of all a Mercedes. And yet:

rochellefran51

An eyewitness claims the blast was so intense that it shook her house and rattled her windows.

Those L.A. palm trees must be made of something more than wood. Hell, everything in Hollywood is fake anyway. Maybe those palm trees are made of some kind of plastic. Like C4.

Moving on, our next eyewitness is Hollywood producer Gary Grossman, whom we can thank for America’s Funniest Home Videos (1989):

grossman107 garygrossman109 engine113

He says the engine flew 50 or 60 yards and landed near a telephone pole. Other accounts say 100 feet. Who’s counting? How does any car, much less a Mercedes, hit a palm tree and explode with enough force to throw the engine ANYWHERE???

Vin Diesel would blush at a script like that. Not even a hack like Gary Grossman could conceive of writing it. What does that tell you?

For the record, here is Grossman’s address from the Hollywood White Pages:

grossmanaddress

546 North Highland Avenue. I decided to plop myself down there on Google Maps. Here is the scene of the “accident”, from left to right.

highland1 highland2 highland3

Do you see how SPACIOUS it is? LOOK at all that SPACE! And yet they say Hastings, in the darkness at 4:30 a.m., smashed his Mercedes into one of those toothpick palm trees with enough force to cause an explosion that sent the engine flying some distance, any distance at all. Impossible. Even in Hollyweird.

Even if a collision took place, was he blind drunk? If so, what are the odds he’d hit one of those trees? If he wasn’t blind drunk, then he was suicidal. Why would a suicidal man pick a palm tree in the middle of a residential neighborhood?

After Grossman’s testimony, we get this chilling eulogy from the talking head:

hastingsencomium130

Hastings will, likely, partially be remembered? That is very deliberately worded. Whoever had the bomb put in Hastings’ car hated him with the passion of a billion white-hot suns, and wanted to crap all over his accomplishments by delivering that insult unto his legacy.

And who has the power to make sure that the slight is worded just so, via the mainstream news?

I’ll give you a hint: the answer rhymes with “news”.

Still stumped? Oh well, take a look at who was first on the scene, except for Grossman:

jewishgroup

Here’s the first responders’ website:

http://www.hatzolahofla.org/

Make sure to turn your speakers down before you click, or they will offend your eardrums as well as every other atom of your being.

Jim Stone’s take is here: http://www.jimstonefreelance.com/hastingsmurdered.html

For more on how cars do not turn into bombs upon impact with trees:

http://www.thetruthaboutcars.com/2013/06/famed-non-automotive-journalist-michael-hastings-turns-a-c250-into-a-bomb/

_____________

Tinfoil Hat Addendum:

They waited until Hastings was 33.