But why would FEC be in favor of it? It's a significantly slower train that can't keep a schedule worth a darn and that will be directly competing with their own trains.Frankly, if you can get the CSX-airport connection going (e.g. the planned SunRail connection) and you could successfully platform and run through Amtrak's trains at the planned OIA station, I'd tentatively be in favor of re-routing Amtrak over the new FEC tracks. The problem is that (A') you'd lose several stations (Sebring is more important than Okeechobee); (B') you'd need to split trains to serve Tampa; and (C') you'd lose Tampa-Miami intrastate traffic, which is a non-trivial consideration. The offset is that you'd knock about two hours off of the Orlando-Miami time, maybe a bit less if you switch back to CSX/Tri-Rail tracks in South Florida.I will say this. MCO is a better location for transfers than Amtrak's ORL. If the monorail happens, and if it connects with Sunrail at Sand Lake Rd., then I'll be the first to advocate moving the Orlando Amtrak station there, whether the current location is historical or not.
What is more important is that the current SunRail plans for connecting to the Orlando Airport Multimodal Center is to a stub end station with no connection to AAF. We heard this from the proverbial horse's mouth when we visited the unRail operations and maintenance center in Debary earlier this year.Indeed, it is not clear why AAF would want such a connection. They have stated several times that they have no interest in going to Tampa, and yet we keep insisting here that that is what they want to do all along. Oh well....But why would FEC be in favor of it? It's a significantly slower train that can't keep a schedule worth a darn and that will be directly competing with their own trains.Frankly, if you can get the CSX-airport connection going (e.g. the planned SunRail connection) and you could successfully platform and run through Amtrak's trains at the planned OIA station, I'd tentatively be in favor of re-routing Amtrak over the new FEC tracks. The problem is that (A') you'd lose several stations (Sebring is more important than Okeechobee); (B') you'd need to split trains to serve Tampa; and (C') you'd lose Tampa-Miami intrastate traffic, which is a non-trivial consideration. The offset is that you'd knock about two hours off of the Orlando-Miami time, maybe a bit less if you switch back to CSX/Tri-Rail tracks in South Florida.I will say this. MCO is a better location for transfers than Amtrak's ORL. If the monorail happens, and if it connects with Sunrail at Sand Lake Rd., then I'll be the first to advocate moving the Orlando Amtrak station there, whether the current location is historical or not.
I can think of two reasons why AAF would want separate Sunrail platforms at the airport station:What is more important is that the current SunRail plans for connecting to the Orlando Airport Multimodal Center is to a stub end station with no connection to AAF. We heard this from the proverbial horse's mouth when we visited the unRail operations and maintenance center in Debary earlier this year.Indeed, it is not clear why AAF would want such a connection. They have stated several times that they have no interest in going to Tampa, and yet we keep insisting here that that is what they want to do all along. Oh well....But why would FEC be in favor of it? It's a significantly slower train that can't keep a schedule worth a darn and that will be directly competing with their own trains.Frankly, if you can get the CSX-airport connection going (e.g. the planned SunRail connection) and you could successfully platform and run through Amtrak's trains at the planned OIA station, I'd tentatively be in favor of re-routing Amtrak over the new FEC tracks. The problem is that (A') you'd lose several stations (Sebring is more important than Okeechobee); (B') you'd need to split trains to serve Tampa; and (C') you'd lose Tampa-Miami intrastate traffic, which is a non-trivial consideration. The offset is that you'd knock about two hours off of the Orlando-Miami time, maybe a bit less if you switch back to CSX/Tri-Rail tracks in South Florida.I will say this. MCO is a better location for transfers than Amtrak's ORL. If the monorail happens, and if it connects with Sunrail at Sand Lake Rd., then I'll be the first to advocate moving the Orlando Amtrak station there, whether the current location is historical or not.
Anyway, forget about Amtrak run-through onto AAF tracks.Won't happen, and there is absolutely no logical reason to make it happen. It would be going against the agreement that AAF had to keep STB off their backs. Besides, Paulus' question is very apt. What exactly is in it for AAF to get a headache of a slower train on their 125mph tracks? Also, Amtrak would not want to have their own toll negotiations with Central Florida Toll Authority now, would they? If Amtrak is to run on FEC they should simply run JAX to Miami.
And BTW, it is Tri-Rail tracks in South Florida south of Mangonia.Park No CSX anymore. The tracks are owned by FDOT and managed by SFRTA and operated by Tri-Rail (reporting mark TRCX). Similarly around Orlando, between Deland and Poinciana, there is no CSX anymore. That segment is dispatched and operated by SunRail from their Debary base. CSX is just another tenent like Amtrak, on that segment. We from the Florida Passenger
Frankly, the issue is that Amtrak is going to lose...I'd say probably about 80% of their "native" south-of-Orlando business at a minimum (e.g. passengers traveling from ORL to points south), if not more. A bus-to-OIA connection to Tampa for FEC would probably make a substantial dent in Amtrak's TPA-MIA business as well. Unlike WAS-NYP (which Amtrak excludes from the LD trains to avoid being swamped with local traffic), ORL-MIA is likely to end up as basically a "ghost town" for the trains if AAF is successful.What is more important is that the current SunRail plans for connecting to the Orlando Airport Multimodal Center is to a stub end station with no connection to AAF. We heard this from the proverbial horse's mouth when we visited the unRail operations and maintenance center in Debary earlier this year.Indeed, it is not clear why AAF would want such a connection. They have stated several times that they have no interest in going to Tampa, and yet we keep insisting here that that is what they want to do all along. Oh well....But why would FEC be in favor of it? It's a significantly slower train that can't keep a schedule worth a darn and that will be directly competing with their own trains.Frankly, if you can get the CSX-airport connection going (e.g. the planned SunRail connection) and you could successfully platform and run through Amtrak's trains at the planned OIA station, I'd tentatively be in favor of re-routing Amtrak over the new FEC tracks. The problem is that (A') you'd lose several stations (Sebring is more important than Okeechobee); (B') you'd need to split trains to serve Tampa; and (C') you'd lose Tampa-Miami intrastate traffic, which is a non-trivial consideration. The offset is that you'd knock about two hours off of the Orlando-Miami time, maybe a bit less if you switch back to CSX/Tri-Rail tracks in South Florida.I will say this. MCO is a better location for transfers than Amtrak's ORL. If the monorail happens, and if it connects with Sunrail at Sand Lake Rd., then I'll be the first to advocate moving the Orlando Amtrak station there, whether the current location is historical or not.
Anyway, forget about Amtrak run-through onto AAF tracks.Won't happen, and there is absolutely no logical reason to make it happen. It would be going against the agreement that AAF had to keep STB off their backs. Besides, Paulus' question is very apt. What exactly is in it for AAF to get a headache of a slower train on their 125mph tracks? Also, Amtrak would not want to have their own toll negotiations with Central Florida Toll Authority now, would they? If Amtrak is to run on FEC they should simply run JAX to Miami.
And BTW, it is Tri-Rail tracks in South Florida south of Mangonia.Park No CSX anymore. The tracks are owned by FDOT and managed by SFRTA and operated by Tri-Rail (reporting mark TRCX). Similarly around Orlando, between Deland and Poinciana, there is no CSX anymore. That segment is dispatched and operated by SunRail from their Debary base. CSX is just another tenent like Amtrak, on that segment. We from the Florida Passenger
IIRC the "small bit of blood" AAF has to pay comes to...I think it was something like $1 or so per one-way ticket (so probably $1-2m/yr if only applied to WPB-MCO tickets, and more if applied more generally).I don't think Central Florida Toll folks would care too much about what Amtrak does. A train or two a day which already exists going another way, specially if it does not stop north of WPB would be a wash for them. Although I understand they did extract a small bit of blood out of AAF for their projected MCO - WPB traffic, but then we are talking 32 higher speed trains running highly reliable clockface schedule, which is a different ballgame altogether. I am sure they plan to extract more blood for MCO to Cocoa/Melbourne traffic when the Brevard stations comes into being. It is all based on figures that they had used in the Bond issuing document, so it does make sense.
But I still cannot see why AAF would want to have Amtrak run on the MCO - Cocoa segment. There literally is no positive in it for them and only some amount of dispatching pain. I think Amtrak would be better off concentrating on running JAX to Miami on FEC, even though that too adds dispatching pain for FEC. But I think they might be willing to live with that since there is little that is negative for them otherwise, even if the decided to run their own trains to JAX.
AAF and SunRail may have the same gauge but the platform heights are different. So it wouldn't make much sense for them to try and share platforms.I've got to say...the idea of two same-gauge rail systems on more or less the same level entering the same station from the same side and not connecting is truly facepalm-worthy. At least when this is done with, say, a subway system it's usually because the lines are on separate levels. I would really think it would make more sense to have AAF and SunRail use a single double-track line to access the station...it isn't like either of them would likely ever have the traffic to overload such a line.
Point taken. I'm frankly so used to "everyone uses the low platform" station situations with Amtrak (at least, from WAS southwards) that this didn't even jump to mind.AAF and SunRail may have the same gauge but the platform heights are different. So it wouldn't make much sense for them to try and share platforms.I've got to say...the idea of two same-gauge rail systems on more or less the same level entering the same station from the same side and not connecting is truly facepalm-worthy. At least when this is done with, say, a subway system it's usually because the lines are on separate levels. I would really think it would make more sense to have AAF and SunRail use a single double-track line to access the station...it isn't like either of them would likely ever have the traffic to overload such a line.
There may well be some emergency track connection, permitting for example the transfer of track maintenance trains. But such would be by mutual agreement bettween the two railroads.
Perhaps the fact that they have different height platforms, and also that they approach the station from two completely different directions have any bearing on this?I've got to say...the idea of two same-gauge rail systems on more or less the same level entering the same station from the same side and not connecting is truly facepalm-worthy. At least when this is done with, say, a subway system it's usually because the lines are on separate levels. I would really think it would make more sense to have AAF and SunRail use a single double-track line to access the station...it isn't like either of them would likely ever have the traffic to overload such a line.
Explorations on Google Earth and in real life show that when two railroads approach one another, and there isn't already a connection some way further up or down, that there is often a physical connection between the two at the easiest location. I guess in the bigger picture of things extra switches don't cost much and you never know when you might need them. If such switches are padlocked and clipped they don't interfere with anybody's signals and you can dispatch both sides as if there wasn't a connection but still transfer stuff when an emergency or special situation arises. Sometimes you even find spurs connecting museums or metros to freight railroads. Apart from maybe the once in 30 years delivery of new trains, I cannot see any purpose in that.Perhaps the fact that they have different height platforms, and also that they approach the station from two completely different directions have any bearing on this?I've got to say...the idea of two same-gauge rail systems on more or less the same level entering the same station from the same side and not connecting is truly facepalm-worthy. At least when this is done with, say, a subway system it's usually because the lines are on separate levels. I would really think it would make more sense to have AAF and SunRail use a single double-track line to access the station...it isn't like either of them would likely ever have the traffic to overload such a line.
Also why would you unnecessarily put in additional switches and signals where none are really needed for the currently planned operational pattern. By keeping them separate, the SunRail side can be dispatched from Debary and the AAF side from wherever they dispacth AAF and the two centers do not need to do any coordination. That would seem to be a significant simplification and money saver.
So for me, if they did connect at MCO that would have been more of a facepalm than what they are doing now. But then again, I guess I am more of a "what does it take to operate this efficiently while providing the best service" kinda guy.
But the same argument goes for working with Tri Rail. They use low platforms like SunRail.Point taken. I'm frankly so used to "everyone uses the low platform" station situations with Amtrak (at least, from WAS southwards) that this didn't even jump to mind.AAF and SunRail may have the same gauge but the platform heights are different. So it wouldn't make much sense for them to try and share platforms.I've got to say...the idea of two same-gauge rail systems on more or less the same level entering the same station from the same side and not connecting is truly facepalm-worthy. At least when this is done with, say, a subway system it's usually because the lines are on separate levels. I would really think it would make more sense to have AAF and SunRail use a single double-track line to access the station...it isn't like either of them would likely ever have the traffic to overload such a line.
There may well be some emergency track connection, permitting for example the transfer of track maintenance trains. But such would be by mutual agreement bettween the two railroads.
AAF is probably going to tell Tri-Rail to spring for low-level platforms at various stops (and/or work out agreements to add high-level platforms if/when AAF seeks to add infill stations).But the same argument goes for working with Tri Rail. They use low platforms like SunRail.Point taken. I'm frankly so used to "everyone uses the low platform" station situations with Amtrak (at least, from WAS southwards) that this didn't even jump to mind.AAF and SunRail may have the same gauge but the platform heights are different. So it wouldn't make much sense for them to try and share platforms.I've got to say...the idea of two same-gauge rail systems on more or less the same level entering the same station from the same side and not connecting is truly facepalm-worthy. At least when this is done with, say, a subway system it's usually because the lines are on separate levels. I would really think it would make more sense to have AAF and SunRail use a single double-track line to access the station...it isn't like either of them would likely ever have the traffic to overload such a line.
There may well be some emergency track connection, permitting for example the transfer of track maintenance trains. But such would be by mutual agreement bettween the two railroads.
@andersonAAF is probably going to tell Tri-Rail to spring for low-level platforms at various stops (and/or work out agreements to add high-level platforms if/when AAF seeks to add infill stations).But the same argument goes for working with Tri Rail. They use low platforms like SunRail.Point taken. I'm frankly so used to "everyone uses the low platform" station situations with Amtrak (at least, from WAS southwards) that this didn't even jump to mind.AAF and SunRail may have the same gauge but the platform heights are different. So it wouldn't make much sense for them to try and share platforms.I've got to say...the idea of two same-gauge rail systems on more or less the same level entering the same station from the same side and not connecting is truly facepalm-worthy. At least when this is done with, say, a subway system it's usually because the lines are on separate levels. I would really think it would make more sense to have AAF and SunRail use a single double-track line to access the station...it isn't like either of them would likely ever have the traffic to overload such a line.
There may well be some emergency track connection, permitting for example the transfer of track maintenance trains. But such would be by mutual agreement bettween the two railroads.
jis: My inclination is "how do I reduce costs while not seriously impacting service". SunRail and AAF using entirely separate tracks strikes me as a situation where you're going to end up with several miles of underused double-tracking (SunRail will probably want/need it if their service frequencies go over twice-hourly; AAF seems inclined to double-track the approaches as well...but four tracks on approach seems both unnecessary and probably a waste of space (of which I'm not sure how much they have to work with...I haven't seen detailed site plans for the station yet, but most maps seem to imply a northerly approach for both systems).
I didn't realize this. This makes me understand your previous statements better and indeed I agree it is unlikely that there will be a track connection.SunRail will use the existing ROW used by the power station lead. So I will be surprised if they have a northerly approach since that track skirts the airport to its south, AFAIR just north of 417 but way south of the airport. The siding to the power house passes under 528 quite a ways to the east of the 528/417 interchange. There will be a lead built from it to the west of 417 to get to the station is how it was explained to me by the SunRail folks during our Debary visit. So I can't visualize where the two would run parallel for several miles. Also I got the impression that the airport connection will be a single track possibly even single stub end platform thing to keep the need for scarce funds to the minimum. Nobody knows where it is going to be funded from as of now apparently.
I find the odds of it not at least having either a double platform or a passing siding to be...well, let's just say that not doing so would present real operational issues.SunRail will use the existing ROW used by the power station lead. So I will be surprised if they have a northerly approach since that track skirts the airport to its south, AFAIR just north of 417 but way south of the airport. The siding to the power house passes under 528 quite a ways to the east of the 528/417 interchange. There will be a lead built from it to the west of 417 to get to the station is how it was explained to me by the SunRail folks during our Debary visit. So I can't visualize where the two would run parallel for several miles. Also I got the impression that the airport connection will be a single track possibly even single stub end platform thing to keep the need for scarce funds to the minimum. Nobody knows where it is going to be funded from as of now apparently.
That makes sense. Only having a single track at a single platform seems (A) like it is being overly cheap and (B) runs into all sorts of room for an operational meltdown since you can't get a train inbound until the last one that came in drops off its passengers and more or less gets back to Sand Lake.I think practically speaking they will have a single platform with two tracks at MCO. At least initially there will probably not be a passing siding enroute from the SunRail main line to MCO since an hourly service can be operated without one.
Downtown Tampa to downtown Miami is about 4:30-4:45 hours by car. The problem with driving is that if going to Miami (not so much Ft Lauderdale or WPB), the traffic is horrible the last 20 miles into Miami. I've been in traffic jams on 826 more than I care to remember. Not to mention that on weekends, I-75 can be very busy with congestion from around Ft Myers to Naples.Talkng about the (potential) Tampa extension, I only kust realized by looking at the map that Tampa is actually slightly south of Orlando.Miami to Tampa via Orlanda is thus going to be a bit of a dog leg, with the advantages of high speed being negated by the detour required.Maybe this is why AAF are not actively pursuing thsi right now.Tampa to destinations north makes much more sense though, so maybe Tampa won't start geting serious until after the Jacksonville part has been achieved.
Enter your email address to join: