A Resident Data Brief - Fremont, California
We checked the city's own records, state data, and federal road-safety research before making a single claim. Here is the honest case for re-evaluation - and we left out everything we couldn't prove.
The strongest evidence the design hurt drivers isn't ours. It's Fremont's own project to restore the right-turn lane it removed.
In 2016 Fremont spent $1,296,450 in federal HSIP grant money to build "protected intersections" at Fremont Blvd & Mowry and Stevenson - a redesign that removed the dedicated right-turn lanes. Now the city is adding a dedicated right-turn pocket back at Mowry - in its own words:
"The project will address an existing deficiency at the Fremont Boulevard/Mowry Avenue intersection and will provide a dedicated right turn pocket for the southbound Fremont Blvd approach to address the delay and queuing currently experienced by motorists ... up to a 49.4% reduction in average delay during the morning peak period." - City of Fremont, official "Fremont Boulevard (Country Drive to Grimmer Boulevard)" project page. Estimated project cost: $14 million.[1]
And the fix is thinner than it sounds. By the city's own impact table the 49.4% cut applies to just one of four approaches (southbound) - the other three see 0% change - and even that "improvement" is measured against the delay the city's own ~2021 turn-lane removal created. It's clawing back its own mess, not beating the original intersection.[1]
Worse, the same $14M project builds three more slip-lane removals - Beacon, Sundale, Bidwell - that the city's analysis says will increase delay (Beacon's AM peak: 10.2 -> 16.1 sec). Undoing the design at one intersection while repeating it at three. And it's a pattern - the Council rejected the Paseo Padre road diet 5-2 (2021) and kept four lanes there again in 2026. When a city keeps declining and undoing its own designs, "is it working?" answers itself.[1][2]
This is the live, real-dimension Roadscape sim of the turn. The green bike lane is on the Mowry turn side; the right-turning vehicle path crosses the protected lane zone at Mowry, then enters the receiving lane. Vehicle bodies are scaled against a 10.5 ft city lane so the car, box truck, bus, and WB-67 read at true size — not fake-small.
Why this belongs in the study: Fremont's own delay model says restoring the right-turn pocket cuts AM-peak delay by up to 49.4%. This visual is the dimension check: the bike-lane side and travel lane are exactly where the bigger vehicles need room.
Screening read · generated July 6, 2026 · AI-summarized from the sources cited below — not a live per-visitor generation. Screening-grade, not PE-stamped; regenerated on a schedule and reviewed before publishing.
Screening-grade assessment of flow, safety, and dimensions at Fremont Blvd & Mowry Ave — focused on AADT / peak volume, crash context, WB-67 and BUS-40 swept path / off-tracking, and lane-width fitment.
Source: Roadscape corridor AI (screening-grade, not PE-stamped) — summarized from the records cited in this article. A dated read, not a live feed: it can't change between visitors or stall in public.
A parent late to school pickup. A worker losing another few minutes every morning. A bus or delivery truck clipping a hardened corner. An ambulance with less room for traffic to clear. That is not a culture-war argument - it is daily life on public roads.
The fair test is simple: if the redesigns saved lives and did not meaningfully hurt movement, Fremont should publish the corridor-level proof. If the proof is missing, residents are right to demand a pause before the city spends more money and repeats the same geometry.
This is the part residents feel every day. Fremont was not shrinking into a low-car town when these designs were pushed. It added people and households after 2010, South Fremont became a bigger job and housing node, and the commute record still shows a car-dependent city.
The citywide population estimate dipped after 2020, so the honest claim is not "population is exploding today." The harder-to-attack claim is this: Fremont added a 2010-to-2020 growth load, kept adding households and South Fremont job pressure, and still has a commuting system dominated by cars.[18][19][20]
ACS 2024 shows 94.5% of Fremont households have at least one vehicle, 66.1% have two or more, and even counting the "4 or more" category as only four vehicles gives a floor of about 156,000 household vehicles. That household count includes renters and vehicles available to the people living there, including licensed older kids or adult children in the same home. It is conservative twice: every 4+ vehicle household is counted as exactly four, and survey/census counts can miss informal sublets, crowded units, garage/ADU-style living, and people who avoid forms. So the official number is a documented floor, not the real-world ceiling. The same ACS profile shows roughly 73% of workers commute by car/truck/van, while only about 167 workers reported bicycling to work.[19]
That 146,000 hours is not a city-published number. It is a transparent resident estimate: 17,500 added household vehicles x 2 extra minutes/day x 250 weekdays. At 5 minutes each way, the same scale becomes roughly 729,000 vehicle-hours/year. That is why the city's own Mowry admission matters: Fremont already has a model showing a 49.4% AM-peak delay reduction from restoring one right-turn pocket. If the city can calculate delay when it wants to justify a fix, it can publish the same kind of delay math before narrowing or hardening more corridors.[1][19]
Roadscape has published its full Fremont Blvd @ Mowry Ave corridor packet — and a companion corridor report — openly, so other cities can reference the format. They frame this same corridor issue as a review workflow: what is known, what is estimated, what still needs measurement, and where video counts, swept paths, crash data, and field verification fit.[23]
Use it as a public reference layer for the Fremont discussion, not as a substitute for local counts, field verification, or professional review.
Fremont's average commute is already in the same range as major California congestion cities: 32.2 minutes in Fremont, 31.7 in Los Angeles city, 32.2 in San Francisco city, and 27.2 nationally. This is a time comparison, not a mile-for-mile speed comparison, because ACS publishes mean commute time here, not each worker's trip distance. Still, it means Fremont starts about 18% above the U.S. average before the city removes lanes, hardens corners, or adds more South Fremont growth pressure.[22]
Fremont keeps getting ranked as one of America's happiest places to live, including WalletHub-linked 2025 and 2026 coverage putting it at or near No. 1. That makes the traffic question sharper, not softer: if residents choose Fremont for quality of life, the city should not casually trade daily commute time for designs it has not proven made the actual corridors safer.[21]
Here's the precise gap. The city does run before-and-after traffic-operations analysis for its proposed work - that's exactly how it justified restoring the Mowry turn lane (the 49.4% delay cut). What it has never published is a before-and-after CRASH/SAFETY evaluation of the bike-lane corridors it already built - Fremont Blvd, Mowry, Grimmer - showing the redesigns actually reduced collisions on those streets. For safety, it cites only program-wide totals, years apart.
In other words: the one before-and-after the city publishes is about fixing the delay its own design created - not proving the safety projects worked. And it isn't only Fremont - across Boise, Spokane, Fort Collins, Cary, and Chula Vista, none published a corridor-level safety before/after either. The one clean measurement we found, Spokane's Monroe corridor, came back flat: 29 crashes before, 29 after.[3][4]
If these safety projects worked, the crash data exists to prove it. Publish the before-and-after collision results for the Fremont Blvd, Mowry, and Grimmer corridors before approving another dollar of redesign. Modeling the delay on the next project isn't the same as proving the last one made anyone safer.
Fremont's redesigns were sold as a safety investment. Yet across the years its protected-lane network was built out (2020-2024), traffic deaths did not fall - they climbed to 12 in 2024, the city's worst year in over a decade.
Fatal crashes on Fremont city streets, 2014-2025. 2024 = worst recent year (12). 2025* preliminary. Source: City of Fremont, Safety Data & Trends.[5]
We state this carefully, by design. The rise began in 2021, California's pedestrian and cyclist deaths climbed statewide over the same window, and the city attributes its toll to reckless driving and night-time pedestrian crashes rather than lane design - so we do not claim the lanes caused these deaths. But a program sold on safety must be judged on results, and across its rollout Fremont's death toll rose to a multi-year high. At minimum, these redesigns cannot demonstrate they made our corridors safer - and the burden of proof rests with the city, using the corridor-level data it has never published.
Two numbers the program can't get around: cyclists are a sliver of the people dying on Fremont's roads - and a sliver of the people using them.
Share of Fremont traffic fatalities by mode. Source: City of Fremont.[5]
Pedestrians are 45% of deaths; cyclists are 9% - Fremont reports 39 pedestrian fatal crashes, 27 motor-vehicle driver/occupant fatal crashes, 13 motorcyclist fatal crashes, and 8 bicyclist fatal crashes in the 2014-2025 period. Yet the arterial lane-space and grant money went heavily to the smallest fatality group, while the people actually dying most often (pedestrians, often at night) got the least targeted help.
Bike-to-work share - a real cycling city vs Fremont. Sources: U.S. Census ACS / League of American Bicyclists.[15]
Fremont barely bikes, and it's not close: 54% drive alone, 7% carpool, and 32% now work from home - leaving cycling a fraction of one percent. Davis, California - "Bike City USA" - bikes at 17-23% and built its network for that real, large demand. Fremont ran the same disruptive playbook - removed car lanes, 13+ protected intersections, millions of dollars - for a cycling share that rounds to zero.
And demand is shrinking, not growing: U.S. bike commuting peaked in 2014 and fell five straight years, and the share of kids who walk or bike to school collapsed from 48% (1969) to 13% - which is why the bike racks came off the schools. The lanes expanded as the riders vanished.[16]
Proportionality: you don't tear out travel lanes and rebuild intersections for riders who appear a fraction of a percent of the time. And the demand is structural, not a paint problem - Fremont is a large, low-density, spread-out suburb where most trips are simply too far to bike, which is why even transit carries only a small, non-growing share. The city's "build it and they'll come" answer just raises the next question: after years of buildout, where are the ridership counts proving they came? Same as everywhere else here - never published.
Not "do nothing" - match the treatment to the demand: keep standard striped bike lanes, and put the money into shared-use paths and better sidewalks. A fraction of the cost and disruption of removing car lanes and rebuilding intersections. Fremont already does this elsewhere - it striped bike lanes on Paseo Padre Pkwy in 2023 with all four car lanes kept, and its $5.2M Grimmer Blvd Trail puts a separated path in vacant right-of-way without touching a travel lane. The disruptive lane-removals on Fremont Blvd were a choice, not a necessity.
Lane-reduction "road diets" aren't a free lunch. The Federal Highway Administration's own guidance says they belong on roads under about 20,000 vehicles per day - above that, congestion risk is real and a feasibility study is required.
So publish it: what is Fremont Blvd's actual average daily traffic against that line? If it's over, the congestion residents feel isn't imagination - it's exactly what FHWA warns about. The city has the count. Show the public.[6]
Set aside how the lanes started. Here's where they are today: a private company's autonomous robots are approved for the same Fremont corridors residents were told were built for safety.
The bike lanes residents were told were about safety are now part of a private company's delivery corridor. Fremont's own DoorDash Dot page lists Mowry Avenue and Paseo Padre Parkway among proposed primary corridors, says Dot may use bike lanes, and says speeds can reach 16 mph in bike lanes and 20 mph on neighborhood streets. A Feb. 17, 2026 council presentation described a permit request covering bike lanes, sidewalks, and local streets, with primary routes including Walnut Ave, Fremont Blvd, Mowry Ave, Stevenson Blvd, and Paseo Padre Pkwy.[7]
Important caveat: the city page and council presentation do not phrase the speed limits identically, so the clean public ask is simple: publish the final permit, operating plan, crash/incident log, and resident complaint process before expanding beyond the initial pilot.
The loudest gripe - buses and big rigs riding up over the new curbs - isn't just a feeling. It's an engineering mismatch with a paper trail.
The city has already said reduced vehicle lane widths will be used "as feasible" on this corridor work, and residents are reporting the visible result: buses and big rigs clipping or riding over the new hardened corner geometry. The clean engineering question is not a vibe - it is whether the final design still clears the vehicles that actually use Fremont Blvd.
Caltrans' Highway Design Manual is a useful benchmark even where the road is city-owned. It says State-highway lane widths are normally 12 ft, with 11 ft allowed only in limited lower-speed/lower-truck settings, and that curb returns should use the smallest radius that still accommodates the design vehicle. Its intersection guidance says truck/bus swept-path templates or AutoTURN-style software are used to test whether the design vehicle clears the layout; tires may not mount curbs; and turning vehicles should not cross into opposing traffic. That is exactly the document Fremont should publish for Fremont Blvd, Mowry, Grimmer, Beacon, Sundale, and Bidwell.[17]
The resident evidence to collect: photos/video of trucks or buses clipping the curb, exact location, travel direction, time, vehicle type, and, if safe, a few basic dimensions. Measure the vehicle lane at a straight segment, perpendicular from lane line to lane line or curb face to lane line, not including the bike buffer/gutter unless vehicles can legally use it. For the turn, photograph the corner, measure two straight curb legs back from where the curve begins, and measure the chord/offset of the curved curb so the radius can be estimated later. Also measure the corner island offset and the protected-bike-lane curb height if visible. Then the city can answer with the as-built plan sheet and the design-vehicle swept-path overlay instead of hand-waving.
This is the rulebook question Fremont should answer in writing: identify the corridor design vehicle for Fremont Blvd at Mowry Ave, then publish the stamped turning-template or swept-path exhibit showing that vehicle clearing the hardened curb, refuge island, bike-lane protection, crosswalk, and stop-line geometry without mounting the curb or encroaching into opposing traffic.
Use the right standards, not a vague safety slogan. CA-MUTCD governs traffic-control devices, markings, signal features, visibility, channelization, islands, crosswalk markings, and sign/marking conformance. Caltrans HDM and local design standards govern lane width, curb-return geometry, off-tracking, and the design-vehicle turn. AASHTO/agency design-vehicle practice should decide whether the control vehicle is an AC Transit bus, a fire apparatus, a WB-40 style truck, or a larger freight/service vehicle actually using the corridor.[24]
If the city cannot produce that compliance packet, residents are not being asked to trust engineering; they are being asked to trust an assertion.
And the mechanism is concrete: where an open lane lets drivers pull right to clear a path for an ambulance or fire truck, a vertical-separated bike lane takes that room away - and blocks the responder from using it to pass. LA's firefighters' union warned of exactly this: with these designs, "vehicles won't be able to pull over to the right, which would block first responder vehicles."[9]
Honest note: most of this is qualitative because cities rarely publish corridor-level response-time audits before and after these redesigns. That's the point: Fremont should publish fire/EMS response times for its redesigned corridors so the question is answered with numbers, not assumed away.
Asking the city to take a second look isn't anti-bike or radical. Other places have paused, scaled back, or reversed these projects when residents pushed.
Installed downtown bike lanes in 2014 and removed them ~5 weeks later after resident backlash (bus delays, confusion).[12]
Passed a 2025 law restricting lane-narrowing road diets.[12]
Council voted 3-2 in 2023 to scale back its protected bike/bus lane program after 58% of residents opposed it.[13]
We note honestly: most of these reversals were driven by congestion, process, and resident sentiment - not by proof the lanes were statistically deadly. That's the same, fair standard we're asking Fremont to apply.
Piece together the public grant records and the bikeway / protected-intersection program runs into the tens of millions. The visible frame is already roughly $31M+: $17M+ in identified funded projects, plus the city's $14M Country-to-Grimmer corridor now in design. Fremont still publishes no single Vision Zero total, and the lane-removal redesigns themselves never went to a resident vote.
Add it up: over $17 million in the funded projects above - plus the $14 million Country-to-Grimmer corridor now in design - gives residents a $31M+ minimum frame. That is before the Safe & Smart Corridor, Centerville work, and the city's own much larger build-out estimate.
It's public money - local Measure BB taxes plus state and federal grants - and the city won't roll it into one honest number. Itemize the bikeway spend and publish it, especially now that pieces are being rebuilt.[14]
The city can close this debate quickly by publishing the localized files for Fremont Blvd at Mowry Ave. Not citywide averages. Not slogans. The intersection-specific record.
Residents should request the following records under the California Public Records Act, Government Code Division 10, for Fremont Blvd at Mowry Ave and the connected Fremont Blvd redesign limits:[25]
Plain-English test: produce the intersection-specific telemetry and standards packet, or the public record shows the redesign moved forward without the documents needed to prove it.
Nothing extreme. Just measurement, transparency, and a voice - the things a "safety" program should welcome.
Paper claims get stronger when the same problem is filmed repeatedly at known times and places. This appendix is the evidence format residents can use before sending photos, videos, or count clips.
| Timestamp | Exact place / GPS | Vehicle or user | Observed event | Evidence file |
|---|---|---|---|---|
| YYYY-MM-DD HH:MM | Fremont Blvd SB right at Mowry | AC Transit bus / delivery truck / fire apparatus / passenger car / pedestrian / bike | Mounted curb, crossed centerline, blocked through lane, near-miss, long queue, failed turn, pedestrian conflict | Photo, video, count clip, or Roadscape overlay ID |
One clip is an anecdote. Repeated clips showing the same bus, truck, or queue failure at the same geometry become a pattern. A Roadscape swept-path overlay can then compare the as-built corner against the design vehicle and show whether the physical road matches the public promise.
Roadscape can run a free screening-grade corridor check — flow, safety, and real-scale turn geometry — on any Fremont / Newark / Union City street. Tell us the corridor you care about.
Re-Evaluate Fremont's Bike Path Implementation