NYC Subway Trains Might Start Moving Faster
nytimes.com
nytimes.com
https://www.villagevoice.com/2018/03/13/the-trains-are-slowe...
If my memory serves me well, it made a pretty convincing argument that the MTA was deliberately and publicly misconstruing the "slow train problem" as a result of "congestion", effectively blaming the success of the city for the failure of its public transportation. The Voice article rendered this commonly-touted line of defense not just misleading, but flagrantly incorrect.
From my perspective, it seems that the reversal of policy reported now, only came into existence because of the line of investigative reporting that began with the Village Voice piece.
Credit for your commute's speedup probably belongs, at least in part, to the Voice's fantastic investigative reporting (a full 2 months before the linked NYT piece). Even more reason to support your local journalists! :)
> Workers have also started to replace faulty signals that trigger a train’s emergency brakes at low speeds, a problem investigated by The New York Times and The Village Voice that has also led to slower service.
There are almost 100 other possible locations.
The real problem here, as I see it, is that humans are still involved in running the trains. We need speed signs for them to read, we need to hope they follow the rules, we need them to control the train as best a human can. Plenty of cities in the world are running autonomous trains. It's not easy to do, but it is doable. Retrofitting existing trains would be a difficult project, I imagine, but worth the cost.
How much more efficiency could we gain just by shaving those half seconds (or more) at every single start, stop, door open, door close, etc?
I don't even think we need to fire the operators (I'm certain their union would object anyway) so much as change their role to one of managing the autonomous train, providing first aid when needed, keeping a human watch on things.
https://www.nydailynews.com/new-york/automated-train-rolls-a...
It costs hundreds of million of dollars and there were service disruptions for years, often entire weekends to do the work. There was no Uber or Lyft either.
The reason that only the L was improved was that it is largely separate from the rest of the system. There are extremely few rail connections and none that are regularly used.
I'm afraid that computer-driven trains mostly mean no need for people "driving" the trains, and the trade union won't be happy with that.
I'm going to guess you don't commute on the New York subway. :P
Generally, there's two tracks for each direction, one local and one express. You can't shut down just one direction for obvious reasons.
The New York subway is busy enough that shutting down either the local or express track—while better than taking the subways fully out of commission—is a huge pain. When the express track closes, your commute takes twice as long; when the local track closes, your station will likely be bypassed. And in both cases, this makes for overcrowded trains, to the point where you often have to wait for a couple before you're able to board.
(I'm not saying we shouldn't do upgrades, but shutting down a track is indeed very disruptive.)
I'm pro union and worker's right but the MTA definitely fits lot of the negative stereotypes of unions.
Is the MTA different?
Making the entire NYC subway "driverless" would probably cost on the order of hundreds of billions of dollars, if it could be done at all. There are more cost effective ways to reduce dwell times, to use your example.
https://www.newyorker.com/magazine/2018/07/09/can-andy-byfor...
I'm sure part of the problem is that subway workers in NYC are well-paid, but that's probably not all of it.
NYCT workers are well paid, but that is only an explanation for high operating expense, not obscene capital expenses.
Operating expense is really fairly well managed, albeit with unusually high wages. It is a small, small part of the subway’s problems.
Train conductor base pay is $23-30 an hour - the six-figure salaries that you read about are for people doing >40h/week, including night shift/holiday/on-call work.
I generally think that it's reasonable that people who do more work get paid more then people who do less work... Or that people doing the same work during hardship hours get paid more then people doing their 9-5.
[1] https://www.nytimes.com/2017/12/28/nyregion/new-york-subway-...
For those interested in analysis of subway construction costs, I highly recommend Alon Levy's work at Pedestrian Observations: https://pedestrianobservations.com/construction-costs/
[0]https://www.citylab.com/transportation/2018/01/why-its-so-ex...
Does not help that NYC is paying 5-10x that. Given that, the former comment is pretty much in line, even if slightly exaggerated.
A low maximum speed is not what's responsible for the MTA's deteriorating service levels. The problems are mainly signal issues and train malfunctions[0]. To a lesser extent, track fires. This begets the question -- what good is a marginal top speed increase, if so many trains arent reaching their top speed anyways? At least 30% of the time during my rush-hour MTA commute, my train is crawling through the tunnel, well under its current maximum speed. Think tortoise and hare.
Also -- higher max speed might mean harder stops. [0] https://ny.curbed.com/2018/9/17/17869218/nyc-subway-signal-p...
In this article (which you probably also won't be able to read, sorry; try incognito?), the Times explains why some mis-configured time signals are the cause of many delays, with compelling evidence to back up the claim.
https://www.nytimes.com/interactive/2018/05/09/nyregion/subw...
Their other favorite BS excuse it that delays are caused by people holding doors open. But that doesn't hold water either when uncrowded trains still have the doors malfunction and reopen multiple times.
Pre-Byford management seems to have been controlling their burn rate with these shenanigans. Otherwise the system should be able to handle 1948 ridership levels.
Basically, it boils down to heavy consequences for operators that go too fast coupled with systems that measure speed inconsistently.