home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!olivea!decwrl!pa.dec.com!ucs.indiana.edu!FCHARY
- From: FCHARY@ucs.indiana.edu
- Newsgroups: rec.railroad
- Subject: Re: Amtrak Pere Marquette delayed
- Message-ID: <9301261427.AA08718@inet-gw-2.pa.dec.com>
- Date: 26 Jan 93 14:27:11 GMT
- Lines: 35
- X-Received: by usenet.pa.dec.com; id AA25023; Tue, 26 Jan 93 06:28:11 -0800
- X-Received: by inet-gw-2.pa.dec.com; id AA08718; Tue, 26 Jan 93 06:27:49 -0800
- X-Received: from PRISM.DECnet by PO1.Indiana.EDU; id AA16428
- (5.65c+jsm/2.5.1jsm); Tue, 26 Jan 1993 09:26:31 -0500
- X-To: PO1::"rec.railroad.usenet@decwrl.dec.com"
- X-To: rec.railroad.usenet
-
- From: x92ochs1@gw.wmich.edu
- Newsgroups: rec.railroad
- Subject: Amtrak's reputation(was Amtrak Pere Marquette delayed)
- Message-id: <1993Jan25.215933.7461@gw.wmich.edu>
- Date: 25 Jan 93 21:59:33 EST
-
- In article <1993Jan25.130338.7448@gw.wmich.edu>, x92ochs1@gw.wmich.edu writes:
- > Last night, Amtrak's Pere Marquette(#370) lost it's engine and was
- > stranded in Michigan City for nearly 5 hours until an engine could be
- > sent out to pull the train. This is the second time in less than a week
- > that this train has been delayed by faulty equipment. Last week an their
- > engine died in Hammond, IN and was delayed for several hours. Then the
- > morning after that, the replacement engine was damaged and the train derailed
- > by a flat-bed trailer on a truck in Gary near the steel mills.
-
- So Michigan City remains a "black hole" for Amtrak. In the above incident,
- passengers were bused to Grand Rapids after 4 hours. The engine in question
- was #238, rescued by #299. Just if that wasn't enough, train 353's engine
- 282 failed about a mile north of where 371's engine failed. The train was
- towed on 355 (engine #401).
-
-
- > P370-24, as CSX designates it, arrived at St. Joseph MI at 12:53 am, rather
- > than 8:11 pm as it is supposed to.
-
- > This, in addition to last month's wreck in Stevensville and the general
- > trend to be behind schedule have taken a toll on Amtrak's reputation.
- > After last month's wreck, many people said that they had taken their
-
- Not a good week, I say. At least 365 (Toronto-Chicago) is consistently
- on time (Not like last year when 4 hour delays and Grand Trunk rescue
- engines were common).
-
- Dave Chary
- fbcb@iunsys.iun.indiana.edu
-