Category: New York

The Politics of QueensLink

The abandoned right-of-way of the Rockaway Cutoff, or Rockaway Beach Branch, is an attractive target for reuse by some groups. Area railfans have wanted to do something with it for years, and I was mostly negative about these plans, but more recently, QueensLink has emerged as a serious plan to extend the subway along the Rockaway Cutoff, to connect neighborhoods in southwestern Queens to one another and to Manhattan, where current connections do not exist (in the middle) or only serve Midtown Manhattan indirectly and slowly (in the south, via the A train). The right-of-way is wide enough that most of it can also accommodate additional infrastructure, in the case of this plan a bike trail.

The problem is that this more serious plan is still not getting much political play. This is not because of the typical reasons people may think of, such as high costs or NIMBYism. Rather, a competing plan for the same corridor, Queensway, wants to turn it into pure parkland, and is backed by a power broker with opinions and connections. The QueensLink advocates have asked for and been so far refused planning money for an environmental impact statement, which step is in better infrastructure environments apolitical; instead, Mayor Eric Adams is connected with a Queensway backer and thus favors Queensway.

The QueensLink project

QueensLink is a subway extension, with a short tunnel to get from the Queens Boulevard Line’s local tracks to the Rockaway Cutoff. Where there is room, a bike trail is included on the same corridor.

As this is a former rail mainline, the connections to the crossing subway lines are not great – the subway placed stations at major street intersections, leading to long walks at the Jamaica and Liberty Avenue transfers. In contrast, the connection to the LIRR is good: there is no station there today, but there used to be one, and it could be reopened, especially now that the Atlantic Branch is retooling to be more useful for urban service, with more stops, higher frequency, and perhaps integrated fares.

The subway connection makes this proposal viable. I previously criticized a proposal to run commuter rail service on the Cutoff, since it would crowd out the busy LIRR Main Line. In contrast, QueensLink has the new branch using the Queens Boulevard local tracks, which are undersubscribed even at rush hour, to the point that it may even be possible to run three rush hour services on the same tracks and not just two like today. The G doesn’t run to Forest Hills, for good reason, but the new service would vacate space at the Forest Hills terminal of the local tracks to the point that it could potentially be viable.

At the Transportation and Land Use program at Marron, we’re building tools to estimate not just costs for public transit construction but also ridership, and it’s likely that QueensLink will be next on our agenda right after the Interborough Express. I can’t give more than first-order estimates now, but it’s notable that the closest parallel bus corridor, Woodhaven, has high ridership: it carries four local or SBS routes and four express routes, with 31,000 weekday boardings among them. Then there’s the possibility of faster service to JFK Airport via QueensLink. It’s not going to be the Second Avenue Subway of Queens by ridership, but because only a short tunnel is needed, it’s not going to come close to Second Avenue Subway in costs either.

QueensLink and Queensway

The alternative to QueensLink isn’t doing nothing, as is usually the case. Some political players have eyed the corridor for a trail project called Queensway. The idea of Queensway is to create more parkland in the area, including a hiking and bike trail; as the map above shows, there is no shortage of parkland there. There’s an obsession of urbanists in the United States with linear parks, in imitation of the High Line; one attempt at imitation even wanted to build a park underground in a former streetcar terminal and called it the Lowline.

I want to dwell on the politics of Queensway, because I know I have a lot of readers in the general neoliberal and rationalist communities, including specifically in New York, and the political support for it is not what their first instinct might be.

Often, it’s the case that public transit projects are supported by broadly developmentalist interest groups, who are also fairly YIMBY, and tend to be rooted in professionals and office workers commuting to city center, and opposed by NIMBYs, who tend to be rooted in longstanding neighborhood residents and small business owners. Neighborhood NIMBYs often like parks, because they’re local improvements; when we studied the Green Line Extension in Boston, we saw some local interest groups demand money for a trail as a precondition to supporting the light rail line.

And this is not at all what is happening with the Rockaway Cutoff. Local interest groups are not consistently anti-QueensLink and pro-Queensway. Some are, but in at least one case, a local advocate came to argue on NIMBY grounds against Queensway, which would bring pedestrians to their backyard, and for QueensLink, since the passing train would not cause unwanted impact and would serve the area. On net, YIMBYer groups are more pro-QueensLink – for example much of the community at the northern end of the corridor, in Community Board 6, which due to its location on the subway has a more pro-transit and pro-development orientation. But it doesn’t boil down to these class interests pitting professional workers against small business owners, at all. Rather, it’s rather random, boiling down to individual power brokers for Queensway.

What autocrats want

I highlight the randomness of the interest groups for Queensway, because it relates to the broadly autocratic style of some leaders, who the de facto system of government in New York empowers too much. In the 2010s, Andrew Cuomo liked the idea of Queensway, and if he wanted something, anyone who wanted to stay in the good grace of the local power system had to support it. The backward air train to LaGuardia, hated by transit activists in the city from the start, is such an example – while Cuomo was in power opposition was restricted to people outside city and state politics, like the technical advocacy community or Alexandria Ocasio-Cortez. Then Cuomo left office and because nobody really wanted it, this project died. Queensway survives, I think partly because it’s not a multi-billion dollar investment, and partly because some power brokers do like it and have attached themselves to Mayor Eric Adams, such as political operative and lobbyist Travis Terry.

The point of this is not that Adams wants Queensway and therefore it will happen. Rather, it’s that, in a system with a democratic deficit like New York, professional decisions often boil down to which random advocate happens to have the ear of the autocrat. I keep contrasting this with the situation in Berlin, in which bike lanes and pedestrianization have been put on hold and even been reversed under Mayor Kai Wegner (CDU) – but Wegner ran on this agenda in the election and CDU came first, and the pivotal party, SPD, chose to enter a coalition with him and not with more left-wing parties under a known-quantity (and disgraced) leader in Franziska Giffey, whose conservative-for-SPD politics and poor relationship with the left was well-known. I dislike this outcome, but voters knew what they were getting. In contrast, in New York, Adams did not run on any explicit agenda of not building public transit, or even on support for interest groups that oppose transit (again, the Queensway support is more individualized than neighborhood-scale NIMBYs). He just makes abrupt decisions, often sniping the judgment of the city’s own civil service, based on what one favorite asks.

The way forward

In healthy infrastructure construction systems and also in Germany, the planning is not politicized; the yes/no decision on what to build must be made by politicians, but the menu of options with their costs and benefits is prepared by the civil service. In contrast, in the United States, even the choice of which projects get an environmental impact study is politicized; QueensLink advocates are asking for money for an EIS, which in the United States is where planning is done, but even that is stalled politically.

The problem is that the message this behavior by the city and state sends is that New York is too messed up to invest in. Private actors who make investment decisions need some amount of political stability and predictability. A political culture of caprice, in which everyone must constantly follow political gossip to have any idea what the autocratic mayor or governor (or in some countries president or prime minister) will do, or else be swamped by otherwise inexplicable investment decisions, screams “go elsewhere, we don’t want you.” Even turning an EIS into a big political ask screams the same thing: “we can’t do, so merely studying is an achievement by itself and you must pay fealty.”

New York’s current system deters investment, not through taxes or union empowerment, but through opacity and unpredictability. I don’t want to turn the question of one right-of-way in Queens into an existential issue that it is not, but on the margin, stonewalling on QueensLink because some politically connected actor personally wants Queensway reinforces this system that repels investment, whereas treating the EIS as an apolitical step and then based on the results of further planning building it or not based on broad interest agreement signals that New York can and wants to build things. It’s the city’s choice.

The Future of Congestion Pricing in New York

New York just passed congestion pricing, to begin operation on June 30th. The magazine Vital City published an issue dedicated to this policy two days ago; among the articles about it is one by me, about public transportation investments. People should read the entire article; here I’d like to both give more context and discuss some of the other articles in the issue. Much of this comes from what I said to editor Josh Greenman when discussing the pitch for the piece, and how I interpret the other pieces in the same context. The most basic point, for me, is that what matters is if the overall quality of public transit in and around New York is seen to improve in the next 5-10 years. In particular, if congestion pricing is paired with one specific thing (such as a new subway line) and it improves but the rest of the system is seen to decline, then it will not help, and instead people will be cynical about government actions like this and come to oppose further programs and even call for repealing the congestion tax.

The other articles in the issue

There are 10 articles in this issue. One is my own. Another is by Josh, explaining the background to congestion pricing and setting up the other nine articles. The other eight were written by John Surico, Sam Schwartz, Becca Baird-Remba, Austin Celestin, Howard Yaruss, Nicole Gelinas, Vishaan Chakrabarti, and Henry Grabar, and I recommend that people read all of them, for different perspectives.

The general themes the nine of us have covered, not all equally, include,

  • How to use congestion pricing to improve transportation alternatives (me on transit investment, Yaruss on transit fare cuts, Nicole and Chakrabarti on active transportation, Henry on removing parking to improve pedestrian safety).
  • The unpopularity of congestion pricing and what it portends (Surico about polling, Becca about business group opposition, Schwartz on political risk, Yaruss again on why the fare cut is wise); of note, none of the authors are coming out against congestion pricing, just warning that it will need to deliver tangible benefits to remain popular, and Surico is making the point that in London and Stockholm, congestion pricing was unpopular until it took effect, after which it was popular enough that new center-right leadership did not repeal it.
  • Environmental justice issues (Becca and Celestin): my article points out that traffic levels fell within the London congestion zone but not outside it, and Becca and Celestin both point out that the projections in New York are for traffic levels outside the zone not to improve and possibly to worsen, in particular in asthma-stricken Upper Manhattan and the Bronx, Celestin going more deeply into this point and correctly lamenting that not enough transit improvements are intended to go into these areas. The only things I can add to this are that for environmental justice, two good investment targets include a 125th Street subway tunnel extending Second Avenue Subway and battery-electric buses at depots to reduce pollution.
  • Problems with toll evasion (Schwartz and Yaruss): there’s a growing trend of intentional defacement of license plates by the cars’ own drivers, to make them unreadable by traffic camera and avoid paying tolls, which could complicate revenue collection under congestion pricing.

The need for broad success

When discussing my article with Josh, before I wrote it, we talked about the idea of connecting congestion pricing to specific improvements. My lane would be specific transit improvements, like new lines, elevator access at existing stations, and so on, and similarly, Nicole, Henry, Chakrabarti, and Yaruss proposed their own points. But at the same time, it’s not possible to just make one thing work and say “this was funded by congestion pricing.” The entire system has to both be better and look better, the latter since visible revenue collection by the state like congestion pricing or new taxes are always on the chopping block for populist politicians if the state is too unpopular.

The example I gave Josh when we talked was the TGV. The TGV is a clear success as transportation; it is also, unlike congestion pricing, politically safe, in the sense that nobody seriously proposes eliminating it or slowing it down, and the only controversy is about the construction of new, financially marginal lines augmenting the core lilnes. However, the success of the TGV has not prevented populists and people who generally mistrust the state from claiming that things are actually bad; in France, they are often animated by New Left nostalgia for when they could ride slow, cheap trains everywhere, and since they were young then, the long trip times and wait times didn’t matter to them. Such nostalgics complain that regional trains, connecting city pairs where the train has not been competitive with cars since mass motorization and only survived so long as people were too poor to afford cars, are getting worse. Even though ridership in France is up, this specific use case (which by the 1980s was already moribund) is down, leading to mistrust. Unfortunately, while the TGV is politically safe in France, this corner case is used by German rail advocates to argue against the construction of a connected high-speed rail network here, as those corner case trains are better in Germany (while still not carrying much traffic).

The most important conclusion of the story of the TGV is that France needs to keep its high-speed system but adopt German operations, just as Germany needs to adopt French high-speed rail. But in the case of New York, the important lesson to extract is that if the MTA does one thing that I or Nicole or Henry or Chakrabarti or Yaruss called for while neglecting the broad system, people will not be happy. If the MTA builds subway lines with the projected $1 billion a year in revenue, politicians will say “this subway line has been built with congestion pricing revenue,” and then riders will see declines in reliability, frequency, speed, and cleanliness elsewhere and learn to be cynical of the state and oppose further support for the state’s transit operations.

The MTA could split the difference among what we propose. As I mentioned above, I find Celestin’s points about environmental justice compelling, and want to see improvements including new subways in at-risk areas, bus depot electrification to reduce pollution, and commuter rail improvements making it usable by city residents and not just suburbanites (Celestin mentions frequency; to that I’ll add fare integration). Nicole, Henry, and Chakrabarti are proposing street space reallocation, which doesn’t cost much money, but does cost political capital and requires the public to be broadly trusting of the state’s promises on transportation. The problem with doing an all-of-the-above program is that at the end of the day, projected congestion pricing revenue is $1 billion a year and the MTA capital program is $11 billion a year; the new revenue is secondary, and my usual bête noire, construction costs, is primary.

Subway Expansion and Bus Redesign

The ongoing designs for the Interborough Express are making me think about bus redesign again. Before the Transit Costs Project, Eric and I worked on a proposal for a bus redesign in Brooklyn, which sadly was not adopted. The redesign was based on the reality of 2017 – the ridership patterns, the bus speeds, the extent of the system, etc. Since then the subway map has not changed, but IBX stands to change the map, and with it, the buses should change as well.

With our program having produced both the bus redesign proposal and soon a comprehensive proposal for how to change the city’s built-up layout to take advantage of the new line, I should probably say something about how the buses should change. I say I and not we, because so far we don’t have a project under our program for this; for now, this is just a blog post, though one informed by past work on the subject.

Parallel and orthogonal buses

In general, when a new line opens, it reduces demand on parallel bus routes, which it outcompetes, and increases it on orthogonal ones, which feed it. However, what counts as parallel and what counts as orthogonal are not always obvious.

Case in point: when Second Avenue Subway opened at the end of 2016, ridership on the east-west buses between the Upper East and West Sides fell. The new line in theory runs north-south, but it undulates from the Upper East Side to Times Square, where passengers can connect to trains to the Upper West Side and points north; when I lived at 72nd and York and commuted to Columbia by bus and subway in 2009-10, I calculated that if Second Avenue Subway had been open already, a two-seat subway ride with a Times Square connection would have cut my one-way commute from 50 to 37 minutes.

This means that to understand how a new rail line will impact buses, it’s necessary to look beyond just the line itself, and think what it connects to.

For example, note on the above map that the increase in job access at the Flatbush Avenue station, intersecting the Nostrand Avenue Line, is relatively small, and doesn’t have a big north-south footprint along Nostrand. This is because the location already has subway service connecting to Manhattan, a much larger job center than anything IBX would connect to; the buses at the station, the B41 on Flatbush and B44 on Nostrand, already function as connectors to the subway at this point, and are unlikely to acquire more ridership as a result.

In contrast, the stations at Myrtle and Metropolitan are both seen to have a large increase in job access, and in particular a large increase in job access along those two avenues even somewhat away from the stations. On Myrtle, the current buses are the B54 and Q55; the B54 connects to the M train, but it’s one branch, and then the bus continues to Downtown Brooklyn, to which there’s no good subway connection from the future IBX station. The B54 is likely to lose ridership to Downtown Brooklyn but gain it to the new IBX station, and the Q55 is likely to gain in general, as they ferry passengers to a station where they can quickly and with one change go to any number of express lines. Metropolitan has a similar issue – the Q54 already connects to the M, but at least from points west, nobody has any reason to make that connection since it would just double back, whereas with IBX, the Q54 would efficiently connect people to Jackson Heights, and with an additional change to anywhere on the Queens Boulevard and Flushing Lines.

New nodes

Public transit lines serve two functions: to run along a corridor, and to connect nodes. New York usually thinks in terms of corridors, and indeed names nearly all subway lines after the streets they run on (such as a Manhattan avenue) rather than after where they go. But nodes are important as well. Some of that is reflected in the above analysis of the Flatbush-Nostrand Avenue station, currently Brooklyn College on the Nostrand Avenue Line: it really needs to be thought of as a node, and IBX will strengthen it, but not by enough to require running more B41 and B44 buses. In contrast, other nodes will be strengthened enough that bus service increases are warranted.

East New York/Broadway Junction is the biggest standout. East New York’s bus network today is not much of a grid – instead, buses connect outlying areas to the nearest subway station; the bus redesign we did for Brooklyn would make it more of a grid but still follow the logic of feeding the subway wherever it is closest. However, IBX makes Broadway Junction and the Atlantic Avenue station more interesting, which should leads to some changes, turning the new station into more of a node for buses. Buses avoiding this node should instead make sure to stop not just at the subway but also at a new IBX stop, such as Linden.

Jackson Heights is the other. It is a node to some extent today, served by the Q32, Q33, Q47, Q49, Q53, and Q70. But in that general area, the intersection of Woodhaven and Queens Boulevard is an even larger node, and in Queens writ large, the ends of the subway in Jamaica and Flushing are far and away the biggest ones. With IBX, more buses should run to Jackson Heights; for example, all Woodhaven buses, and not just the Q53, should continue along Queens Boulevard and Broadway to reach the station.

Substitutions

In Queens, the street network connecting Jackson Heights with the neighborhoods near the borough line with Brooklyn is not at all conducive for good transit. Buses are usually a good indicator of relative demand along a corridor, but sometimes they aren’t; the situation of IBX is generally one in which they are not, but this is especially bad in Queens. This means that the question of which buses would see demand fall as IBX substitutes for them is even harder than on Second Avenue Subway, the north-south line that efficiently substitutes for east-west buses.

In Brooklyn, I think the answer is relatively straightforward, in that the main crosstown routes, like the B35 on Church, exhibit substitutability. In Queens, it’s harder, and I don’t have concrete answers, only general thoughts that we can turn into a report if there turns out to be demand for it:

  • If a bus has sections along the corridor but also away from it, like the Q18 or Q47, then it should be cut to just connect to the line, in these two case at Jackson Heights.
  • If a bus runs directly between two nodes that could get faster service via a subway-IBX connection, and it doesn’t serve much along the way, then it’s likely to be analogous to the east-west buses across Central Park, and see reduced ridership demand.
  • In general, the routes in Central Queens zigzag so much that IBX is likely to represent a massive improvement in trip times, making such buses less useful.

Frequency in Units of Distance

I have annoying commenters. They nitpick what I say and point out errors in my thinking – or if there are no errors, they take it beyond where I thought it could be taken and find new ways of looking at it. After I wrote about frequency relative to trip length last week, Colin Parker pointed out on the Fediverse that this can be simplified into thinking about frequency not in units of time (trains or buses per hour), but in units of distance (trains or buses per km of route). This post is dedicated to developing this idea on various kinds of transit service, including buses and trains.

The key unit throughout, as Colin points out, is the number of buses available per route, the assumption being that the average trip length is proportional to the average route length. However, this is not a perfect assumption, because then the introduction of network effects changes things – generally in the direction of shorter average trip length, as passengers are likelier to transfer, in turn forcing agencies to run more vehicles on a given route to remain useful. Conversely, timed transfers permit running fewer vehicles, or by the same token more routes with the same resources – but the network had better have a strong node to connect to after a series of vehicle changes, more like the Swiss rail network than like a small American city’s bus network.

Frequency and resources

On a bus network with even frequency across all routes, the following formula governs frequency, as I discussed six years ago:

Daily service hours * average speed per hour = daily trips * network length

When Eric and I proposed our Brooklyn bus redesign, we were working with a service-hour budget of about 10,800 per weekday; status quo as of 2017-8 was 11 km/h, 550 km, and thus 216 daily trips (108 per direction), averaging around a bus per 11 minutes during the daytime, while we were proposing speed up treatments and a redesign to change these figures to 15 km/h, 355 km, and thus 456 daily trips (228 per direction). The six-minute service ideal over 16 hours requires 188 trips per direction; the difference between 188 and 228 is due to higher frequencies on the busiest routes, which need the capacity.

To express this in units of length, we essentially eliminate time from the above dimensional analysis. Daily service hours is a dimensionless quantity: 10,800 hours per weekday means 450 buses circulating at a given time on average, in practice about 570 during the daytime but not many more than 100 buses circulating overnight. If there are 570 buses circulating at a given time, then a 550 km network will average a bus every 1.9 km and a 355 km one will average a bus every 1.25 km. With pre-corona New York bus trips averaging 3.4 km unlinked, a bus every 1.9 km means the maximum headway is a little higher than half the trip time, and a bus every 1.25 km means the maximum headway is a little higher than one third the trip time, independently of speed.

This calculation already illustrates one consequence of looking at frequency in units of distance and not time: your city probably needs to aggressively prune its bus network to limit the wait times relative to overall trip times.

Route length and trip length

On an isolated bus or train route, serving an idealized geography with a destination at its center and isotropic origins along the line, the average trip length is exactly one quarter of the route length. The frequency of service in units of distance should therefore be one eighth of the route length, requiring 16 vehicles to run service plus spares and turnarounds. This is around 18-20 vehicles in isolation, though bear in mind, the 10,800 service hours/day figure for Brooklyn buses above is only for revenue service, and thus already incorporates the margin for turnaround times and deadheads.

Colin points out that where he lives, in Atlanta, bus routes usually have around four vehicles circulating per route at a given time, rather than 16. With the above assumptions, this means that the average wait is twice the average trip time, which goes a long way to explaining why Atlanta’s bus service quality is so poor.

But then, different assumptions of how people travel can reduce the number 16:

  1. If destinations are isotropic, then the average trip length rises from one quarter of the route length to 3/8 of the route length, and then the frequency should be 1.5/8 of the route length, which requires 11 vehicles in revenue service.
  2. If origins are not isotropic, then the average trip length can rise or fall, depending on whether they are likelier to be farther out or closer in. A natural density gradient means origins are disproportionately closer-in, but then in a city with a natural density gradient and only four buses to spare per route, the route is likely to be cut well short of the end of the built-up area. If the end of the route is chosen to be a high-density anchor, then the origins relative to the route itself may be disproportionately farther out. In the limiting case, in which the average trip is half the route length, only eight buses are needed to circulate.

To be clear, this is for a two-tailed route; a one-tailed route, connecting city center at one end to outlying areas at the other, needs half the bus service, but then a city needs twice as many such routes for its network.

The impact of transfers

Transfers can either reduce the required amount of service for it to be worth running or increase it, depending on type. The general rule is that untimed transfers occurring at many points along the line reduce the average unlinked trip and therefore force the city to run more service, while timed transfers occurring at a central node lengthen the effective trip relative to the wait time and therefore permit the city to run less service. In practice, this describes both how existing bus practices work in North America, and even why the Swiss rail network is so enamored with timed connections.

To the point of untimed transfers, their benefit is that there can be very many of them. On an idealized grid – let’s call it Toronto, or maybe Vancouver, or maybe Chicago – every grid corner is a transfer point between an east-west and a north-south route, and passengers can get from anywhere to anywhere. But then they have to wait multiple times; in transit usage statistics, this is seen in low average unlinked trip lengths. New York, as mentioned above, averages 3.4 km bus trips, with a network heavily based on bus-subway transfers; Chicago averages a not much higher 3.9 km. This can sort of work for New York with its okay if not great relative frequency, and I think also for Chicago; Vancouver proper (not so much its suburbs) and Toronto have especially strong all-day frequencies. But weaker transit networks can’t do this – the transfers can still exist but are too onerous. For example, Los Angeles has about the same total bus resources as Chicago but has to spread them across a much larger network, with longer average trip times to boot, and is not meaningfully competitive. The untimed grid, then, is a good feature for transit cities, which have the resources and demand to support the required frequencies.

Not for nothing, rapid transit networks love untimed transfers, and often actively prefer to spread them across multiple stations, to avoid overwhelming the transfer corridors. Subways are only built on routes that are strong enough to have many vehicles circulating, to the point that all but the shortest trips have low ratios of wait to in-vehicle times. They are also usually radial, aiming to get passengers to connect between any pair of stations with just one transfer; Berlin, Paris, and New York are among the main exceptions. These features make untimed transfers tolerable, in ways they aren’t on weaker systems; not for nothing, a city with enough resources for a 100 km bus network and nothing else does not mimic a 100 km subway network.

Timed transfers have the opposite effect as untimed transfers. By definition, a timed transfer means the wait is designed to be very short, ideally zero. At this point, the unlinked trip length ceases to be meaningful – the quantity that should be compared with frequency is the entire trip with all timed transfers included. In particular, lower frequencies may be justifiable, because passengers travel to much more than just the single bus or rail route.

This can be seen in small-city American bus networks, or some night bus networks, albeit not with good quality. It can be seen much more so on transfer-based rail networks like Switzerland’s. The idealized timed transfer network comprises many routes all converging on one node where they are timed to arrive and depart simultaneously, with very short transfers; this is called a knot in German transit planning and a pulse in American transit planning. American networks like this typically run a single bus circulating on each one-tailed route; the average wait works out to be four times longer than the average unlinked trip, and still twice as long as a transfer trip, which helps explain why ridership on such networks is a rounding error, and this system is only used for last-resort transportation in small cities where transit is little more than a soup kitchen or on night bus networks that are hardly more ridden. It would be better to redo such networks, pruning weaker routes to run more service on stronger ones, at least two per one-tailed route and ideally more.

But then the Swiss rail network is very effective, even though it’s based on a similar principle: there’s no way to fill more frequent trains than one every hour to many outlying towns, and even what are midsize cities by Swiss standards can’t support more than a train every half hour, so that many routes have a service offer of two to four vehicles circulating at a given time. However, on this network, the timed transfers are more complex than the idealized pulse – there are many knots with pulses, and they work to connect people to much bigger destinations than could be done with sporadic one-seat rides. A succession of timed connections can get one from a small town in eastern Switzerland to St. Gallen, then Zurich, then Basel, stretching the effective trip to hours, and making the hourly base frequency relatively tolerable. The key feature is that the timed transfers work because while individual links are weak enough to need them, there are some major nodes that they can connect to, often far away from the towns that make the most use of the knot system.

Local and Intercity Rail are Complements

An argument in my comments section is reminding me of a discussion by American transit advocates 15 years ago, I think by The Overhead Wire, about the tension between funding local transit and high-speed rail. I forget who it was – probably Jeff Wood himself – pointing out that the argument in 2008-9 about whether the priority was local transit or intercity rail didn’t make much sense. There are separate questions of how to allocate funding for intercity transportation and how to do the same for local transportation, and in both cases the same group of activists can push for a more favorable rail : car funding ratio. Jeff was talking about this in the sense of political activism; the purpose of this post is to explain the same concept from the point of view of public transportation connectivity and network effects. This is not an obvious observation, judging by how many people argue to the contrary – years ago I had a debate with Noah Smith about this, in which he said the US shouldn’t build high-speed rail like the Shinkansen before building urban rail systems like those of Japanese cities (see my side here and here).

I’ve written about related issues before, namely, in 2022 when I recommended that countries invest against type. For example, France with its TGV-centric investment strategy should invest in connecting regional lines, whereas Germany with its hourly regional train connections should invest in completing its high-speed rail network. It’s also worthwhile to reread what I wrote about Metcalfe’s law for high-speed rail in 2020, here and here. Metcalfe’s law is an abstract rule about how the value of a network with n nodes is proportional to n^2, and Odlyzko-Tilly argue strongly that it is wrong and in fact the value is n\log n; my post just looks at specific high-speed rail connections rather than trying to abstract it out, but the point is that in the presence of an initial network, even weaker-looking extensions can be worth it because of the connections to more nodes. Finally, this builds on what I said five days ago about subway-intercity rail connections.

The combined point is that whenever two forms of local, regional, or intercity public transportation connect, investments in one strengthen the case for investments in the other.

In some edge cases, those investments can even be the same thing. I’ve been arguing for maybe 12 years that MBTA electrification complements Northeast Corridor high-speed rail investment, because running fast electric multiple units (EMUs) on the Providence Line and its branches instead of slow diesel locomotive-hauled trains means intercity trains wouldn’t get stuck behind commuter trains. Similarly, I blogged five years ago, and have been doing much more serious analysis recently with Devin Wilkins, that coordinating commuter rail and intercity rail schedules on the New Haven Line would produce very large speed gains, on the order of 40-45 minutes, for both intercity and commuter trains.

But those are edge cases, borne of exceptionally poor management and operations by Amtrak and the commuter railroads in the Northeast. Usually, investments clearly are mostly about one thing and not another – building a subway line is not an intercity rail project, and building greenfield high-speed rail is not a local or regional rail project.

And yet, they remain complements. The time savings that better operations and maintenance can produce on the New Haven Line are also present on other commuter lines in New York, for example on the LIRR (see also here, here, and here); they don’t speed up intercity trains, but do mean that people originating in the suburbs have much faster effective trips to where they’d take intercity rail. The same is true for physical investments in concrete: the North-South Rail Link in Boston and a Penn Station-Grand Central connection in New York both make it easier for passengers to connect to intercity trains, in addition to benefits for local and regional travel, and conversely, fast intercity trains strengthen the case for these two projects since they’d connect passengers to better intercity service.

Concretely, let’s take two New York-area commuter lines, of which one will definitely never have to interface with intercity rail and one probably will not either. The definitely line is the Morristown Line: right now it enters New York via the same North River Tunnels as all other trains from points west, intercity or regional, but the plan for the Gateway Tunnel is to segregate service so that the Morris and Essex Lines use the new tunnel and the Northeast Corridor intercity and commuter trains use the old tunnel, and so in the future they are not planned to interact. The probably line is the LIRR Main Line, which currently doesn’t interface with intercity trains as I explain in my post about the LIRR and Northeast Corridor, and which should keep not interfacing, but there are Amtrak plans to send a few daily intercities onto it.

Currently, the trip time from Morristown to New York is around 1:09 off-peak, with some peak-only express trains doing it in 1:01. With better operations and maintenance, it should take 0:47. The upshot is that passengers traveling from Morristown to Boston today have to do the trip in 1:09 plus 3:42-3:49 (Acela) or 4:15-4:35 (Regional). The commuter rail improvements, which other than Gateway and about one unfunded tie-in do not involve significant investment in concrete, turn the 4:51 plus transfer time trip to 4:29 plus transfer time – say 5 hours with the transfer, since the intercities run hourly and the transfers are untimed and, given the number of different branches coming in from New Jersey, cannot be timed. High-speed rail, say doing New York-Boston in 2 hours flat (which involves an I-95 bypass from New Haven to Kingston but no other significant deviations from the right-of-way), would make it 2:47 with a transfer time capped at 10 minutes, so maximum 2:57. In effect, these two investments combine to give people from Morristown an effective 41% reduction in trip time to Boston, which increases trip generation by a factor of 2.87. Of course, far more people from Morristown are interested in traveling to New York than to Boston, but the point is that in the presence of cheap interventions to rationalize and speed up commuter rail, intercity rail looks better.

The same is true from the other direction, from the LIRR Main Line. The two busiest suburban stations in the United States are on 2000s and 10s numbers Ronkonkoma and Hicksville, each with about 10,000 weekday boardings. Ronkonkoma-Penn Station is 1:18 and Hicksville-Penn Station is 0:42 off-peak; a few peak express trains per day do the trip a few minutes faster from Ronkonkoma by skipping Hicksville, but the fastest looks like 1:15. If the schedule is rationalized, Ronkonkoma is about 0:57 from New York and Hicksville 0:31, on trains making more stops than today. I don’t have to-the-minute New York-Washington schedules with high-speed rail yet, but I suspect 1:50 plus or minus 10 minutes is about right, down from 2:53-3:01 on the Acela and 3:17-3:38 on the Regional. So the current timetable for Ronkonkoma-Washington is, with a half-hour transfer time, around 4:45 today and 2:57 in the future, which is a 38% reduction in time and a factor of 2.59 increase in the propensity to travel. From Hicksville, the corresponding reduction is from 4:09 to 2:31, a 39% reduction and a factor of 2.72 increase in trip generation. Again, Long Islanders are far more interested in traveling to Manhattan than to Washington, but a factor of 2.59-2.72 increase in trip generation is nothing to scoff at.

The issue here is that once the cheap upgrades are done, the expensive ones start making more sense – and this is true for both intercity and regional trains. The New York-Boston timetable assumes an I-95 bypass between New Haven and Kingston, saving trains around 24 minutes, at a cost of maybe $5 billion; those 24 minutes matter more when they cut the trip time from 2:24 to 2:00 than when the current trip time is about 3:45 and the capacity on the line is so limited any increase in underlying demand has to go to higher fares, not more throughput. For suburban travelers, the gains are smaller, but still, going from 5:00 to 4:36 matters less than going from 3:21 to 2:57.

Conversely, the expensive upgrades for regional trains – by which I mean multi-billion dollars tunnels, not $300 million junction grade separations like Hunter or the few tens of millions of dollars on upgrading the junction and railyard at Summit – work better in a better-operated system. Electronics before concrete, not instead of concrete – in fact, good operations (i.e. good electronics) create more demand for megaprojects.

At no point are these really in competition, not just because flashy commuter rail projects complement intercity rail through mutual feeding, but also because the benefits for non-connecting passengers are so different that different funding mechanisms make sense. The North-South Rail Link has some benefits to intercity travel, as part of the same program with high-speed rail on the Northeast Corridor, and as such, it could be studied as part of the same program, if there is enough money in the budget for it, which there is not. Conversely, it has very strong local benefits, ideal for a funding partnership between the federal government and Massachusetts; similarly, New York commuter rail improvements are ideal for a funding partnership between the federal government, New York State, New Jersey, and very occasionally Connecticut.

In contrast, intercity rail benefits people who are far away from where construction is done: extensive bypasses built in Connecticut would create a small number of jobs in Connecticut temporarily, but the bigger benefits would accrue not just to residents of the state (through better New Haven-Boston and perhaps New Haven-New York trip times) but mostly to residents of neighboring states traveling through Connecticut. This is why there’s generally more national coordination of intercity rail planning than of regional rail planning: the German federal government, too, partly funds S-Bahn projects in major German cities, but isn’t involved in planning S21 S15 or the second S-Bahn trunk in Munich, whereas it is very involved in decisions on building high-speed rail lines. The situation in France is similar – the state is involved in decisions on LGVs and on Parisian transit but not on provincial transit, though it helps fund the latter; despite the similarity in the broad outlines of the funding structure, the outcomes are different, which should mean that the differences between France and Germany do not boil down to funding mechanisms or to inherent competition between intercity rail funds and regional rail funds.

Subway-Intercity Rail Connections

Something Onux said in comments on yesterday’s post, about connecting Brooklyn to intercity rail, got me thinking more about how metro lines and intercity rail can connect better. This matters for mature cities that build little infrastructure like New York or Berlin, but also for developing-world cities with large construction programs ahead of them. For the most part, a better subway system is automatically one that can also serve the train station better – the train station is usually an important destination for urban travel and therefore, usually the same things that make for a stronger subway system also make for better subway-intercity rail connections.

Subways and commuter trains

Like gender, transit mode is a spectrum. There are extensive systems that are clearly metro and ones that are clearly commuter rail, but also things in between, like the RER A, and by this schema, the Tokyo and Seoul subways are fairly modequeer.

The scope of this post is generally pure subway systems – even the most metro-like commuter lines, like the RER A and the Berlin S-Bahn, use mainline rail rights-of-way and usually naturally come to connect with intercity train stations. Of note, RER A planning, as soon as SNCF got involved, was modified to ensure the line would connect with Gare de Lyon and Gare Saint-Lazare; previous RATP-only plans had the line serving Bastille and not Gare de Lyon, and Concorde and not Auber. So here, the first rule is that metro (and metro-like commuter rail) plans should, when possible, be modified to have the lines serve mainline train stations.

Which train stations?

A city designing a subway system should ensure to serve the train station. This involves nontrivial questions about which train stations exactly.

On the one hand, opening more train stations allows for more opportunities for metro connections. In Boston, all intercity trains serve South Station and Back Bay, with connections to the Red and Orange Lines respectively. In Berlin, north-south intercity trains call not just at Hauptbahnhof, which connects to the Stadtbahn and (since 2020) U5, but also Gesundbrunnen and Südkreuz, which connect to the northern and southern legs of the Ringbahn and to the North-South Tunnel; Gesunbrunnen also has a U8 connection. In contrast, trains into Paris only call at the main terminal, and intercity trains in New York only stop at Penn Station.

On the other hand, extra stations like Back Bay and delay trains. The questions that need to be answered when deciding whether to add stations on an intercity line are,

  • How constructible is the new station? In New York, this question rules out additional stops; some of the through-running plans involve a Penn Station-Grand Central connection to be used by intercity trains, but there are other reasons to keep it commuter rail-only (for example, it would make track-sharing on the Harlem Line even harder).
  • How fast is the line around the new station? More stations are acceptable in already slow zones (reducing the stop penalty), on lines where most trips take a long time (reducing the impact of a given stop penalty). Back Bay and Südkreuz are in slow areas; Gesundbrunnen is north of Hauptbahnhof where nearly passengers are going south of Berlin, so it’s free from the perspective of passengers’ time.
  • How valuable are the connections? This depends on factors like the ease of internal subway transfers, but mostly on which subway lines the line can connect to. Parisian train terminals should in theory get subsidiary stations because internal Métro transfers are so annoying, but there’s not much to connect to – just the M2/M6 ring, generally with no stations over the tracks.

Subway operations

In general, most things that improve subway operations in general also improve connectivity to the train station. For example, in New York, speeding up the trains would be noticeable enough to induce more ridership for all trips, including access to Penn Station; this could be done through reducing flagging restrictions (which we briefly mention at ETA), among other things. The same is true of reliability, frequency, and other common demands of transit advocates.

Also in New York, deinterlining would generally be an unalloyed good for Penn Station-bound passengers. The reason is that the north-south trunk lines in Manhattan, other than the 4/5/6, either serve Penn Station or get to Herald Square one long block away. The most critical place to deinterline is at DeKalb Avenue in Brooklyn, where the B/D/N/Q switch from a pattern in which the B and D share one track pair and the N and Q share another to one in which the B and Q share a pair and the D and N share a pair; the current situation is so delicate that trains are delayed two minutes just at this junction. The B/D and N/Q trunk lines in Manhattan are generally very close to each other, so that the drawback of deinterlining is reduced, but when it comes to serving Penn Station, the drawback is entirely eliminated, since both lines serve Herald Square.

If anything, it’s faster to list areas where subway service quality and subway service quality to the train station specifically are not the same than to list areas where they are:

  • The train station is in city center, and so circumferential transit, generally important, doesn’t generally connect to the station; exceptions like the Ringbahn exist but are uncommon.
  • If too many lines connect to the one station, then the station may become overloaded. Three lines are probably fine – Stockholm has all three T-bana lines serving T-Centralen, adjacent to the mainline Stockholm Central Station, and there is considerable but not dangerous crowding. But beyond that, metro networks need to start spreading out.
  • Some American Sunbelt cities if anything have a subway connection to the train station, for example Los Angeles, without having good service in general. In Los Angeles, the one heavy rail trunk connects to Union Station and so does one branch of the Regional Connector; the city’s problems with subway-intercity rail connections are that it doesn’t really have a subway and that it doesn’t really have intercity rail either.

Intercity Trains and Long Island

Amtrak wants to extend three daily Northeast Corridor trains to Long Island. It’s a bad idea – for one, if the timetable can accommodate three daily trains, it can accommodate an hourly train – but beyond the frequency point, this is for fairly deep reasons, and it took me years of studying timetabling on the corridor to understand why. In short, the timetabling introduces too many points of failure, and meanwhile, the alternative of sending all trains that arrive in New York from Philadelphia and Washington onward to New Haven is appealing. To be clear, there are benefits to the Long Island routing, they’re just smaller than the operational costs; there’s a reason this post is notably not tagged “incompetence.”

How to connect the Northeast Corridor with Long Island

Map of the Northeast Corridor and LIRR Main Line; the Northeast Corridor is depicted with extensive bypasses in Connecticut and small curve modifications in New Jersey and Pennsylvania

The Northeast Corridor has asymmetric demand on its two halves. North of New York, it connects the city with Boston. But south of New York, it connects to both Philadelphia and Washington. As a result, the line can always expect to have more traffic south of New York than north of it; today, this difference is magnified by the lower average speed of the northern half, due to the slowness of the line in Connecticut. Today, many trains terminate in New York and don’t run farther north; in the last 20 years, Amtrak has also gone back and forth on whether some trains should divert north at New Haven and run to Springfield or whether such service should only be provided with shuttle trains with a timed connection. Extending service to Long Island is one way to resolve the asymmetry of demand.

Such an extension would stop at the major stattions on the LIRR Main Line. The most important is Jamaica, with a connection to JFK; then, in the suburbs, it would be interesting to stop at least at Mineola and Hicksville and probably also go as far as Ronkonkoma, the end of the line depicted on the map. Amtrak’s proposed service makes exactly these stops plus one, Deer Park between Hicksville and Ronkonkoma.

The entire Main Line is electrified, but with third rail, not catenary. The trains for it therefore would need to be dual-voltage. This requires a dedicated fleet, but it’s not too hard to procure – it’s easier to go from AC to DC than in the opposite direction, and Amtrak and the LIRR already have dual-mode diesel locomotives with third rail shoes, so they could ask for shoes on catenary electric locomotives (or on EMUs).

The main benefit of doing this, as opposed to short-turning surplus Northeast Corridor trains in New York, is that it provides direct service to Long Island. In theory, this provides access to the 2.9 million people living on Long Island. In practice, the shed is somewhat smaller, because people living near LIRR branches that are not the Main Line would be connecting by train anyway and then the difference between connecting at Jamaica and connecting at Penn Station is not material; that said, Ronkonkoma has a large parking lot accessible from all of Suffolk County, and between it and significant parts of Nassau County near the Main Line, this is still 2 million people. There aren’t many destinations on Long Island, which has atypically little job sprawl for an American suburb, but 2 million originating passengers plus people boarding at Jamaica plus people going to Jamaica for JFK is a significant benefit. (How significant I can’t tell you – the tools I have for ridership estimation aren’t granular enough to detect the LIRR-Amtrak transfer penalty at Penn Station.)

My early Northeast Corridor ideas did include such service, for the above reasons. However, there are two serious drawbacks, detailed below.

Timetabling considerations

Under current plans, there is little interaction between the LIRR and the Northeast Corridor. There are two separate routes into Penn Station from the east, one via 32nd Street (“southern tunnels”) and one via 33rd (“northern tunnels”), each a two-track line with one track in each direction. The North River Tunnels, connecting Penn Station with New Jersey and the rest of the United States, face the southern tunnels; the Gateway tunnels under construction to double trans-Hudson capacity are not planned to pair with the northern tunnels, but rather to connect to stub-end tracks facing 31st Street. For this reason, Amtrak always or almost always enters Penn Station from the east using the southern tunnels; the northern tunnels do have some station tracks that connect to them and still allow through-service to the west, but the moves through the station interlocking are more complex and more constrained.

As seen on the map, east of Penn Station, the Northeast Corridor is to the north of the LIRR. Thus, Amtrak has to transition from being south of the LIRR to being north of it. This used to be done at-grade, with conflict with same-direction trains (but not opposite-direction ones); it has since been grade-separated, at excessive cost. With much LIRR service diverted to Grand Central via the East Side Access tunnel, current traffic can be divided so that LIRR Main Line service exclusively uses the northern tunnels and Northeast Corridor (Amtrak or commuter rail under the soon to open Penn Station Access project) service exclusively uses the southern tunnels; the one LIRR branch not going through Jamaica, the Port Washington Branch, can use the southern tunnels as if it is a Penn Station Access branch. This is not too far from how current service is organized anyway, with the LIRR preferring the northern (high-numbered) tracks at Penn Station, Amtrak the middle ones, and New Jersey Transit the southern ones with the stub end:

The status quo, including any modification thereto that keeps the LIRR (except the Port Washington Branch) separate from the Northeast Corridor, means that all timetabling complexity on the LIRR is localized to the LIRR. LIRR timetabling has to deal with all of the following issues today:

  • There are many different branches, all of which want to go to Manhattan rather than to Brooklyn, and to a large extent they also want to go on the express tracks between Jamaica and Manhattan rather than the local tracks.
  • There are two Manhattan terminals and no place to transfer between trains to different ones except Jamaica; an infill station at Sunnyside Yards, permitting trains from the LIRR going to Grand Central to exchange passengers with Penn Station Access trains, would be helpful, but does not currently exist.
  • The outer Port Jefferson Branch is unelectrified and single-track and yet has fairly high ridership, so that isolating it with shuttle trains is infeasible except in the extreme short run pending electrification.
  • All junctions east of Jamaica are flat.
  • The Main Line has three tracks east of Floral Park, the third recently opened at very high cost, purely for peak-direction express trains, but cannot easily schedule express trains in both directions.

There are solutions to all of these problems, involving timetable simplification, reduction of express patterns with time saved through much reduced schedule padding, and targeted infrastructure interventions such as electrifying and double-tracking the entire Port Jefferson Branch.

However, Amtrak service throws multiple wrenches in this system. First, it requires a vigorous all-day express service between New York and Hicksville if not Ronkonkoma. Between Floral Park and Hicksville, there are three tracks. Right now the local demand is weak, but this is only because there is little local service, and instead the schedule encourages passengers to drive to Hicksville or Mineola and park there. Any stable timetable has to provide much stronger local service, and this means express trains have to awkwardly use the middle track as a single track. This isn’t impossible – it’s about 15 km of fast tracks with only one intermediate station, Mineola – but it’s constraining. Then the constraint propagates east of Hicksville, where there are only two tracks, and so those express trains have to share tracks with the locals and be timetabled not to conflict.

And second, all these additional conflict points would be transmitted to the entire Northeast Corridor. A delay in Deer Park would propagate to Philadelphia and Washington. Even without delays, the timetabling of the trains in New Jersey would be affected by constraints on Long Island; then the New Jersey timetabling constraints would be transmitted east to Connecticut and Massachusetts. All of this is doable, but at the price of worse schedule padding. I suspect that this is why the proposed Amtrak trip time for New York-Ronkonkoma is 1:25, where off-peak LIRR trains do it in 1:18 making all eight local stops between Ronkonkoma and Hicksville, Mineola, Jamaica, and Woodside. With low padding, which can only be done with more separated out timetables, they could do it in 1:08, making four more net stops.

Trains to New Haven

The other reason I’ve come to believe Northeast Corridor trains shouldn’t go to Jamaica and Long Island is that more trains need to go to Stamford and New Haven. This is for a number of different reasons.

The impact of higher average speed

The higher the average speed of the train, the more significant Boston-Philadelphia and Boston-Washington ridership is. This, in turn, reduces the difference in ridership north and south of New York somewhat, to the point that closer to one train in three doesn’t need to go to Boston than one train in two.

Springfield

Hartford and Springfield can expect significant ridership to New York if there is better service. Right now the line is unelectrified and runs haphazard schedules, but it could be electrified and trains could run through; moreover, any improvement to the New York-Boston line automatically also means New York-Springfield trains get faster, producing more ridership.

New Haven-New York trips

If we break my gravity model of ridership not into larger combined statistical areas but into smaller metropolitan statistical areas, separating out New Haven and Stamford from New York, then we see significant trips between Connecticut and New York. The model, which is purely intercity, at this point projects only 15% less traffic density in the Stamford-New York section than in the New York-Trenton section, counting the impact of Springfield and higher average speed as well.

Commutes from north of New York

There is some reason to believe that there will be much more ridership into New York from the nearby points – New Haven, Stamford, Newark, Trenton (if it has a stop), and Philadelphia – than the model predicts. The model doesn’t take commute trips into account; thus, it projects about 7.78 million annual trips between New York and either Stamford or New Haven, where in fact the New Haven Line was getting 125,000 weekday passengers and 39 million annual passengers in the 2010s, mostly from Connecticut and not Westchester County suburbs. Commute trips, in turn, accrete fairly symmetrically around the main city, reducing the difference in ridership between New York-Philadelphia and New York-New Haven, even though Philadelphia is the much larger city.

Combining everything

With largely symmetric ridership around New York in the core, it’s best to schedule the Northeast Corridor with the same number of trains immediately north and immediately south of it. At New Haven, trains should branch. The gravity model projects a 3:1 ratio between the ridership to Boston and to Springfield. Thus, if there are eight trains per hour between New Haven and Washington, then six should go to Boston and two to Springfield; this is not even that aggressive of an assumption, it’s just hard to timetable without additional bypasses. If there are six trains per hour south of New Haven, which is more delicate to timetable but can be done with much less concrete, then two should still go to Springfield, and they’ll be less full but over this short a section it’s probably worth it, given how important frequency is (hourly vs. half-hourly) for trips that are on the order of an hour and a half to New York.

How Residential is a Residential Neighborhood?

Last post, I brought up the point that the neighborhoods along the Interborough Express corridor in New York are residential. An alert commenter, Teban54transit, pointed out that this should weaken the line, since subway lines should connect residential neighborhoods with destinations and not just with other residential neighborhoods. To explain why this is not a major problem in this case, I’d like to go over what exactly is a residential neighborhood and what exactly is a destination. In short, a predominantly residential neighborhood may still have other functional uses, turning it into a destination. It’s imperfect in the case of IBX, but the relative ease of using the right-of-way makes the line still viable.

Residential-but-mixed neighborhoods

Residential neighborhoods always have nonresidential uses, serving the local population: supermarkets, schools, doctors’ offices, restaurants, pharmacies, clothing stores. These induce very few trips from out of the neighborhood, normally. But things are not always normal, and some residential areas end up getting a cluster of destinations.

In New York, the most common way such a cluster can form is as an ethnic center, including Harlem and several Chinatowns. People in and around New York travel to Harlem for specifically black cultural events, for example the shows at the Apollo Theater; they travel to Chinatown and Flushing for Chinese restaurants and supermarkets. Usually the people who so travel are members of the same ethnic community who live elsewhere; this way, in Washington Metro origin-and-destination travel data, one can see a few hundred extra trips a day between black neighborhoods east of the Anacostia River and Columbia Heights, whereas no noticeable bump is seen in work trips between those two areas on OnTheMap.

On the IBX route, this is Jackson Heights. It’s on net a bedroom community, whereas Flushing has within 1 km of Main and Roosevelt 43,000 jobs and 29,000 employed residents, but such ethnic cultural centers over time grow into destinations. People travel to the neighborhood for Indian restaurants, groceries, and cultural events, and it’s likely that over time the area will also get more professional services that cater to the community, creating more non-work and work destinations. The growth of Flushing as a job center is recent and has to be understood as part of this process: in 2007, on the eve of the Global Financial Crisis, there were only 17,000 jobs within 1 km of Main and Roosevelt. Jackson Heights, too, has seen growth in jobs from 2007 to 2019, though much less, by 27%, or 50% excluding Elmhurst Hospital, which over this period saw a small decrease in jobs.

Not only ethnic neighborhoods have this pattern. A neighborhood can grow to become mixed out of proximity to a business district, for example the Village, or out of a particular destination, for example anything near a university. On IBX, there’s nothing like the Village or Long Island City, but Brooklyn College is a destination in and of itself.

Building neighborhood-scale destinations

New public transit lines can help build neighborhoods into destinations. At the centers of cities, central business districts and rapid transit systems tend to co-evolve with each other: a high degree of centralization creates demand for more lines as the only way to truly serve all of those jobs, while a larger rapid transit system in turn can encourage the growth of city center as the place best served by the network. The same is true for secondary centers and junctions of other lines.

This, to be clear, is not a guarantee. Broadway Junction is very easily accessible by public transportation from a large fraction of New York. It’s also more or less the poorest area of the city, where working-class Bangladeshi immigrants living several to a room to save money on rent are considered a sign of gentrification and growth in rent. Adding IBX there is unlikely to change this situation.

But in Jackson Heights and around Brooklyn College, a change is more likely. Jackson Heights already has large numbers of residents using the radial subway lines to get to Manhattan for work, and a growing number of nonresidents who use its specialized businesses and cultural events. The latter group is the greatest beneficiary from circumferential transit, if it connects to the radial lines well; strong radial transit is a prerequisite, but in Jackson Heights, there already is such transit. Brooklyn College is already a destination, in a neighborhood that’s much better off than East New York and already draws widely because of the university trips; I expect that rapid transit service in three directions, up from the one direction available today (toward Manhattan), would encourage the growth of university-facing amenities, which generate their own trips.

Where to build circumferential rail

The best alignment for circumferential rail remains one that connects strong secondary destinations. However, that is strictly in theory, because usually such destinations don’t form a neat circle around city center, especially not in a city so divided by water like New York. If we were to draw the strongest secondary destinations in the city outside the Manhattan core excluding Downtown Brooklyn and Long Island City on the G, we’d get Morningside Heights for Columbia (centered on 116th), maybe 125th Street, the Bronx Hub, LaGuardia, Flushing, Jamaica, and Kings County Hospital/SUNY Downstate. These barely even form a coherent line if dug entirely underground by tunnel boring machine, diagonally under private blocks. And this is without taking into account destinations in New Jersey on the waterfront, which don’t form any neat circle with those city destinations (for example, Fort Lee is well to the north of Morningside Heights and Harlem).

In practice, then, circumferential lines have to go where it is possible, making compromises along the way. This is why it’s so important to connect to every radial, with as short a walk as practical: they never connect the strongest destinations and therefore have to live off of transfers. The G, which does connect the two largest job centers in the region outside Manhattan, fails because of the poor transfers. IBX works as a compromise alignment, connecting to interesting secondary destinations, with transfers to the most important ones, like Flushing and Jamaica. It is fortunate that the route is not purely residential: the neighborhoods are all on net bedroom communities, but some have the potential to grow to be more than that through both processes that are already happening and ones that good rapid transit can unlock.

Land Use Around the Interborough Express

Eric and Elif are working on a project to analyze land use around the corridor of the planned Interborough Express line in New York. The current land use is mostly residential, and a fascinating mix of densities. This leads to work on pedestrian, car, and transit connectedness, and on modal split. As might be expected, car ownership is fairly high along the corridor, especially near the stations that are not at all served by the subway today, as opposed to ones that are only served by radial lines. Elif gave a seminar talk about the subject together with João Paulouro Neves, and I’d like to share some highlights.

The increase in transit accessibility in the above map is not too surprising, I don’t think. Stations at both ends of the line gain relatively little; the stations that gain the most are ones without subway service today, but Metropolitan Avenue, currently only on the M, gains dramatically from the short trip to Roosevelt with its better accessibility to Midtown.

More interesting than this, at least to me, is the role of the line as a way to gradually push out the boundary between the transit- and auto-oriented sections of the city. For this, we should look at a density map together with a modal split map.

At the seminar talk, Elif described IBX as roughly delineating the boundary between the auto- and transit-oriented parts of the city, at least in Brooklyn. (In Queens, the model is much spikier, with ribbons of density and transit ridership along subway lines.) This isn’t quite visible in population density, but is glaring on the second map, of modal split.

Now, to be clear, it’s not that the IBX route itself is a boundary. The route is not a formidable barrier to pedestrian circulation: there are two freight trains per day in each direction, I believe, which means that people can cross the trench without worrying about noise the way they do when crossing a freeway. Rather, it’s a transitional zone, with more line density to the north and less to the south.

The upshot is that IBX is likely to push this transitional zone farther out. There is exceptionally poor crosstown access today – the street network is slow, and while some of the crosstown Brooklyn buses are very busy, they are also painfully slow, with the B35 on Church Avenue, perennially a top 10 route in citywide ridership, winning the borough-wide Pokey Award for its slowness. So we’re seeing strong latent demand for crosstown access in Brooklyn with how much ridership these buses have, and yet IBX is likely to greatly surpass them, because of the grade-separated right-of-way. With such a line in place, it’s likely that people living close to the line will learn to conceive of the subway system plus the IBX route as capable of connecting them in multiple directions: the subway would go toward and away from Manhattan, and IBX orthogonally, providing enough transit accessibility to incentivize people to rely on modes of travel other than the car.

This is especially important since the city’s street network looks differently by mode. Here is pedestrian integration by street:

And here is auto integration:

The auto integration map is not strongly centered the way the pedestrian map is. Quite a lot of the IBX route is in the highest-integration zone, that is with the best access for cars, but the there isn’t really a single continuous patch of high integration the way Midtown Manhattan is the center of the pedestrian map. East Williamsburg has high car integration and is not at all an auto-oriented area; I suspect it has such high integration because of the proximity to the Williamsburg and Kosciuszko Bridges but also to Grand Street and Metropolitan Avenue toward Queens, and while the freeways are zones of pedestrian hostility, Grand and Metropolitan are not.

What this means is that the red color of so many streets along the IBX should not by itself mean the area will remain auto-oriented. More likely, the presence of the line will encourage people to move to the area if they intend to commute by train, and I suspect this will happen even at stations that already have service to Manhattan and even among people who work in Manhattan. The mechanism here is that a subway commuter chooses where to live based on commuter convenience but also access to other amenities, and being able to take the train (for example) from Eastern Brooklyn to Jackson Heights matters. It’s a secondary effect, but it’s not zero. And then for people commuting to Brooklyn College or intending to live at one of the new stops (or at Metropolitan, which has Midtown access today but not great access), it’s a much larger effect.

The snag is that transit-oriented development is required. To some extent, the secondary effect of people intending to commute by train coming to the neighborhood to commute from it can generate ridership by itself; in the United States, all ridership estimates assume no change in zoning, due to federal requirements (the Federal Transit Administration has been burned before by cities promising upzoning to get funding for lines and then not delivering). But then transit-oriented development can make it much more, and much of the goal of the project is to recommend best practices in that direction: how to increase density, improve pedestrian accessibility to ensure the areas of effect become more rather than less walkable, encourage mixed uses, and so on.

Is There Room for Optimism About New York Construction Costs?

This year, there have been some positive signs about things changing in New York on subway construction – and yet, I’m uncertain about them. There are some signs that construction costs for Second Avenue Subway Phase 2 are coming under control. The New York Post broke in January that the MTA is eying smaller station designs, to reduce costs, to the tun of $300 million; an article released a few hours ago adds that there may be another $600 million in potential savings. So, in theory, costs are going down, and they’re going down as the MTA implements something we’ve been screaming about at the Transit Costs Project, so we should be happy.

And yet, I’m uncertain – not negative, but still somewhat pessimistic about whether this portends an era in which New York can finally build more subways. The main reason isn’t even some mistrust in the MTA at this point – the reduction in station footprints is a genuinely good thing, and to the extent it’s incomplete, it’s because it’s a longstanding project with older designs. Rather, it’s a combination of what this means for future projects, and how it interacts with federal funding. In brief, federal funding is at the level of the project rather than agency, and this makes it hard for cost savings to be plugged into the most straightforward benefit – namely, being able to build more on the same budget.

How is the money being saved?

The New York Post is relying on an MTA presentation from January that defends the cost structure but talks about how to reduce station costs through reducing back-of-house space. Phase 1 of Second Avenue Subway built two deep-mined intermediate stations, at 72nd and 86th Streets; the platforms are 610′ (187 meters) long, and there are no serious prospects of ever running longer trains since the line is an extension of older lines, but the station caverns are, respectively, 398 and 295 meters long, where the norm in the European comparison cases we’ve seen is that the station dig is 3-15% longer than the platforms, not twice as long.

Both stations have extensive back-of-house space, which New York City Transit demanded so that each department using the station would have its own space; 72nd also has a crossover inherited from older designs that would have permitted some trains from the south to terminate there on a third station track, which was later removed from scope to reduce costs. (The terminal station, the cut-and-cover 96th Street, is a 485 meter long dig, but that’s an artifact of block-level geology: the northern end had to go as far as 99th in order to connect with an older tunnel built in the 1970s, whereas the southern end had to go as far as 92nd because the underground geology changes abruptly there and it was easier to start boring at 92nd than at 96th.)

The plan for Phase 2 initially included much longer digs than the platform, for the same reason. However, it has since changed, and now the digs are substantially reduced. The MTA’s presentation looks like the overage at 125th Street is reduced from somewhat more than 100% in the 2004 plan to about 40-50% in the 2023 plan, and the overage at 106th and 116th is somewhat less than that, maybe 30-40%. While the 125th Street station dig is still as deep as in prior plans, the deep-mined station will also extend less far up, reducing the extent of space required to be outfit with systems.

The MTA could shrink the stations’ footprint further and save more money, but it’s fairly late in the design, and thus the opportunity to take full benefit of this improvement is for future projects. If this establishes precedent for future station construction, then it’s an unmixed blessing.

Money is saved. So what?

The broader issue is that the savings from shrinking the stations’ footprint – totaling potentially $1 billion out of a budget of $7 billion – don’t have much to go. The rub is that the project already has a Full Funding Grant Agreement. If the MTA manages to do it for less, then the most obvious, and most pessimistic, answer to where the money goes is “preventing future overruns.” The savings, in the worst case, then transfer waste from one basket, namely oversize stations, to other baskets, which could be future conflict with contractors, last-minute design changes, or betterments to the neighborhood.

That said, there are plans to spend it on something useful. But the problem is that this is limited by the scope of the project itself. Second Avenue Subway in its current iteration dates to the 1990s, and is reusing some infrastructure from the 1970s. The intention in the 1990s was to do the entire thing, or at least Phases 1 and 2, together, and the project was only chopped into four phases due to high costs. There was design work done 20 years ago or more, and the environmental impact statement is roughly that old.

I suspect the reason the cost saving from shrinking the stations is $1 billion and not much more – we estimated that Phase 1’s cost would have been halved if the stations had been only as long as the platforms – is that the designs are already spoken for, with 20 years of optimization involved. Thus the change is reducing the hard costs of construction, but not the soft costs. It will not surprise me if a postmortem will reveal an elevated ratio of soft to hard costs, purely because the cost savings are happening at such a late stage; in this case, and only in this case, it is important to forgive a high ratio of soft to hard costs, since it portends that future designs will be cheaper, and future cost savings larger. Normally, a high soft-to-hard cost ratio suggests red tape and waste involving consultants, but in this one case, it would suggest something else; I highlight this so that watchdogs for government waste, including the New York Post, realize what is going on and avoid hitting the project if it turns out to indeed have a high soft-to-hard cost ratio as I expect.

Current plans include potentially continuing the tunnel boring under 125th Street. Governor Hochul expressed some interest in a subway extension under 125th Street, extending Phase 2 from 125th/Lexington to the Hudson, with stops at the intersections with the subway lines, at Lenox (2/3), St. Nicholas (A/B/C/D), and Broadway (1 and also potential commuter rail). Such an extension was long on the wishlist of New York-area railfans, and an operations planner mentioned it to me as a future desire more than 10 years ago, unprompted. But there is no way to just reallocate $1 billion to this line; that’s not how federal funding works. At best, it will be possible to continue boring the tunnel all the way to the west, and leave the systems and stations to a future project.

My pessimism is that the cost figure given for the 125th Street extension is $7.6 billion, around $3.3 billion per kilometer. Even taking into account future inflation, it’s costlier than Second Avenue Subway Phases 1 and 2. Now, this is an early number, one that hasn’t really made it into any plans. I hope that the current cost savings are then plugged into the 125th Street extension plan, and that this project is pursued seriously at a much lower cost figure; since all stations would have to be complex digs underneath older north-south subway lines, the benefits of shrinking station footprint are especially large. But I worry that this will not happen; I’ve had hopes dashed before – for example, FRA reform did not lead American commuter rail agencies to start buying alt-compliant vehicles. We’ll see what happens if there’s more detailed work on the 125th Street extension proposal.

Funding projects vs. funding agencies

The current way federal funding works for public transportation in the United States is that the government funds specific capital projects. The MTA can ask for funding for big-ticket items like Second Avenue Subway Phase 1, Phase 2, a future 125th Street subway, the Interborough Express, or any similar such line. It can also ask for a rolling program of improvements, for example installing elevators at stations to make them accessible in line with the Americans with Disabilities Act. But the federal government does not make it easy to move money between such projects.

Phase 2 is just one project, but imagine that there are three subway lines funded concurrently: Phase 2, a subway extension under Nostrand, and a subway extension under Utica. If the MTA finds 25% cost savings, it can’t easily flex the money to a fourth line, say under 125th. It would need to start the planning process early, which is so cumbersome and expensive that it wouldn’t do so for a project it wasn’t certain it wanted to do; there is no shelf of subway extensions that are approved and are just waiting for money.

This makes the incentives for cost savings uncertain: cost savings could be used to establish the agency’s bona fides with a distrustful public, or to establish a warchest guarding against future cost overruns, or to trial new ways of working that could lead to bigger cost savings in the future, but the most straightforward benefit of cost savings – building more infrastructure on the same budget – is not generally available. For Phase 2, the best that can happen is, again, continuing boring the tunnel to the western end of 125th Street, which could be connected with the current project because the geology under the street is the same from Second Avenue to Broadway so might as well future-proof it.

And unfortunately, in the United States, the current examples of funding agencies rather than projects have been lacking. The programs in Los Angeles and Seattle, funded by sales taxes, in effect fund the agencies. There are long lists of projects in both metro areas that are funded from them, but they come from the same pool of money in each region. The situation in Los Angeles is that there’s a decided priority list, with money allocated through the end of the 2050s; if Los Angeles figures out how to cut costs significantly, all of the opening dates will be moved closer and additional lines could be planned and built with the money (the planning and environmental review process takes years, not decades, so by 2050 they will have reviews for the additional subways they could build).

And yet, the same process that’s produced lush agency-level funding in both regions has also led to bad prioritization. New York may have the world’s highest construction costs, but at least what it’s building is what it should be building: Second Avenue Subway Phase 2 is indeed the highest priority right now, and among the next priorities, the Interborough Express and 125th Street are solid choices, according to most area rail advocates two of the top five, and potentially even the top two (the other three are Nostrand, Utica, and an elevated extension of the Astoria Line to LaGuardia). In contrast, Los Angeles is prioritizing the wrong projects. The same ballot proposition process there that produces agency-level funding also requires the agency to bribe local actors who care little for public transportation or for ideological politics with lines to their own subregions of the county, not because they or their constituents will ride the trains, but because they will be able to tell their constituents “I managed to force the county to give us infrastructure money.” This way, each region of the county gets a light rail extension, no matter how lightly-ridden, while the core of the system receives little investment: while the busiest bus corridor in Los Angeles, Wilshire, is getting a subway in the D (Purple) Line Extension, the next two busiest, Vermont and Western, are not getting any rail through the 2050s, despite calls from advocates to built a line on Vermont to turn the B (Red) Line into a north-south line rather than a branch with the Purple Line.

Incentives for the future

The MTA is clearly capable of saving money. The question is now how to incentivize doing more of it. First of all, I urge New York-area advocates to pursue the 125th Street extension, and demand that the cost savings identified for Phase 2 apply to it too. The savings may even potentially be relevant to the Interborough Express, though with at-grade and above-ground stations, the impact is greatly reduced. The Phase 2 savings are reactive; applying them to future lines is proactive.

Second, I urge both the MTA and advocates to look for cost savings in areas where it is easier to flex money – namely, ADA accessibility. Being able to make a station accessible not for the current budget of about $70 million per station with contingency but the $25 million of Boston or $10 million of Madrid would enable New York to have an all-accessible subway system not in the 2050s but in the early 2030s.

Finally, at the federal level, it is useful to figure out how to fund agencies with a positive track record and not just specific projects. Potentially, agencies could be encouraged to submit wishlists of future projects that may be cleared in case money becomes available on short notice; this is useful not just in the case of cost savings, but also in the case of an unexpected infrastructure stimulus – neither the scope of the 2009 stimulus in the early Obama era nor that of 2021 under Biden had been telegraphed until shortly before, and so agencies have not always been able to take maximum advantage of the additional funds.