Wednesday, October 26, 2016

One crash too many on Griffin Avenue


Neighbors inspect crash damage on Griffin Avenue | Photo courtesy Matt Johnson

MONTECITO HEIGHTS — A speeding car crashed into parked vehicles this afternoon in the 3600 block of Griffin Avenue, the third collision in recent months on this stretch of the street, according to one resident.

A blue car heading south on Griffin smashed into a parked vehicle, which then hit a parked SUV at about 12:15 pm, said Matt Johnson, who lives near the crash scene.  “I heard the impact and came out of my house to see the driver emerge from the blue car, remove [an Amazon delivery and laptop computer], have a verbal confrontation with the residents of the house before fleeing the scene,” Johnson said.  It’s not clear what caused the crash or if the driver who  suffered any injuries, Johnson said.

Two other crashes also involving speeding vehicles have taken place on  this stretch of Griffin Avenue within the past nine months, Johnson said. One vehicle flipped over at the end of a high-speed chase, and the other involved an SUV that flipped over about a month ago in broad daylight, he said.

“This stretch of Griffin Avenue is purely residential and needs to have speed bumps installed to keep the many children and elderly who live on this road safe,” Johnson said.

Eastside Guide Small Logo

The Eastside Guide Business Directory is designed to help readers find the services and products they need.

The businesses and services in the directory have not been reviewed nor are they endorsed by The Eastsider. Users are responsible for taking care to investigate any offers, products or services provided by businesses listed in the directory.

Want your business included in the Eastside Guide? Click here for details

Eastsider Advertising


  1. Carsmakepeoplestupid

    Road Famine.

  2. Just another day in chaotic council district 1. What a random cosmic alignment of chance events. Somebody should probably install a stop sign where that crash was so people know to slow down there, right?

  3. Well, wait a minute. How do you, the reporter, know speeding was involved? You pronounce it as a fact, as a final conclusion — it is not, it is one person’s say-so, Gee, the person you are relying on didn’t even see the accident! They say they were inside and heard the crash, and then came out. They actually have ZERO idea how fast anyone was going, they are simply making a presumption. As a reporter, you can’t be relying on someone’s presumptions and reporting it as fact, starting rumors. You can say one resident SUSPECTED it might have been speed, but even then, responsible journalism requires you back that up with something to even justify repeating it. You can’t pronounce that as a fact it was speed.

    This guy was making a delivery? I’ll bet it more likely he was on his cell phone, not paying attention to his driving. This report will now create a big hoopla about dangerous drivers and cars are the bane of society and bring responses to thwart traffic — but the real solution would probably be to have a crackdown on people using cell phones while driving. Or, maybe it was neither, maybe his steering linkage was broken.

    In the end, there is nothing in this story to indicate anyone have any idea of the cause. If the police do ann investigation, because apparently this is hit and run, then skid marks and other might give us an answer, but for now, we have none, and none should be getting reported as fact.

    In fact, since in the photo, the car appears to have been left behind, this driver fled on foot. That would suggest it might not even be his car, maybe it was a stolen car, maybe to steal that laptop computer he saw on the seat..

    • You go after the journalist for stating there was speeding involved while completely unsubstantiated, then immediately claim cellphone use was likely the case, I get that you’re not a journo, but yikes.


      • No, I didn’t say cellphone use was the problem. I suggested it as an example of any number of possibilities that might have been going on, that speed is not the only thing that will cause a car crash, any number of things might, and one should not just jump to a conclusion with no facts, as this story has.

    • You state, “The guy was making a delivery?” This based on statement “…see the driver emerge from the blue car, remove [an Amazon delivery and laptop computer],…”

      The driver could have picked up his own package from an Amazon pick-up center, or was taking a present to a friend who didn’t care if it was in the Amazon box, or perhaps the driver stole it from someone’s front porch? Many, many possible scenarios.

      So, Now you’re the person making assumptions, Mr. Righteous.

Post a Comment

Please keep your comments civil and on topic and refrain from personal attacks. The moderator reserves the right to edit or delete any comments. The Eastsider's Terms of Use and Privacy Policy apply to comments submitted by readers. Required fields are marked *