Long-Distance vs. Corridor Amtrak Trains: How the On-Time Record Differs by Service Line
None of the 14 long-distance Amtrak routes met the 80% on-time standard in FY26 Q2; 11 of 27 state-supported routes did. How the FRA data compares them.
In the quarter from January 1 to March 31, 2026 (the FRA's FY26 Q2), none of the 14 long-distance Amtrak routes met the federal on-time standard of 80 percent, while 11 of the 27 state-supported routes did. The figures are customer on-time performance from the Federal Railroad Administration's quarterly filing under 49 CFR part 273: the share of customers who arrive at their stop no later than 15 minutes after the published scheduled arrival time (49 CFR 273.5(a)(1)).
This guide sets the service lines side by side so you can tell what a route's figure is being compared with. It is a record of one past quarter, not a forecast for a trip. The route-by-route pages are in Amtrak On-Time Performance by Route; how the measure itself works is in How Amtrak On-Time Performance Is Measured.
The four service lines, FY26 Q2
The Amtrak pages on this site group the FRA's 47 reported routes into four service lines. Counts below are for FY26 Q2 (January 1 to March 31, 2026); "two-quarter standard" means the route met 80 percent in both that quarter and the one before it, the way the rule words it: 80 percent "for any 2 consecutive calendar quarters" (49 CFR 273.5(a)(2)).
| Service line | Routes | Met 80% in FY26 Q2 | Met the two-quarter standard | Customer OTP range, FY26 Q2 |
|---|---|---|---|---|
| Northeast Corridor | 5 | 1 | 1 | 67.3% to 84.1% |
| State Supported | 27 | 11 | 8 | 52.8% to 88.5% |
| Long Distance | 14 | 0 | 0 | 39.7% to 79.9% |
| Seasonal Trains | 1 | 1 | 1 | 93.9% |
Two things the table does not say. The ranges are the spread between the lowest and highest route in each line, not an average, and a line's range says nothing about how many passengers sit at each end of it. And the table does not explain why the lines differ; the federal rule defines the measure and the delay categories, not the reasons a line runs late.
Long distance: no route at the standard, two a tenth of a point under
The long-distance figures run from 39.7 percent to 79.9 percent. Two routes sit at 79.9 percent in FY26 Q2, the City of New Orleans and the Palmetto. Missing 80 percent by 0.1 points and missing it by 40 points both count as "did not meet the metric", so the met-or-missed mark alone hides a wide spread. That is why the route pages show the percentage as well.
Who the delay minutes are charged to
The rule requires Amtrak to record each delay as host-responsible, Amtrak-responsible or third party. Host-responsible delays are "delays recorded by Amtrak, in accordance with Amtrak procedures, as host-responsible delays, including freight train interference, slow orders, signals, routing, maintenance of way, commuter train interference, passenger train interference, catenary or wayside power system failure, and detours" (49 CFR 273.3). The figures below are minutes of delay per 10,000 train miles.
In FY26 Q2, host-responsible minutes per 10,000 train miles were the largest of the three categories on all 14 long-distance routes and on 23 of the 27 state-supported routes. Those are the counts of routes where the host figure exceeds both the Amtrak and the third-party figure; they say where the coded minutes fall, not whose fault any individual delay was. The coding is Amtrak's, made under Amtrak procedures, as the rule's own wording says.
Worked example: two long-distance routes, FY26 Q2
| Southwest Chief | Palmetto | |
|---|---|---|
| Customer OTP | 39.7% | 79.9% |
| Host-responsible minutes per 10,000 train miles | 942 | 825 |
| Amtrak-responsible | 420 | 240 |
| Third party | 236 | 461 |
| Total coded minutes per 10,000 train miles | 1,598 | 1,526 |
| Host share of the total | 58.9% (942 ÷ 1,598) | 54.1% (825 ÷ 1,526) |
The two routes are 40.2 points apart on customer on-time performance yet carry a similar host-responsible share of coded delay, and their totals per 10,000 train miles differ by 72 minutes. The delay split alone does not account for the gap in on-time performance between them. Read the split as the composition of a route's delay, and read the customer OTP as how many passengers it affected.
Using this when you pick a train
- Compare a route with its own service line first. A 70 percent figure means one thing on a state-supported corridor, where FY26 Q2 figures ran from 52.8 to 88.5 percent, and another against the long-distance range of 39.7 to 79.9 percent. Neither is a promise about your date.
- Look at the last two quarters, not one. The standard is judged over two consecutive quarters, and 8 of the 11 state-supported routes that met 80 percent in FY26 Q2 also met it in the quarter before.
- Check the percentage, not just the mark. A route at 79.9 percent and one at 39.7 percent both show as "missed".
- These are historical base rates from the FRA's filing. This site does not track live trains and does not predict delays.
Informational only, not professional advice.
Last reviewed: October 2026. Analysis by Eric, OnTimeIndex founder.
Sources
- Federal Railroad Administration, Intercity Passenger Rail Service Quality and Performance Reports, FY26 Q2 (January 1 to March 31, 2026, posted July 21, 2026): https://railroads.dot.gov/rail-network-development/passenger-rail/amtrak/intercity-passenger-rail-service-quality-and
- 49 CFR 273.5, Metrics and minimum standards: https://www.law.cornell.edu/cfr/text/49/273.5
- 49 CFR 273.3, Definitions (host-responsible, Amtrak-responsible and third party delays): https://www.law.cornell.edu/cfr/text/49/273.3
Sources
Informational only — every figure here comes from historical federal filings, not a prediction of any future flight, and nothing here is professional travel advice.