Eleven Claims

The 10:1 figure is unsourced. Published NJT and LIRR ridership reports show peak directional ratios in the range of two-to-one to four-to-one across most lines, not ten-to-one. A ratio of ten-to-one would describe a near-total absence of reverse-peak ridership, which is empirically false. The number functions as a claim about scale rather than a documented analytical input.

More substantively, peak asymmetry does not prevent through-running. Equipment must move out of Penn between AM and PM peaks regardless of operating model. Under terminal operations that movement is a non-revenue deadhead. Under through-running it becomes a revenue trip serving reverse-peak demand. The asymmetry argument confuses ridership distribution with operational requirement.

The premise is correct but the conclusion drawn from it does not follow. Equipment must move out of a terminal station regardless of operating model. Trains do not vanish at the bumper block. Under terminal operations, an inbound trainset is reversed and dispatched outbound either in revenue service or as a deadhead. The question is not whether the trainset moves outbound but whether that movement carries passengers and serves through-demand or moves empty as a positioning move.

Through-running converts a movement that is operationally necessary into a movement that is also revenue-productive. The "requirement" Wright identifies as a constraint is in fact a description of what already happens at Penn under terminal operation, except that today the outbound move is laden with terminal turnaround time, throat conflict, and dwell penalty.

The argument confuses two different capacity constraints. Under-river tunnel capacity, measured in tracks per hour through the North River Tunnels, is one constraint. Penn Station platform and throat capacity, measured by how quickly trains can be received, processed, and dispatched, is another. Through-running does not change tunnel capacity. Two tracks remain two tracks. What through-running changes is platform capacity, by reducing dwell time per train from roughly twenty minutes for terminal turnaround to under two minutes for a continuous move.

The "empty reverse train replaces a full inbound train" framing assumes one-for-one substitution at the tunnel level. That substitution is not the binding constraint. Under terminal operations, the binding constraint is the time each train occupies a Penn platform. Compressing that time by an order of magnitude allows more inbound trains per hour to be received, not fewer.

Even granting the framing on its own terms, the reverse-peak movement happens regardless. The choice is whether that movement carries passengers or runs empty. Through-running converts deadhead positioning moves into revenue service. Wright's argument treats this as a cost rather than a benefit.

This conclusion depends on the premises assessed under A·02 and A·03. Once those premises fall, the conclusion does not survive. The peer evidentiary record does not support net capacity loss. The 2024 WSP/FXC feasibility study finds throughput gains. The Penn Station Master Plan Alternatives Report itself acknowledges through-running as a future operational state the southern expansion is being designed to accommodate, which is a strange thing to design for if the operating model would reduce capacity.

The April 2026 RPA report reaches the same negative conclusion as Wright's interview, but does so through a 9-minute dwell assumption and a 90 trains-per-hour directional benchmark. Both inputs are calibrated to stub-end terminal operation. Through-running is not a stub-end operation. Calibrating the simulation to terminal logic and then concluding that through-running does not work is not a finding. It is an artifact of the model setup.

The framing is selective. Through-running regional rail is not a London phenomenon. Paris RER. Berlin S-Bahn. Munich S-Bahn. Zurich S-Bahn. Stockholm pendeltåg. Tokyo's through-running JR and private-rail operations. Stuttgart S-Bahn. These systems serve cities with diverse spatial geographies, including monocentric, polycentric, linear, and clustered urban forms. The claim that through-running depends on a London-specific geography requires erasing every other city that operates the same service model.

The east-west alignment of the Elizabeth line was not a found feature of London's geography. It was a deliberate routing decision made over decades of planning to connect the commercial centers. The rail infrastructure shaped the geography it served as much as it conformed to it.

London also operates Thameslink, a north-south through-running line, on a different corridor entirely. The "two things" framing collapses to one example and treats it as the general case.

The dismissive "and that's about it" reads as rhetorical erasure rather than empirical description. Long Island City has roughly sixty thousand jobs and has been one of the fastest-growing employment centers in the region. Newark has approximately one hundred fifty thousand daytime workers. Downtown Brooklyn is a Class A office market with significant recent job growth. Jersey City and Hoboken host major financial-services employment. Stamford is the eighth-largest city in New England and a regional employment center in its own right. The Bronx Hub, Industry City in Sunset Park, and the Long Island employment corridor along the Nassau-Suffolk border all generate substantial commuter flows that the monocentric framing cannot describe.

The argument is also circular. Through-running enables the polycentric employment growth the dismissal claims is impossible. Reverse-commute connectivity is itself a precondition for office markets outside Manhattan. Without it, Newark stays smaller than it would be, Long Island City stays smaller than it would be, and the monocentric pattern reproduces itself. With it, the geography that the rebuttal requires becomes economically possible.

The Sunnyside Yards housing-and-transit proposal, which would create a major new employment-and-residential cluster directly served by through-running infrastructure, is itself self-defeating evidence against the monocentric claim. The same RPA institution promotes development of new centers while arguing the rail network that would serve them cannot be built because no centers exist outside Midtown.

The example is a straw-man of through-running's actual value proposition. Through-running is not primarily justified by direct suburb-to-suburb flows. The benefits are operational. Reduced dwell at Penn. Higher frequency on each line. Eliminated terminal turnaround. Capacity gains that accrue regardless of any particular passenger's origin and destination.

To the extent through-running does generate new origin-destination demand, the relevant flows are reverse commutes between Manhattan and outer-borough or New Jersey employment centers, same-side trips that pass through Manhattan en route to a destination further along the corridor, and induced demand from employment relocations that improved connectivity makes economically feasible. The cherry-picked extreme of New Brunswick to Ronkonkoma functions as an argument by minimization, not analysis of the actual demand patterns through-running would serve.

Even on the cherry-picked example, demand is endogenous to supply in transit. The Elizabeth line generated trips that did not previously exist as documented demand. Asking what current ridership is between a pair of nodes in a network that does not connect them produces a small number, not a meaningful measure of latent demand.

The behavioral observation is correct and the inference drawn from it is wrong. Through-running advocates do not primarily promise generic connectivity to many destinations. They promise higher frequency on each line, faster trips overall, reduced dwell, and capacity that supports more service to each rider's actual destination. The riders of the New Brunswick branch under through-running operations get more trains per hour to New Brunswick, not a useless connection to Ronkonkoma.

The argument substitutes a weak version of the through-running case for the actual case, then dismisses the weak version. That version of the argument does not engage with the operational benefits that form the core through-running case.

The claim treats frequency as a property of through-running rather than as an operational design choice. Properly designed through-running increases frequency on each branch. Reduced platform dwell allows more trains per platform per hour. Reduced fleet idle time at terminal layovers allows more revenue trips per day from the same equipment. Eliminated terminal-throat conflicts at Penn allow more conflict-free movements across the diamond.

The frequency claim is unsupported by any analysis the public can review. RPA's April 2026 report does not present a frequency comparison between a through-running operating model and the current terminal model. Wright's assertion that frequency "is never going to be very frequent" is forecasting a result based on an analysis no one has shown.

The 2024 WSP/FXC feasibility study reaches the opposite conclusion. The frequency benefit is one of the core operational gains the study documents.

This claim recasts an operational question as a station-experience question. The choice presented is narrower than the policy question. It is between operational change that delivers capacity benefits within years at roughly one billion dollars for the Penn-only scope, and a physical reconstruction that delivers an improved waiting environment at fourteen-and-a-half to nearly seventeen billion dollars while preserving terminal-only operation. The "beautiful Penn" framing trades the operational case for a station-experience case, then accepts an order-of-magnitude cost difference as if the comparison were neutral.

The April 2022 Penn Station Master Plan Alternatives Report on its face describes a southern expansion that is being designed to permit eventual through-running by means of new tunnels constructed at some future date. The expansion preserves terminal-only operation in the interim. The temporal horizon for the future tunnel construction has been estimated by some analysts at the 2080s. This is what "beautiful Penn with easy transfer" is being proposed in lieu of. It is not a station upgrade. It is a multi-decade deferral of the operational change that would deliver the network benefit, financed at a price point that makes the deferral structurally hard to revisit once committed.

The transfer experience itself does not address the binding capacity constraints. A passenger with a smooth concourse transfer is still subject to the dwell penalty at the terminal, the throat conflict at the diamond, and the per-line frequency ceiling those constraints impose. The argument substitutes wayfinding and aesthetics for operational performance.

The framing presents a false choice. Hudson tunnels and through-running are not substitutes. They are complementary. New tunnels expand under-river capacity. Through-running maximizes the productivity of platform infrastructure, both existing and new. The two interventions answer different constraints and a regional rail strategy that needs both does not have to choose.

Crucially, the Gateway tunnels are funded and proceeding regardless. The decision in front of the Gateway Development Commission and the master developer procurement is not whether to build new tunnels. It is whether the southern expansion of Penn at fourteen-and-a-half to nearly seventeen billion dollars is the best use of public funds when through-running operational change at roughly one billion dollars for the Penn-only scope would deliver capacity benefits within years and shape how new Gateway tunnels are operated when they open.

The "future step" framing has a long pedigree at this institution. The 2014 RPA institutional governance report by the same organization treated through-running as a future goal. The 2026 RPA report treats through-running as a future possibility. The southern expansion currently being procured by Amtrak under the master developer P3 treats through-running as a future operating model the new station will eventually accommodate. Each iteration of "future step" has come with a generation of cost commitments to physical infrastructure that does not require operational change to proceed. The deferral compounds. At what point does "future step" become "permanently deferred"?

The cost of perpetually deferring operational change is itself enormous. Climate considerations make additional decades of automobile-dependent commute patterns increasingly costly. Demographic and employment shifts are reshaping the region in ways that operational change could accommodate sooner if undertaken now. Technology is advancing in ways that could change what counts as feasible. Promising the operational change in some indefinite future and committing the funding to physical infrastructure today is the structural choice through-running advocates have been objecting to for decades.