Report a Comment

There's a simpler answer to Stephen's question about bunching: Generally, DC Metro bus drivers don't adhere to schedules. Certainly busses can be late when they hit very busy periods and unexpected surges in ridership, but those can also be monitored and adjustments made to schedules and vehicle assets over time to minimize that impact.

What's happening here is that bus drivers generally drive their routes as fast as they can, often catching up to each other or passing each other on their routes. I've ridden other major city bus systems where drivers stop and wait at a stop to stay on their schedule. It can be frustrating for riders in a rush, but it is the only practical way to maintain spacing and avoid 3-4 buses arriving at once, followed by an extended wait.

I haven't had the chance to ask the question at a public forum, but it seems like there is some kind of consensus among the metro community that on balance we'd rather have the buses drive as fast as they can once we're on them rather than adhere to schedules. If that's not the majority preference among riders then more of you have to complain, because that's the core cause of the problem.

The NextBus system has done a lot to reduce the impact of DC's 'fast-as-you-can' approach to Metro asset management, but it still amazes me when a packed 32 arrives in Glover Park, followed in the same block by two empty 36s and a medium-full 31. What a silly waste of energy and resources.

by JF_DC on Sep 9, 2011 1:19 pm • link • report