Fairfax County proposes June 2026 Fairfax Connector schedule refinements; two low-ridership routes to be discontinued
Loading...
Summary
Fairfax County Department of Transportation outlined proposed June 2026 Fairfax Connector service changes including frequency and span adjustments on multiple routes, the discontinuation of Routes 552 and 622 for low ridership, and a Title 6 disparate-impact finding for Route 642 with mitigation to retain limited midday service.
Fairfax County Department of Transportation officials on Feb. 24 presented proposed June 2026 changes to the Fairfax Connector bus network that would adjust schedules on numerous routes, discontinue two low-ridership services and retain limited service where civil‑rights impacts were identified.
Christian Desai of the FCDOT planning team said the package of changes is designed "to improve system efficiency and resource allocation, resulting in the improvement of the system on time performance and reliability." The proposal covers routes including 101, 109, 335, 401, 402, 432, 461, 463, 552, 553, 615, 622, 625, 642, 924, 950 and 983.
Among the most consequential proposals, staff recommended discontinuing Routes 552 and 622 because of low ridership and listed alternative routes riders could use where service is removed. Several routes would see weekday frequency or runtime adjustments; for example, Route 101 would keep its existing span (4:26 a.m. to 11:53 p.m.) but move non‑rush headways from 30 to 35 minutes, and Route 625 would be reduced to midday service (9:00 a.m.–1:52 p.m.). Staff said Route 401 and 402 together remain one of the system's highest‑ridership corridors, with Route 401 carrying "almost 12% of our weekday ridership," and that changes there are intended to improve on‑time performance while preserving service coverage.
Weekend adjustments included eliminating Sunday service on Route 615 and ending weekend service on Route 642 (staff said those moves are driven by low weekend boardings), while Route 983 would receive improved weekend frequency and the Dulles stop at the airport would be formalized at Kiss‑and‑Fly Parking Garage 1.
FCDOT also described a Title 6 analysis conducted for the proposals. Desai said "for the proposed changes on Route 642, a disparate impact was identified," and that the department's stated mitigation is to retain limited midday service on that route to maintain access and mobility for protected populations.
The presentation closed with staff inviting live questions and public comments. Resident commenter Zoltan (Mister Bundix) urged extending Route 574 to Tysons Metro, requested earlier weekend service and flagged bus‑stop maintenance issues (missing stop flags and uneven boarding pads). Anthony, a Fairfax Connector driver who grew up in Reston, praised the system but argued Route 552's current alignment duplicates service along the same streets and urged planners to redesign overlapping routes so a single route carries riders to destinations such as Innovation Center.
Kyle, a member of the FCDOT planning staff, thanked commenters and said staff will "evaluate your request" and will pursue facility questions with the appropriate teams. Planners noted ongoing engagement opportunities for operators, including quarterly garage visits and monthly joint planning/operations coordination meetings, as ways for drivers to provide front‑line operational feedback.
No final board action occurred at the meeting. Desai said staff anticipate finalizing changes, seeking board approval and implementing service during 2026. The department encouraged written comments through its public input page, by phone at (703) 339‑7200, by mail to Fairfax County Department of Transportation, Attention: Transit Planning — Proposed June 2026 Service Changes, Fairfax Connector, 4050 Legato Road, Fairfax, VA 22033, or by TTY at (703) 339‑1608. Written comments are being accepted through March 1, 2026.
Next steps: FCDOT will review public input, continue operator engagement, finalize recommended changes and present them to the county board for approval before implementing any service adjustments.

