ALL:
Today's 8 is now running 12 hours late. I assume that #7 was late into Seattle and things cascaded down from there. They lost time in Spokane due to a late #28. Does anyone know the reason for delays? The delays are happening west of Minot.
Ed Burns
3+ hours late leaving SEA lost 6 + at Spokane waiting for 28 that was stuck behind a freight drawbar pull. Can get many details from this link and select train on left side to get delays.
https://asm.transitdocs.com/map
28 also lost time west of Pasco because of power issues, needing to have a BNSF unit added to the point. Across the Northern Corridor, we're seeing a bit of a repeat of 2013-14, when the combination of too much traffic and numerous track projects slowed everything down. That plus the high heat conditions during daytime which only slow freight and passenger speeds that much more. As an example of the many things which compound the tardiness of the Builders as they make their way across the route, yesterday morning had another late 8 leaving Spokane. He got held another hour at Cocolalla, ID, because a westbound was allowed to stop on the Sandpoint bridge and wait for his relief crew at the west end. The doubletrack ahead was full of eastbounds either ready to run or waiting for their own relief crews, so not quite sure how that process could have been handled any better.
Is this the case of "queuing theory" where a system can run smoothly at 50% capacity and maybe 70% capacity? But when it tries to run at 90% capacity all delays are extended. It appears the northern tier is running at capacity and any small glitch becomes a big delay. Glitches are important to avoid when at capacity.
Our community is FREE to join. To participate you must either login or register for an account.