EB Capital Limited for November

[Sam Damon]

Bustitution watch, Day 15: #30(16) arrived in Pittsburgh at 6:17a, 47 minutes late. However, #42(17) departed 20 minutes late. This train was 31 minutes late into Altoona, PA after the ride around Horseshoe Curve, arriving at 10:20a. Amtrak.com estimates #42(17) with an on-time arrival in Harrisburg, PA as of this posting.

We note for the record #42(16) departed on time, and also, #30(16) is projected 2:52 late into Martinsburg, WV.

EDIT: Oh, yes. #42(17) was 35 minutes late into Harrisburg, PA. "Amtrak Time" rears its ugly head. Again.

 

[Sam Damon]

Bustitution watch, Day 16: #30(17) arrived in Pittsburgh at 7:25a, 1:55 late. This pushed the departure of #42(18) to 7:52a, 32 minutes late. #42(18) was 27 minutes late into Harrisburg, PA after the ride over Horseshoe Curve, and terminated at New York's Penn Station ten minutes late.

I don't do the Bustitution Watch on Sundays, but for the record, #30(18) arrived in Pittsburgh at 8:40a, 3:10 late. This would have delayed a train departing on #42's schedule, but #42 doesn't run on Sundays. Amtrak #44 departs Pittsburgh at 1:20p.

Bustitution watch, Day 17: #30(19) arrived in Pittsburgh 1:49 late, at 7:19a. (#42 is supposed to depart at 7:20a -- there's that one minute, again.) This late arrival pushed back the departure of #42(20) to 7:35a, 15 minutes late. #42(20) arrived at Harrisburg, PA 11 minutes late, and terminated at NYP nine minutes late.

Finally, we note that #30(16) arrived at Martinsburg, WV 3:46 late. Amtrak.com's train status feature truly defined the term "Amtrak Time"; #30(16) terminated at WAS a full four hours late.

I think this catches things up after an exhausting football weekend for me.

 

[Guest]

Bustitution watch, Day 18: #30(20) arrived in Pittsburgh at 4:55a, 35 minutes early. It departed Pittsburgh at 5:45a, on-time, and arrived in Washington, DC at 1:59p, 29 minutes late (there's that minute, again!).

Coming up: that thrilling Thanksgiving travel time. Stay tuned...

 

[Sam Damon]

Daggumit, forgot to log in on that last post. Grrr.

 

[Sam Damon]

Bustitution watch, Day 19: #30(21) arrived in Pittsburgh at 6:19a, 49 minutes late (there's that minute, again!). It departed Pittsburgh at 6:53a, 1:08 down. As of this posting, #30(21) is due into Martinsburg, WV at 12:40p, 1:20 late.

#42(21) departed Pittsburgh on-time.

 

[Sam Damon]

Bustitution watch, Day 20: #30(22) arrived in Pittsburgh at 6:22a, 52 minutes late. It departed Pittsburgh at 6:41a, 56 minutes down, and terminated in Washington, DC at 2:05p, 35 minutes late.

#42(23) departed Pittsburgh on-time. For the record, #30(21) arrived in Martinsburg, WV at 1:24p, 2:04 late.

 

[Sam Damon]

Bustitution watch, Day 22: #30(23) arrived in Pittsburgh at 6:26a, 56 minutes late. It departed Pittsburgh at 6:50a, 1:05 down, and terminated in Washington, DC at 2:15p, 45 minutes late.

#42(24) departed Pittsburgh on-time at 7:20a.

 

[Sam Damon]

Bustitution watch, Day 23: #30(24) arrived in Pittsburgh at 5:10a, 20 minutes early. It departed Pittsburgh at 5:45a, on-time. Amtrak.com projects #30(24) as arriving at Martinsburg, WV at 11:40a, 20 minutes late; but as of this posting, the website has not been updated. The train could be late by this stop. Then again, it could not be. I shall check later.

#42(24) departed on-time. No watch tomorrow; but I will put #30(25) on the record.

EDIT: #30(24) arrived at Martinsburg, WV 24 minutes late, at 11:44a. It terminated in Washington, DC at 1:17p, 13 minutes early.

 

[Sam Damon]

Putting #30(25) on the record: arrived Pittsburgh at 5:37a, seven minutes off the timecard. The train terminated in Washington, DC at 1:20p, ten minutes early.

Bustitution watch, Day 24: #30(26) arrived in Pittsburgh at 4:57a, 33 minutes early. It departed Pittsburgh at 5:45a, on-time. The train terminated in Washington, DC at 2:30p, 1:00 late.

#42(27) departed Pittsburgh on-time.

 

[Sam Damon]

Bustitution watch, Day 25: #30(27) arrived in Pittsburgh at 5:08a, 22 minutes early. It departed Pittsburgh at 5:45a, on-time. As of this posting, Amtrak.com projects #30(27) into Martinsburg, WV at 11:25a, five minutes late.

 

[Sam Damon]

Bustitution watch, Day 26: #30(28) arrived in Pittsburgh at 5:14a, 16 minutes early. It departed Pittsburgh at 5:45a, on-time. The train terminated at Washington, DC at 1:42p, 12 minutes late.

For the record, #30(27) arrived in Martinsburg, WV at 12:00n, 40 minutes late, and arrived at Washington, DC eight minutes late.

 

[Sam Damon]

Bustitution watch, Day 27: #30(29) arrived in Pittsburgh at 7:30a, 2:00 late. It departed Pittsburgh at 7:58, 2:13 late. The train is projected to arrive in Martinsburg, WV at 1:42p, 2:22 late as of this posting.

The tardy arrival of #30(29) pushed back #42(30)'s departure from Pittsburgh to 7:55a, 35 minutes late. As of this posting, Amtrak.com estimates #42(30) will be on-time into Harrisburg, PA.

EDIT: #42(30) was 19 minutes late into Harrisburg, PA at 1:04p, and terminated at NYP six minutes early.

As for #30(29), the train arrived in Martinsburg, WV 2:58 late, and terminated in Washington, DC at 4:08p, 2:38 late.

 

[Sam Damon]

Bustitution watch, Day 28: #30(30) arrived in Pittsburgh at 6:39a, 1:09 late. It departed Pittsburgh at 6:56, 1:11 late. The train is projected to arrive in Martinsburg, WV at 12:38p, 1:18 late as of this posting.

#42(1) departed on-time.

This concludes the daily bustitution watch, after I record #30(30)'s arrival in Martinsburg, WV. Let's hope it kept Amtrak, CSX, and NS operations folks honest over the month.

I don't plan on watching #29/30 daily and posting here indefinitely, but I'll attempt to monitor it when I have the time. I watched the performance of #29/30 during August of last year; you can find that one in the forum archives. Hopefully this year I'll get around to tabluating statistics. This weekend is the end of prep football, but my work schedule is still goofed up. Perhaps in two weeks I'll have a chance to tabulate, and summarize for those who care.

 

[Sam Damon]

#42(18) departure from Pittsburgh was delayed 45 minutes by a 2:23 late #30(17).

NS is running #29/30 any way the dispatcher feels like it.

One of these days, I'll get around to tabulating statistics...