West Seattle traffic alert: Stoplight trouble at 35th/Fauntleroy

7:20 AM: We’ve noticed the 35th/Fauntleroy blinking red (in other words, akin to a four-way-stop sign) now and then in recent days, but this is the first time we’ve heard of it happening during the morning commute – and we’re getting reports it’s backing up access to the bridge. If you use that access point, you might consider heading north on 35th instead, which has an access lane that doesn’t require going through the signal. Or, use the onramps reachable via Admiral or Avalon, or Delridge.

8:01 AM: We saw a city worker on scene about 15 minutes ago. Getting on the bridge via northbound 35th was quick, by the way. Will update whenever we get word it’s fixed.

8:02 AM: Todd says it’s fixed.

8:36 AM: We have sent a crew by for a firsthand look, and they too confirm it’s working now. We have a question out to SDOT inquiring why, since it was broken last night, it wasn’t fixed before morning. Whatever we find out, we’ll add here later.

Ugh February 8, 2012 (7:30 am)

Fauntleroy is backed up to Juneau. Take alt route if you can. 54x caught in the mess too.

todd February 8, 2012 (7:54 am)

Ore is backed up past bowling alley, no one can turn on to faunt because people on faunt are running the red light, blocking the intersection, busses are the worst.

Gennessee Hill February 8, 2012 (8:08 am)

The annoying thing is the light was out last night at 11:00…why wasn’t it fixed before rush hour…#incompetence

WSB February 8, 2012 (8:30 am)

G-Hill, we noticed it last night too, but earlier. We’ve asked SDOT why it wasn’t fixed sooner, particularly given its importance at an intersection that regulates a major bridge access point … TR

Tanej February 8, 2012 (8:53 am)

Yes, the lights at 35th SW and Fauntleroy were flashing ALL evening and through the night. Aside from “Why weren’t they fixed earlier”, how about “If this was known last night, WHY WASN’T THERE A SPD OFFICER DIRECTING TRAFFIC THIS MORNING?” This was a known problem and this morning’s backups could be anticipated before I went to bed last night!

rockergirl5678 February 8, 2012 (9:00 am)

Weird – seemed fixed shortly after 8 but then started flashing green n red at same time while green the other way. So might still not be functioning correctly.

Ben February 8, 2012 (10:31 am)

given the recent pattern of events, i am getting the unfortunate sense that SDOT doesn’t have their act together generally, and/or doesn’t give much of a hoot about west seattle (disclaimer: this comes from someone whose 54X was stuck in the thick of the backup this morning).
.
there are only a few major transportation arterials in and out of the substantial population center that is west seattle. SDOT disregarding (at best) or actively causing serious impediments along one or more of those arterials – whatever the reason – is something west seattle residents should rightly expect city officials to prevent.
.
i am not down on seattle city departments in general – for example i have had only positive experiences with the city’s Department of Planning and Development – but my experiences with and observations of the city Department of Transportation sadden and frustrate me.

Walnut February 8, 2012 (10:35 am)

That light was broken and flashing red last night as early as 8:30pm.

timh2o February 8, 2012 (10:56 am)

I liked the way it released cars two at a time east bound, it really made the flow on the bridge nice, I went thru at 0635 wishing it was like that everyday!

WSB February 8, 2012 (11:14 am)

TimH2O – noticed the same thing after getting on the bridge at about 7:45, headed downtown to cover a court hearing. The backup didn’t start till past Nucor, unlike many mornings when it’s almost immediate upon official entry to the bridge on the east edge of 35th/Fauntleroy intersection … TR