Actually, I should have said it arr. Kingman 24 hrs late and is still sitting there. But OK - JB's Dixieland site archive just takes me back to the same screen I get by clicking on his map, which seems to mean it's not in the archives, i.e. there's no record of it having arrived LAX. No service disruption info about it on Amtrak site (not surprising).Maybe the engine with the gps transponder was set out there. And 3 continued to LA? Not sure. Just a guess. You could do train status check for 3 into LAX for yesterday’s arrival.
Sent from my iPhone using Amtrak Forum
He's seeing this: http://dixielandsoftware.net/cgi-bin/gettrain.pl?seltrain=3&selmonth=11&selday=02&selyear=20173(2) arrived in LAX at 7:52am on the 4th. It is right there using train status on the Amtrak web site. Where the heck are you looking?
Sent from my iPhone using Amtrak Forum
Thanks. And IIRC the manual entry of arr/dep times also explains why so often there's no data for an intermediate station. No one got around to it. So does this mean that the gps data aren't used except on the tracking maps, both Amtrak and the "better tracking map"?I believe what's happening here is a clerical error. Normally, everything is done by computer. But the fall time change is the kind of thing that affects only four trains: 1, 2, 3, 4. It's a lot of programming effort to deal with those overnight trains which go through Arizona, where time doesn't change. So it's just easier to have someone make the time adjustments instead of the computer. Now if you get someone making the change at best only once a year, they're liable to make a mistake - INCLUDING adjusting the wrong train. Once Amtrak posted those times incorrectly, the rest of the computers picked it up.
The spring time change is more of a challenge. In addition to those same four trains, every overnight long distance train which has a scheduled station stop between 2.01 am and 3.01 a.m. has a problem. The problem is that Arrow, Amtrak's reservation system, "knows" that since that hour doesn't exist, then no trains can make a station stop then either. It's a mess. Usually, they just fudge those times.
jb
It may not be a clerical error. It is something that I mentioned in the ASMAD update - improvements to connecting trains search thread:Also sometimes clerical error at CNOC causes the wrong locomotive to get associated with a wrong train casing some hilarious outcomes, like train 5 headed to New York e.g.
Sent from my iPhone using Amtrak Forum
Once the equipment is tubed, it will follow the consist. In other words, if 98's inbound power is designated for 19's outbound power at WAS, it will be entered as such. If WAS has some sort of issue and reassigns the engines to 97 without notifying CNOC (or they don't enter it in a timely fashion), when 97 arrives at ALX, it will override 19's previous entry and show train 19 as being late.While we're at it, does your status page update itself in real time as corrections are made? I bring this up because recently an initial terminal decided to flip flop the consists for two trains without telling anyone. As such, the first train out had the second trains consist and the second train had the first consist.
As the first train traveled up the line, it OSd everything an hour early for the arrival and on time for the departure. These are the times that are picked up by your train trackers. When the second train utilizing the first consist departed, every arrival time on the first train was overridden and showed an hour late.
It was fixed hours later. Would the adjustment show?
Enter your email address to join: