The developer is selected. The through-running commitment has no definition.
On May 20, Secretary Duffy and the Amtrak board named Penn Transformation Partners — Halmar International and Skanska — as Penn Station's master developer. The announcement committed to "at least limited through-running on the regional rail network" as one of five project deliverables. That phrase carries no operational definition, no service standard, and no enforcement mechanism as written. Contract negotiations are underway. Whatever the pre-development agreement says about through-running — or doesn't say — will govern what gets built on a half-century timeline. The FRA Service Optimization Study Phase 2 is expected in Summer 2027. The developer is already designing.
Updated May 27, 2026 — Penn Transformation Partners selected May 20 — Contract negotiations underway — Groundbreaking target: end of 2027
Penn Station is a terminal. The region needs a through-station.
Penn Transformation Partners was named on May 20 with a commitment to "at least limited through-running on the regional rail network." That phrase is the entirety of the operational obligation as stated. It carries no service definition, no frequency standard, and no enforcement mechanism. The pre-development agreement — now being negotiated — is the last document that can convert the announcement's language into a binding design requirement. Phase 2 of the FRA Service Optimization Study, the only federal process capable of producing an operationally validated through-running scenario, is expected Summer 2027. The developer will have been designing for months before it arrives.
Penn Station was built as the southern terminus of the Pennsylvania Railroad. Most trains still arrive, dwell, and reverse direction. That paradigm produces three problems at once. Trainsets sit at platforms instead of moving people. Each railroad protects its own slots, which makes coordination across NJ Transit, LIRR, and Amtrak the exception rather than the rule. And the geography of the station forces conflicts at the interlockings that limit how many trains can actually move through, regardless of how many tracks the timetable shows.
This is not a station-design problem. It is an operating-model problem that has been allowed to look like a station-design problem for forty years.
The May 20 announcement introduced a new layer to that problem. "At least limited through-running on the regional rail network" appears as the third of five project deliverables, following "expand track capacity" as a framing — through-running positioned as an adjunct to physical expansion rather than an alternative to it. The phrase will carry whatever meaning the pre-development agreement gives it, and those negotiations are underway now.
- → Penn Station Access slipped to 2030 because the three operators could not coordinate the construction phasing.
- → The April 2026 Amtrak-MTA federal lawsuit over Acela testing access shows how brittle the current shared-use arrangement actually is.
- → The October 2024 feasibility study cited operational modeling against through-running. Amtrak FOIA responses and NJ TRANSIT OPRA records now present accounts that are difficult to reconcile, while separate SOS records show NJT challenging current RTC capacity outputs.
Today, a passenger going from Montclair to Huntington requires two trains, a transfer at Penn, and roughly ninety minutes. Through-running collapses that into one train and roughly fifty. Multiply that across the dozens of cross-Hudson origin-destination pairs that sustained ridership across the region runs on, and you have the regional labor market the Gateway tunnels were built to serve.
What the operating models look like
Terminal operations require trains to reverse, which means crews change ends, dwells stretch, and the interlocking has to clear before the next train can enter. Conflicts at the throat of the station block other movements. The yellow zone shows where those conflicts compound.
Through-running uses the same tracks for continuous bidirectional movement. The platform turns the train in the time it takes for passengers to get on and off.
Through-running. The way every other major rail city does it.
Through-running means a train from New Jersey continues through Penn Station to Long Island, and a train from Long Island continues through Penn Station to New Jersey. The platform is a stop on a route, not the end of one. Every other major regional rail network in the world that has solved a comparable capacity problem has solved it this way. The Elizabeth Line in London. The RER in Paris. The S-Bahn in Berlin and Munich. None of them treat their central station as a terminus.
Penn Station has the track geometry to do this today. Tracks 5 through 21 already connect to both the Hudson tunnels to the west and the East River tunnels to the east. The 2021 MTA-WSP white paper confirmed the physical baseline. The question is whether the next operating contract is written around that capability or written around the assumption that Penn remains a terminal.
The selection announcement listed "completing the FRA-led Service Optimization Study" as a concurrent next step alongside design advancement, contract negotiations, and permitting — not a prerequisite for them. Phase 2, the final phase, is expected Summer 2027. Groundbreaking is targeted before end of 2027. What the developer designs between now and then will be built around whatever through-running standard — if any — ends up in the pre-development agreement.
"At least limited through-running on the regional rail network" appears as the third of five deliverables in the May 20 announcement, following "expand track capacity." The phrase "at least limited" is structural ambiguity — it forecloses nothing and can be satisfied by a configuration where NJT and LIRR trains remain stub-end while a single Amtrak service continues through. The pre-development agreement is the document that converts this phrase into something operationally testable. It is being negotiated now.
The structurally important fact is that the October 2024 WSP/FXC feasibility study identified Sunnyside Yard in western Queens as the required location for a far-side turnback yard if through-running is the operating premise. That same land is now the site of Mayor Mamdani's housing proposal. The geography is forcing a regional decision about how the same parcels get used. The answer to that decision should not be made by accident, by a developer working off a default operating assumption.
The terminal model: Trains arrive, dwell ten to fifteen minutes while passengers board and crews change ends, then reverse out. Each operator hoards capacity. A delay on one side wastes capacity on the other.
The through-running model: Trains stop briefly, exchange passengers, and continue. Penn becomes the middle of routes that connect the region. Service patterns are timetabled across the whole network, not just for trips into Manhattan.
Penn has 21 tracks. Tracks 5 through 21 already connect to both the Hudson and East River tunnels. The constraint is not the tracks. It is the dwell times, the platform widths, the vertical circulation, and the operating agreements between three railroads that currently behave as if they share a building, not a system.
- 17 through-tracks already exist. Tracks 5-21 support bidirectional operation today.
- Platform constraints are addressable. Wider platforms and "load and go" dwells reduce the bottleneck the 2024 study said was binding.
- Tunnel capacity is the real ceiling. Hudson at roughly 24 trains per hour plus East River at roughly 20 sets the system-wide cap. The station configuration determines how much of that ceiling translates into service.
- Unified dispatching is required. AC and DC traction differences are real but solvable. The harder problem is operating discipline across three agencies.
- The announcement's language is not a design specification. "At least limited" through-running does not address platform configuration, turnback yard planning, or signal sequencing. The pre-development agreement is where those answers either appear or don't.
Every comparable city built tunnels to link its legacy terminal stations and operated them as a single through-running spine. None of them treated the original terminal as the endpoint of the system.
Thameslink and the Elizabeth Line
Cross-city tunnels connecting divided terminals. The Elizabeth Line moves more people through its central core than the entire LIRR system.
RER and S-Bahn
Suburban lines stitched through central tunnels. Direct trips across each metro region without the transfer penalty Penn imposes today.
The public record now contains conflicting accounts of what modeling exists and a technical challenge to current RTC outputs.
The case against through-running at Penn rests first on the October 2024 WSP/FXC feasibility study commissioned by Amtrak, the MTA, and NJ TRANSIT. RPA's April 2026 report is a separate publication that relies on that earlier capacity frame. The FRA/DB Service Optimization Study is separate again: a federal study process underway since October 2025. The 2024 study said operational modeling supported its conclusions. FOIA, FOIL, and OPRA records now show a gap between what Amtrak said it possessed, what Amtrak said was performed, and what FRA was asking NJ TRANSIT to release.
"The search did not reveal any simulations or modeling data in Amtrak's possession, and the dwell times were based on publicly available data."
"The work was led by MTA (and their consultant). We have no native files, operational models (because no simulations were performed) or calculation workbooks."
The April 2026 NJ TRANSIT OPRA release adds a third layer. In November 2025, FRA officials asked NJ TRANSIT to release a "Penn Station-specific RTC model developed in coordination with MTA and Amtrak." Those records do not prove, by themselves, which agency holds each technical file or how each agency defined "simulation" in its FOIA responses. They do show that the public record is not yet complete.
"At this time, NJ TRANSIT does not concur with the SOS Team's inclusion of Train Per Hour (TPH) capacity figures in any public-facing report."
NJT's March 2026 feedback concerned the SOS team's RTC files, not the separate October 2024 WSP/FXC feasibility study or the April 2026 RPA report. The distinction matters. The October 2024 study remains the earlier railroad-commissioned record behind the in-footprint feasibility debate. The RPA report treats parts of that record as established. The SOS correspondence shows that when RTC files circulated in the federal study process, NJT identified problems serious enough to object to public-facing TPH conclusions. A developer designing around Phase 1 infrastructure findings is working from a technical foundation whose core analytical outputs NJT has formally said are not credible.
- May 20, 2026Penn Transformation Partners selected. Announcement commits to "at least limited through-running on the regional rail network" without operational definition. FRA commits $200M for design and permitting.
- Mar 24, 2026NJT formally states SOS RTC results "not credible in their current form" and should be excluded from any public report until deficiencies — shortened train consists, zero-second switch handling, dwell-parameter violations, optimistic delay averaging — are corrected.
- Mar 17, 2026NJT tells the SOS team that DB's claimed conclusions do not appear to be supported by the RTC case files when dispatched.
- Aug 14, 2025Amtrak appeal denial says its search found no simulations or modeling data in Amtrak's possession (Case 25-FOI-00443).
- Nov 6, 2025FRA Director Lyle Leitelt emails NJT asking for the Penn Station RTC model.
- Feb 9, 2026Amtrak's response in 26-FOI-00272 states explicitly: no simulations were performed.
- Apr 22, 2026MTA grants the City Club's FOIL appeal. Production dates include April 30 and June 4; scope, redactions, and withholdings remain unknown.
- Apr 26, 2026NJT OPRA documents confirm the railroads had already received the SOS Phase 1 draft report.
The technical case for southern expansion has rested on a study whose underlying modeling has not been publicly produced. Penn Transformation Partners will be designing around assumptions drawn from this record. The FOIL appeal grant creates a production schedule; what it yields will depend on scope, redactions, and agency compliance.
From procurement to contract to shovels.
The procurement closed on a federal timeline that compressed every step. Penn Transformation Partners is now selected. The pre-development agreement is being negotiated. The study that could define what through-running actually requires at Penn Station arrives after the developer is already designing.
Dates reflect the October 2025 RFLOI, the January 2026 shortlist, the May 20 announcement, and the publicly stated procurement schedule.
-
October 30, 2025
Request for Letters of Interest issued
Amtrak issues the RFLOI. The Base Scope focuses on renovating existing infrastructure. Block 780 expansion is not included.
Complete -
January 2026
Three finalists confirmed
Penn Forward Now (Fengate), Penn Transformation Partners (Halmar), and Grand Penn Partners (Macquarie) advance to final bidding.
Complete -
May 4, 2026
Bid deadline
Final bids submitted from three consortia.
Complete -
May 20, 2026
Penn Transformation Partners announced
Secretary Duffy and the Amtrak board named Halmar International and Skanska as the selected consortium. The announcement committed to "at least limited through-running on the regional rail network" as one of five deliverables, without an operational definition. FRA Administrator Fink announced $200 million from the Partnership-Northeast Corridor Program for design and permitting. Byford confirmed a groundbreaking target of end of 2027.
Complete -
May 2026 — ongoing
Pre-development agreement negotiations
Amtrak and Penn Transformation Partners are negotiating the pre-development agreement, which will establish project design requirements and financing structure. Whether a binding through-running standard is included depends on these negotiations. No public timeline for agreement finalization has been announced.
Active window -
June 4, 2026 (anticipated)
MTA FOIL production
The MTA granted the City Club's FOIL appeal on April 22. A June 4 production date is scheduled. Scope, redactions, and withholdings remain unknown. Records from this production may bear on the technical record underlying the October 2024 feasibility study.
Anticipated -
Spring 2026 — delivered
FRA Service Optimization Study, Phase 1 draft
NJT OPRA records confirm the railroads had received the Phase 1 draft by April 26. Separate records show NJT formally challenging the TPH-based conclusions in the SOS RTC analysis as not credible in their current form.
Complete -
2026-2027
NEPA review and design advancement
FRA leads compressed environmental review concurrent with master developer design work. The announcement listed SOS completion as a concurrent activity alongside this phase — not a prerequisite for it.
-
Summer 2027
FRA Service Optimization Study, Phase 2 final
Phase 2 — the final phase, covering operational improvements throughout the NY Metro Region — is expected after the developer is selected and design is already underway. This is the phase that could produce an operationally validated through-running scenario. It arrives months before the targeted groundbreaking.
-
By end of 2027
Groundbreaking
Byford confirmed a groundbreaking target of end of 2027. Financial and commercial close must be achieved before construction begins. Once construction starts, operational changes become significantly more expensive and structurally constrained.
Hold the announcement's commitment to an operational standard
The selection is made. The pre-development agreement is being negotiated. The questions below are designed to be used now, by the people who can ask them and have them count before the contract is signed.
Federal and state officials
- Request the pre-development agreement language on through-running — what operational standard, what service frequency, and what enforcement mechanism, if any, the agreement will contain.
- Ask how NJT's March 2026 formal objection to the SOS RTC methodology has been resolved, and what technical record is governing the design requirements in the agreement.
- Ask what mechanism ensures Phase 2 SOS findings can constrain the developer's design before physical commitments are finalized — given the announcement described design and SOS completion as concurrent activities.
- Tie future appropriations to public release of the technical assumptions underlying the procurement, including the October 2024 feasibility study's underlying modeling.
Reporters and editors
- The announcement's through-running language — "at least limited" — carries no operational definition. The story is what the pre-development agreement does with it.
- The gap between Summer 2027 Phase 2 completion and the end-of-2027 groundbreaking target is the window in which design will be physically committed before the final study lands.
- The documentary spine runs from NJT's March 2026 RTC objection through Amtrak's no-simulations FOIA responses through the Phase 1 draft already in the railroads' hands.
- The April 2026 Amtrak-MTA federal lawsuit over Acela testing access shows that the current operating model is unstable even before a developer touches a track.
Coalitions and organizations
- Demand the pre-development agreement include a binding, operationally specific through-running standard — not a phrase from a press release.
- Review the SOS Phase 1 draft findings for platform and track configuration implications before the developer locks in a design.
- Prepare NEPA scoping comments now. The compressed timeline will not wait for organized response.
- Connect the through-running standard explicitly to housing, climate, and labor-market outcomes your membership already works on — the Sunnyside Yards geography makes these inseparable.
Documents and analyses
Published material that supports the case made above. This list grows as records clear review.
Documents released through FOIA show Amtrak has paid the Regional Plan Association under contract to manage Build Gateway Now Coalition advocacy. RPA published a report on April 23, 2026 concluding that through-running would reduce capacity at Penn. A technical critique of that report, available below, evaluates its claims against international peer-system performance and the documentary record. Readers should weigh RPA's analysis with the funding relationship in mind.
Penn Transformation Partners selection announcement
Secretary Duffy and the Amtrak board name Halmar International and Skanska as master developer. The announcement commits to "at least limited through-running on the regional rail network" as one of five project deliverables and confirms a $200 million FRA commitment for design and permitting.
Read the announcementFix Penn Station and build Sunnyside
The core argument: through-running at the existing Penn footprint, with a Sunnyside Yards turnback, is the operational answer the region has needed for decades.
Read at the Daily NewsAll of Penn must be fixed
The editorial board argues Penn's concourse rebuild and track/platform operating problem must be addressed together, criticizes the RPA through-running report, and urges Gateway changes that avoid forcing Block 780.
Read at the Daily NewsTechnical critique of RPA's April 2026 report
A point-by-point technical evaluation of the RPA report's dwell-time assumptions, capacity claims, and methodological gaps against the ReThinkNYC RUN proposal and international peer-system performance.
Read the critique$4.7 billion Northeast Corridor investment
Secretary Duffy and Deputy Secretary Bradbury announce $4.7 billion in NEC investments through the Partnership-Northeast Corridor Program. Specific Penn Station allocations are determined through application processes; the announcement provided market reassurance rather than committed spending authority.
View at USDOTFOIA, FOIL, and OPRA productions
The full documentary record from the Penn Station investigation, including the August 2025 Amtrak appeal denial, the February 2026 FOIA response, the April 2026 MTA FOIL appeal grant, and the April 2026 NJ TRANSIT OPRA release.
View the document indexQuestions that come up.
The most frequent questions in policy conversations, media coverage, and community discussions. Answers here are informational, not the position of any agency.
The May 20 announcement listed "the introduction of at least limited through-running on the regional rail network" as the third of five project deliverables, following "expand track capacity" and before "enable new retail, better wayfinding, and other passenger experience improvements." The phrase appears without an operational definition. It names no service frequency, no operator pair, no timeline, and no enforcement standard.
"At least limited" is structural ambiguity — it forecloses nothing and can be satisfied by a configuration where NJT and LIRR trains remain stub-end while a single Amtrak service continues through. Whether this phrase becomes a binding design requirement depends entirely on the language of the pre-development agreement now being negotiated. That agreement is the document that converts the announcement's language into something operationally testable.
Penn Transformation Partners was named on May 20, 2026 — more than a year before Phase 2 of the FRA Service Optimization Study is expected to be complete in Summer 2027. The announcement described SOS completion as a concurrent next step alongside design advancement, not a prerequisite for it.
This means the developer will be making decisions about track geometry, platform configuration, and operational capacity before the federal study that could define a through-running scenario has published its final findings. The pre-development agreement, currently being negotiated, is the last opportunity to build in a mechanism requiring Phase 2 findings to actually constrain what gets designed and built — rather than arriving as a study that documents what has already been committed.
No. Through-running is an operating model. It is about how trains use the tracks and platforms below the building, not about the building itself. The current Amtrak procurement focuses on renovating the existing footprint. The Block 780 expansion that would have required substantial real-estate disruption is not in the Base Scope.
Yes. The Hudson tunnels are essential to any operating plan. The question is what they connect to. Through-running treats the tunnels as the western half of a bidirectional spine that continues through the East River tunnels to Long Island. Terminal operations treat the tunnels as a feeder into a station where trains stop and reverse.
The 2015 Gateway Program technical memorandum projected 29 trains per hour eastbound capacity at the Gateway portal. The tunnels are designed for through-running volumes. Whether that capacity translates into regional service depends on the operating model the station is designed around.
The October 2024 WSP/FXC feasibility study identified Sunnyside Yard in western Queens as the required location for a far-side turnback yard if through-running is the operating premise. Mayor Mamdani's housing proposal covers the same site. The geography forces a regional decision: Sunnyside can be the operating-yard backbone of a through-running regional network, the site for tens of thousands of new housing units, or some carefully designed combination that makes both work.
That decision should not be made by accident, by a master developer working off the assumption that Penn remains a terminal. It should be made deliberately, with full visibility into what the operating-yard footprint actually requires and what land remains available for housing above it.
The House surface transportation reauthorization bill, advancing in Congress, includes several provisions with direct bearing on Penn Station's trajectory. The most immediately significant is Section 10202, which would apply the federal Freedom of Information Act and the Government in the Sunshine Act to Amtrak board meetings in any year Amtrak receives a federal grant. Currently, Amtrak holds only one public board meeting per year; this provision would make future board deliberations — including approvals of the Penn Station pre-development agreement and any contract modifications — presumptively open to the public.
The bill also adds non-Amtrak carriers as eligible applicants for intercity passenger rail capital grants and shifts statutory language from "Amtrak routes" to "intercity passenger rail routes," two structural changes with long-term implications for who can compete for federal rail funding on the Northeast Corridor. A separate provision creates a fast-track RRIF financing mechanism for Amtrak-designated priority projects with compressed review timelines and commercially calibrated credit risk premiums — a financing tool the Penn Station project would be well-positioned to use once the pre-development agreement is in place.
FOIA-released documents show Amtrak has paid the Regional Plan Association under contract to manage Build Gateway Now Coalition advocacy and conduct public-facing campaigns supporting the Gateway program. RPA's CEO sits on the Amtrak board's advisory structures and shares trustees and senior staff with the Gateway Development Commission. RPA testified before the GDC without disclosing the funding relationship until FOIA productions made it part of the public record.
None of this disqualifies RPA's analysis. It is context readers deserve when weighing the technical conclusions of a paid advocate. The detailed critique of RPA's April 2026 report is in the resources section.
Request a briefing.
The City Club is available to brief reporters, community boards, and elected officials on the Service Optimization Study record and the pre-development agreement.
Request a briefingFor reporters, indicate outlet, deadline, and angle. For government, include committee or portfolio. Requests on the pre-development agreement are prioritized.