Passenger Trains > Train #29 and #30 (28) - Nearly SIX hours late

Train #29 (28) operating nearly six hours late and train #30 (28) operating nearly four hours late. Train #29 reported "mechanical issues" east of Pittsburgh and then had to be re-crewed. Notes below. Did this then affect performanceon  #30 (28)? UPDATE: As of 11:55 PM ET Capitol Train 29 is currently
_ operating approx. 4 hours late due to mechanical issues.

_ As of 5:10 am ET Train 29 remains stopped east of Pittsburgh
_ (PGH) due to crew issues. Updates to come as more information
_ becomes available.

_ UPDATE: As of 5:58 am ET Train 29 is back on the move and
_ is currently operating approximately 5 hours and 50 minutes
_ late.

In a little over four months 29/30 will have the equipment run through with 91/92 , what could possibly  go wrong and how will Ivy City,DC be able to do any kind of off set for equipment that is still out on the road ?  Stay tuned !

Odds might be a little better if it gets 2 engines. 

Must have been voodoo in the air. Westbound Pennsylvanian was running about twenty minutes late after Latrobe when something went wrong. Shows arriving Greensburg, ten miles away, down an hour and fifty-five minutes. Buses then took the passengers to Pittsburgh with an estimated arrival of eight hours five minutes late. At least passengers would have made their connection to 29.

29 experienced low reservior problems with lone ALC-42 327 shortly after leaving Washington.
Between operating at reduced speeds, longer than normal stops at Rockville and Martinsburg
and a recrew somewhere east of Pittsburgh, the train arrived PGH 5 nrs 45 min LT.  Apparently
there was a fax before Alliance, because it started making running times west of there.  An 
Amtrak alert says the train was held west of Toledo for track maintenance,  At last check 29 wss
8 hrs 51 min LT by South Bend.
An experienced ex-rail who say 30 go by a rail cam with an NS unit leading said the Amtrak unit
was banged up - maybe from hitting a tree.
No idea what happened to 43.
Andy
 

Today's Pennsylvanian's 42(29) was deadhead.  Equipment at Horseshoe Curve webcam at 1749 (scheduled before 1000) with NS freight engine.

42(29) was annulled out of PGH this AM and passengers bussed between PGH and HAR.  

Amtrak stole 42(29)'s power for 30(28) which was unable; it was reported with an NS lead unit from PGH, running long hood forward, so limited to 50mph and requiring an extra qualified crew member in the cab.  But it needed an Amtrak unit for HEP.  Now 5 1/2 hours late.

For all you Siemens Charger fans:  30(28) had the AMTK 132.  Sorry.

IMAGES: Screen capture of 42(29)



Edited 4 time(s). Last edit at 04/29/24 16:08 by GenePoon.

---

---

where did the east bound capitol hit a tree in ohio,i saw both glass was busted on hog pen cam

This is confusing.......and surreal too. So where's the corrections in the below:

- Train #43 (28) bound for Pittsburgh never made it there. After lengthy delay, passengers bussed between Latrobe, PA and Pittsburgh, PA. Presume this train had locomotive troubles, but yet its engine was given over to train #30 (29) in Pittsburgh, after it got to Pittsburgh, PA somehow????

- Train #42 (29) was cancelled out of Pittsburgh (it couldn't turn from train #43 from previous day) because it surrendered its locomotive to train #30 (28)??? Train then deadheaded with a freight locomotive back east. Pittsburgh had surely was out of crews.....

- Train #30 (28) bound for Washington DC seemed to have trouble WEST of Pittsburgh just after Alliance. Its locomotive failed as well? And then somehow it got train #43/42's locomotive out of Pittsburgh, and proceeded with both Amtrak locomotive and a freight locomotive? 

- Train #29 (28) had the greatest delay and had locomotive troubles seemingly from the start of its journey. Did these locomotive troubles resolve themselves somehow and the train got re-crewed, after being delayed east of Pittsburgh and then finally got under track speed to head to Chicago, only to encounter a track work window delay around Toledo?  

UGH! Amtrak did seem to do some fancy train ops here to try and keep things somewhat moving......bus and/or train or combination thereof!

Seems that things coming and going out of Pittsburgh all had issues between April 28 and April 29! And what trains had ALC42 vs P42s? Not that this may make any difference...... Just seems like a real cluster _____. 
 

Screen grab, 29(28) at Elkhart

---

Assigned power:

29 (28)     AMTK 327
  
30 (28)     AMTK 132

43 (28)     AMTK 118

Train 43(28) arrived deadhead at Pittsburgh at 410am, in plenty of time for its engine to add to 30(28) which arrived at 828am, and if it had a lame traction system but still had HEP, that was all it needed since a NS unit was added to Train 30.

Per Facebook group chatter, P42 118 on train 43 hit the hot box detector after passing Latrobe. . This time, it turned out to be a good hit.  They were allowed to travel at ten mph, when they reached Greensburg the passengers were put on buses. The P42 was set off at Trafford, so it could not have been given to 30 this morning.

Excellent catch of the NS Ace leading at the Curve; would've loved to be trackside.

Andy

GenePoon Wrote:
-------------------------------------------------------

> Amtrak stole 42(29)'s power for 30(28) which was
> unable; it was reported with an NS lead unit from
> PGH, running long hood forward, so limited to
> 50mph and requiring an extra qualified crew member
> in the cab.  But it needed an Amtrak unit for
> HEP.  Now 5 1/2 hours late.


Your sources were 100% wrong.

43’s leader, E/118, was set out for a condemned hot box at Trafford the night before. Passengers were taken off at Greensburg and the equipment eventually made it to Pittsburgh at 4am.

30 hit the tree at Ravenna, OH taking out both windshields on E/132. The NS junker was added, and with ditch lights on the long hood end, was not restricted at all. Train lost more time east of Cumberland due to CSX heat orders.

29’s Chugger couldn’t keep main reservoir pressure. A fix was eventually made but by that time, the Conductor ran out of time.

Posted from iPhone

GenePoon Wrote:
-------------------------------------------------------

> Amtrak stole 42(29)'s power for 30(28) which was
> unable; it was reported with an NS lead unit from
> PGH, running long hood forward, so limited to
> 50mph and requiring an extra qualified crew member
> in the cab.  But it needed an Amtrak unit for
> HEP.  Now 5 1/2 hours late.


Your sources were 100% wrong.

43’s leader, E/118, was set out for a condemned hot box at Trafford the night before. Passengers were taken off at Greensburg and the equipment eventually made it to Pittsburgh at 4am.

30 hit the tree at Ravenna, OH taking out both windshields on E/132. The NS junker was added, and with ditch lights on the long hood end, was not restricted at all. Train lost more time east of Cumberland due to CSX heat orders.

29’s Chugger couldn’t keep main reservoir pressure. A fix was eventually made but by that time, the Conductor ran out of time.

Posted from iPhone

Thanks for clarification. This wasn't making complete sense when all was put together.......

mvrr10 Wrote:
-------------------------------------------------------
> In a little over four months 29/30 will have the
> equipment run through with 91/92 , what could
> possibly  go wrong and how will Ivy City,DC be
> able to do any kind of off set for equipment that
> is still out on the road ?  Stay tuned !

Just don't get your hopes up!

Posted from Android