Amfleet
Engineer
Most noteable come back was the Acela Express OTP. I think it was down around 65% in October, but it is good to see it almost at 85%.
Amtrak OTP Soars 5%
- Thread starter Amfleet
- Start date
Help Support Amtrak Unlimited Discussion Forum:
- Status
EmpireBuilderFan
Lead Service Attendant
Yeah, but my train absolutely tanked. 60% is pretty bad for the Empire Builder. Usually it's up in the 80%+ range. I guess all the problems that the Builder had at the beginning of November really hurt its time performance.
AMTRAK-P42
Conductor
I am most suprised by the California Zephyr. Over the summer months, I counted 1, yes 1, westbound Zephyr over a period of about 110 days that arrived into Emeryville ontime.
battalion51
Engineer
Well Amtrak's measure of on time doesn't mean that it's sitting in Emeryville when the card says it is. Amtrak's definition of on time is one half hour late per railroad that the train operates over. So for example the Vermonter, the New England Central must deliver the train to Palmer/St. Albans within one half hour of the scheduled run time the train is alotted from the time it recieved the train. CSX must deliver the train to Palmer/Springfield within one half hour of the scheduled run time from the time it recieves the train. So in all reality the train could get knocked for half an hour by CSX, New England Central, and from itself, for a grand total of an hour and a half, and it would still be considered "on time."
Amfleet
Engineer
While that may be true (but confusing), this is Amtrak's end-pont OTP. I think if a train is 20 minutes late it is still considered on-time. Corridor trains I think can be 10 minutes late to still be considered on-time.battalion51 said:
Actually Amtrak's on-time stats are based upon mileage traveled, not corridor vs long distance.
Based upon the stats, it seems that any train that runs under 300 miles total is held to a 10 minute tolerance. Any train over 300 miles is held to a 30 minute window. Esentially this means that the Metroliners cannot be more than 10 minutes late and still be on time. However the Acela's that run from Boston to DC can be up to 30 minutes late and still be considered on time. An Acela that terminates or originates at NY however is held to the 10 minute window.
All LD's of course are also held to the 30 minute window.
Battalion is also partially correct when he mentioned each railroad being allowed 30 minutes. Those 30 minute windows are for Amtrak's statistics on how well that host RR is doing for Amtrak. So when Amtrak says the UP is making the trains late, they are using that window for their calculations.
The times are not cumulative however for the entire run. When the LD gets to it's end point, if it's more than 30 minutes behind schedule, then it's considered late.
Based upon the stats, it seems that any train that runs under 300 miles total is held to a 10 minute tolerance. Any train over 300 miles is held to a 30 minute window. Esentially this means that the Metroliners cannot be more than 10 minutes late and still be on time. However the Acela's that run from Boston to DC can be up to 30 minutes late and still be considered on time. An Acela that terminates or originates at NY however is held to the 10 minute window.
All LD's of course are also held to the 30 minute window.
Battalion is also partially correct when he mentioned each railroad being allowed 30 minutes. Those 30 minute windows are for Amtrak's statistics on how well that host RR is doing for Amtrak. So when Amtrak says the UP is making the trains late, they are using that window for their calculations.
The times are not cumulative however for the entire run. When the LD gets to it's end point, if it's more than 30 minutes behind schedule, then it's considered late.
- Status
