Oh my . . . you're talking about actually running an express AROUND a local?! Perhaps that was what NorthPenn meant and perhaps not, but I agree that is problematic on a two track line as busy as Septa's main. There are far easier express/local decisions that the dispatchers have been struggling with, particularly the past few years.
- My pet peeve (as I've mentioned in other threads) is Wayne Junction, outbound. Four tracks narrow to two on the main. You can run an express around a local there without any delay to inbound trains, and minimal to the local if it's scheduled to stop. For years, if a local has gotten there ten seconds before an express, the local is sent ahead, and the express meanders behind at 25mph for miles. One time my train (not an official express, but making fewer stops, including skipping Wayne) was even held at Wayne on track 2 while a local pulled in, stopped, discharged and crept over the turnout ahead of us. Just jaw-dropping.
- Inbound out of Glenside, it's the other extreme for the 7:58am (soon to be 8:01) inbound local, which starts at Glenside. It's supposed to wait in its siding for an express to pass, which is perfectly reasonable . . . but it's been held up to TWELVE MINUTES for the express! In that amount of time the local could have been far enough ahead that the express would never catch it, and certainly not before 4 track territory.
To be fair, these issues have not been as bad the past month or so. Could be luck, or perhaps some things are being addressed.
Long-Distance trains are the root of all evil in the known universe.