The Howard Franklin Bridge Commute Reality
The Howard Franklin Bridge carries I-205 traffic between Milwaukie and Portland, and during rush hour the backup routinely stretches for miles. Most people who commute through that corridor learn the hard way that losing time there isn't a matter of minutes — it's a matter of your whole schedule breaking apart. I learned this after spending three months tracking my own commute times and comparing them against what GPS apps promised. Here's the thing nobody at ODOT seems eager to broadcast: the bridge has a capacity problem that's structural, not seasonal. The two-lane approach from the Milwaukie side funnels roughly 40,000 vehicles daily through a bottleneck that was designed for half that volume in the 1980s. When even one car brakes hard near the queue, the shockwave propagates backward for two to three miles. That's basic traffic physics, not bad luck. Last October I hit a standstill that started at 7:18 AM near the SE 122nd Avenue on-ramp and didn't clear until after 8:45. I was running a doctor's appointment that started at 9:30. Google Maps had told me at 6:50 AM the drive would take 18 minutes. It took 87. The app wasn't lying — it just couldn't account for the secondary backups forming from side streets like SE McLoughlin that had no way to discharge into a gridlocked mainline. Once those merge lanes fill, the entire system locks up for 40 to 60 minutes after the initial peak passes.
The workaround that actually works for me is abandoning the 7 AM window entirely. Leaving at 6:15 AM gets you across in under 12 minutes most days. The tradeoff is you lose the ability to do anything productive in those extra morning hours unless you've already prepped the night before. I prep everything the evening before — bag lunch, lay out clothes, load the work laptop — so the early departure doesn't cost me more than sleeping an hour earlier. It's not glamorous but it keeps the day intact. Another counter-intuitive detail: driving the alternative route through Milwaukie itself via McLoughlin Boulevard is almost always slower during peak hours. It sounds logical — avoid the highway — but the signal timing at the major intersections (SE 181st, SE 122nd, the McLoughlin and 181st junction) wasn't synchronized for commuter volume. You'll burn 25 to 35 minutes at lights that feel arbitrary because they are. The lights are timed for local residential flow, not a thousand cars per hour trying to cross the Willamette. Winter compounds the problem. When it rains or the temperature drops below freezing, the approach ramps develop micro-skidding conditions that slow vehicles by 10 to 15 percent right where capacity is already constrained. A 15 percent slowdown on an already saturated link doesn't just add a few minutes — it pushes the queue length past the point where recovery happens within a normal commute window. I've sat through mornings where the backup extended all the way back to the I-205 / Sunset Highway interchange because of a light drizzle and a fender-bender at the bridge toll plaza area.
If you're trying to minimize time lost, the practical steps are straightforward even if they're inconvenient: Leave before 6:30 AM — this is the single highest-leverage decision. The difference between departing at 6:15 and 7:00 can be 40 to 50 minutes of added travel time on a typical weekday. Use real-time radar, not just GPS estimates — the Oregon Department of Transportation's traffic camera system at the bridge and the nearby I-205 / Milwaukie Avenue interchange shows actual queue formation in real time. A GPS ETA is a prediction. A camera feed is what's happening right now. Check both before you merge onto I-205 eastbound.
Get the Full Details

Have a secondary departure plan — if the 6:15 window isn't feasible, consider reversing your schedule. Some employers allow staggered hours. Leaving at 8:30 AM and finishing at 5:30 PM avoids the morning bridge crush entirely, and the evening return has its own separate problems that are generally shorter and more predictable. The structural reality is that the bridge isn't getting wider anytime soon. Reconstruction discussions have floated for over a decade, but funding and environmental review on the Willamette waterfront side keep pushing timelines out. Until there's a new crossing or a major capacity increase, the only variable you control is your departure time and your expectations about what GPS apps will tell you. I've stopped trusting the "typical time" estimate on maps during 6:45 to 8:30 AM. It's based on historical averages that smooth over the worst days, which means it systematically understates the risk on days when weather or incidents amplify the normal congestion. On those days you're looking at 60 to 90 minutes for a trip that should take 20. That's not an outlier. That's the distribution tail that shows up roughly twice a week in winter and once a week in summer.
The math is simple. If you spend an average of 45 extra minutes per commute day dealing with the bridge, that's roughly 3.5 hours per week or 180 hours per year. That's a significant chunk of your life going into a two-lane span over a river. The workaround isn't elegant but it's the only one that works consistently.