Reader report: Safety reminder after Fauntleroy crash

crash1.jpg

That photo comes from Fauntleroy’s Ron Richardson, along with this account of what happened, and the safety reminder it sparks:

Around 3 pm Saturday there was yet another rear-end accident as a car heading up Fauntleroy Way SW ran in to a parked car. The driver of the moving car was sent to the hospital to be checked out. One of the responding police officers said that there appeared to be no serious injury.

Moving cars slamming in to parked car is a common happening along Fauntleroy Way with northbound traffic. Drivers often are distracted by action in and around the park. Drinking has been a factor in some of the incidents. [editor’s note: there is no police report available yet on what might have been to blame in this case]

Some folks do not realize that Fauntleroy Way is a two-lane road and not a four lane road so they drive along what they think is a curb lane until they run in to a parked car. Drivers also need to be aware that this area has kids crossing to the park, fast moving traffic, cars pulling out from side streets, and drivers making dangerous U turns in attempt to get in to the southbound ferry lane. This latest incident happened at Fauntleroy Way and Rose Street.

That intersection is across from central Lincoln Park; here’s a map.

2 Replies to "Reader report: Safety reminder after Fauntleroy crash"

  • nulu September 13, 2008 (8:34 pm)

    Thanks for the primer, Ron.
    It’s always a bit embarrassing to run into a parked car, although this certainly didn’t occur while the speed monitor was working.
    If those cadet troopers at the ferry dock did not direct drunk ferry drivers to exit the dock in tandem onto the same two-lane Fauntleroy, maybe we would all have more of a chance.

  • paul September 13, 2008 (9:23 pm)

    And it has a speed limit, which most people do not adhear to. At our shop its getting quite bad in the afternoons when people are rushing to the ferry. Not sure on the mornings because we are not in till 9.

Sorry, comment time is over.