Amtrak On-Time Performance (OTP) Delays Reroutes Annulled

Per the twitter "bird", Amtrak pulled the plug on any services into/out of Chicago due to the Polar Vortex for 01/30 and 01/31.
includes all LD trains and the midwest corridor services except for the Mules between St Louis and Kansas City.

IT was cold enough to freeze BEER!!!

Does anybody know why westbound #313 (1st) on the STL/KCY Corridor lost 5' 55" from Jefferson City to
Sedalia; eastbound #316 lost no time.

Found this on Tweeter:
Missouri River Runner Train 313 is currently stopped due to a disabled freight train in its path outside of Sedalia (SED). We will update as more information becomes available.
That help? Didn't see any updates. Seems like not everything rates a tweet.

Thanks OhioRiver,

I don't know if this line is single- or double-tracked in that area, but #316 eastbound went through with no delay.

Have to wonder why they left #313 sitting for that length of time.

At what point do they just cancel a train? 21 (1) was 10 plus hours leaving CHI due to late turn of equipment.

#48 (1st) eastbound Lake Shore Limited was 6' 30" late Dpg. CHI.

Track closed north of LAX. Surfliners and Starlights having changes. Is this related to the last month's track getting close to washing out by surf?
https://www.amtrak.com/alert/west-servi ... ather.html" onclick="window.open(this.href);return false;

CA got hit with another round of rain storms this weekend,Burn scar mud slides possible

ohioriverrailway wrote:At what point do they just cancel a train? 21 (1) was 10 plus hours leaving CHI due to late turn of equipment.

shlustig wrote:#48 (1st) eastbound Lake Shore Limited was 6' 30" late Dpg. CHI.

Likewise 3 (1) was 12 hours late. Freezing water tanks in the cars was reported to be a factor.

Amtrak Vermonter #54 struck a p/u truck on the tracks at Walpole NH
The southbound Vermonter #57 is showing sold out for Monday 2/4,
which likely indicates that there was damage to the train. Details
on mishap from Northeast Fire News here:

2019-02-03 17:48 EST | NH | CHARLESTOWN |**TRAIN INCIDENT**| ROUTE 12 & 12 A | ONE TRUCK OVER THE GUARD RAILS ONTO THE RR TRACKS, AMTRAK TRAIN CRASHING INTO THE TRUCK ON THE TRACKS. CONDUCTOR REPORTING NO INJURIES ON THE TRAIN, FIRE CHIEF REPORTING NO INJURIES IN THE VEHICLES. M/AID WALPOLE AND NORTH WALPOLE. | NEFA29

Does anybody know what happened to:

Eastbound Wolverine #354 (3rd) that Dp. CHI 4' 50" late and was about 7' late at PNT? and

#302 (3rd) and #303 (3rd) that caused 3' 30" / 4'00" delays between Dwight and Pontiac on the STL Corridor?

Dick H wrote:Amtrak Vermonter #54 struck a p/u truck on the tracks at Walpole NH
The southbound Vermonter #57 is showing sold out for Monday 2/4,
which likely indicates that there was damage to the train. Details
on mishap from Northeast Fire News here:

2019-02-03 17:48 EST | NH | CHARLESTOWN |**TRAIN INCIDENT**| ROUTE 12 & 12 A | ONE TRUCK OVER THE GUARD RAILS ONTO THE RR TRACKS, AMTRAK TRAIN CRASHING INTO THE TRUCK ON THE TRACKS. CONDUCTOR REPORTING NO INJURIES ON THE TRAIN, FIRE CHIEF REPORTING NO INJURIES IN THE VEHICLES. M/AID WALPOLE AND NORTH WALPOLE. | NEFA29

Muddled story on WMUR-TV reported a second train involved - unlikely since the Conn River is single track there. The North Walpole siding starts about 1/2 mile south of the 12/12-A junction. Where Route 12 is next to North Walpole siding the track sits higher than the road, and there's no guardrail. There is a guardrail (clearly visible in WMUR video) along Route 12 where Route 12-A (Langdon Rd.) crosses overhead.

From the Amtweets on 2/13:

@AmtrakAlerts
9h9 hours ago

Wolverine Train 354 is currently stopped at Battle Creek (BTL) due to an unforeseen crew change,

Oops??