by shlustig
Results for this period are:
TOTAL TRAINS =769
ON TIME = 321 (42%)
LATE = 448 (%8%)
AVERAGE DELAY = 49"
Of the late trains:
54% were 29" or less late;
20% were 30" to 59" late;
16% were 1' to 2' late;
10% were more than 2' late; and
<1% had no arrival time shown.
BY ROUTE, WITH ON-TIME % AND AVERAGE DELAY:
CAPITOL LIMITED
#29 - 8% - 1' 08"
#30 - 8% - 1' 10"
CARDINAL (WAS)
#51 - 23% - 1' 21"
#50 - 17% - 1' 18"
PENNSYLVANIAN
#43 - 11% - 37"
#42 - 25% - 24"
LAKE SHORE LIMITED
#49 - 38% - 1' 11"
#48 - 76% - 9"
LAKE SHORE LIMITED (BOSTON / ALBANY)
#449 - 38% - 26"
#448 - 0% - 41"
CITY OF NEW ORLENS
#59 - 76% - 56"
#58 - 85% - 2' 11"
CRESCENT (WAS)
#19 - 14% - 1' 43"
#20 - 59% - 1' 52"
DETROIT CORRIDOR
(W) - 0% - 28"
(E) - 45% - 44"
ST. LOUIS CORRIDOR
(W) - 44% - 28"
(E) - 50% - 1' 09"
BUFFALO CORRIDOR
(W) - 24% - 40"
(E) - 72% - 14"
KANSAS CITY CORRIDOR
(W) - 50% - 25"
(E) - 50% - 35"
The results of this period are disappointing, especially in view of the Amtrak campaign to expand its services and routes.
The only services which showed improvement in both measured categories were the eastbound "Lake Shore Limited" and the southbound "Crescent". However, improvement in the "Crescent" is largely due not to better operations but to the addition of more padding in the schedule.
The poorest performers in this period were the eastbound Boston-section of the "Lake Shore Limited" and the westbound DET Corridor both of which scored 0% OT. Both directions of the "Capitol Limited" followed closely with 8% OT.
Of the causes for delays as taken from the 2 Amtrak Twitter sites, the tally was:
Amtrak Mechanical - 47
Host Carriers - 134
3rd Party - 25
Weather - 24
Amtrak Holds - 13
Unforeseen Crew Issues - 14
Cancelled / Annulled - 15
N.O.S. - 354
The last category is inflated due to the Amtrak practice of simply stating that a train is running late without specifying a cause for the delay. Also, there are numerous examples in each route reviewed where a train arrives late at an intermediate station and no reason is given for the delay. Apparently, as long as the excessive padding found in many schedules allows for partial or even complete recovery, Amtrak does not feel that it is necessary to account for any intermediate delays.
NOTE: not all delays are included in the tally as I generally include only those of 30" or more. This amounts to less than half of the total delays seen in the period. I would not begin to try to extrapolate a total number of delays for all services outside of the NEC as it must be humungous!
A continuing disturbing trend is the number of delays attributed to "signal issues". This certainly raises the question of the safety / reliability of the existing signal systems in this era of PTC. Or, is it possible that PTC itself is a causal factor of these delays.
To refer back to a once popular advertising quote: "Inquiring minds want to know."
TOTAL TRAINS =769
ON TIME = 321 (42%)
LATE = 448 (%8%)
AVERAGE DELAY = 49"
Of the late trains:
54% were 29" or less late;
20% were 30" to 59" late;
16% were 1' to 2' late;
10% were more than 2' late; and
<1% had no arrival time shown.
BY ROUTE, WITH ON-TIME % AND AVERAGE DELAY:
CAPITOL LIMITED
#29 - 8% - 1' 08"
#30 - 8% - 1' 10"
CARDINAL (WAS)
#51 - 23% - 1' 21"
#50 - 17% - 1' 18"
PENNSYLVANIAN
#43 - 11% - 37"
#42 - 25% - 24"
LAKE SHORE LIMITED
#49 - 38% - 1' 11"
#48 - 76% - 9"
LAKE SHORE LIMITED (BOSTON / ALBANY)
#449 - 38% - 26"
#448 - 0% - 41"
CITY OF NEW ORLENS
#59 - 76% - 56"
#58 - 85% - 2' 11"
CRESCENT (WAS)
#19 - 14% - 1' 43"
#20 - 59% - 1' 52"
DETROIT CORRIDOR
(W) - 0% - 28"
(E) - 45% - 44"
ST. LOUIS CORRIDOR
(W) - 44% - 28"
(E) - 50% - 1' 09"
BUFFALO CORRIDOR
(W) - 24% - 40"
(E) - 72% - 14"
KANSAS CITY CORRIDOR
(W) - 50% - 25"
(E) - 50% - 35"
The results of this period are disappointing, especially in view of the Amtrak campaign to expand its services and routes.
The only services which showed improvement in both measured categories were the eastbound "Lake Shore Limited" and the southbound "Crescent". However, improvement in the "Crescent" is largely due not to better operations but to the addition of more padding in the schedule.
The poorest performers in this period were the eastbound Boston-section of the "Lake Shore Limited" and the westbound DET Corridor both of which scored 0% OT. Both directions of the "Capitol Limited" followed closely with 8% OT.
Of the causes for delays as taken from the 2 Amtrak Twitter sites, the tally was:
Amtrak Mechanical - 47
Host Carriers - 134
3rd Party - 25
Weather - 24
Amtrak Holds - 13
Unforeseen Crew Issues - 14
Cancelled / Annulled - 15
N.O.S. - 354
The last category is inflated due to the Amtrak practice of simply stating that a train is running late without specifying a cause for the delay. Also, there are numerous examples in each route reviewed where a train arrives late at an intermediate station and no reason is given for the delay. Apparently, as long as the excessive padding found in many schedules allows for partial or even complete recovery, Amtrak does not feel that it is necessary to account for any intermediate delays.
NOTE: not all delays are included in the tally as I generally include only those of 30" or more. This amounts to less than half of the total delays seen in the period. I would not begin to try to extrapolate a total number of delays for all services outside of the NEC as it must be humungous!
A continuing disturbing trend is the number of delays attributed to "signal issues". This certainly raises the question of the safety / reliability of the existing signal systems in this era of PTC. Or, is it possible that PTC itself is a causal factor of these delays.
To refer back to a once popular advertising quote: "Inquiring minds want to know."
