The Brightline Model

Brightline is coming! With two trainsets on the property and limited service starting in July, the most interesting passenger rail initiative currently going in the country is set to launch. Although I admit to lingering skepticism of the long-term viability of the high-end, private model of intercity passenger rail, Brightline appears to be on track to get service up and running, and it is at the very least an interesting experiment, a return to the days when railroads made a significant percentage of their revenues from land development (a grand tradition on Brightline’s home railroad).

It’s interesting, then, that Brightline is projecting an image of confidence not just about its initial Miami-West Palm Beach service and the eventual expansion to Orlando, but about prospects for future expansion elsewhere as well. In an interview with Trains Magazine, Brightline execs stressed expansion within Florida–Tampa and Jacksonville being natural targets–but, in the words of interviewer Bob Johnston (no relation), “didn’t rule out” the possibility of taking their model elsewhere in the country as well. What Mike Reininger–formerly president of Brightline, and now moving over to sister company FEC Industries–did tell the magazine, though, is potentially interesting:

“We don’t have any specific targets or notions about markets that Amtrak is serving,” he explains. “Our thesis is that there are major population centers 250 to 350 miles apart that are underserved or don’t have the capacity within their infrastructure systems to respond to (mobility) needs that could benefit from the type of service we are talking about, on a profitable basis as opposed to necessarily a subsidized basis.”

In a separate interview with Railway Gazette, Reininger touched on much the same topic:

‘Florida is not the only area where there are overcrowded roads and interstates’, he pointed out. ‘We are fulfilling our vision here in Florida, but we are not exclusively bound by the state borders. We have a belief that major cities that are 500 to 600 km apart set themselves up as prime candidates for express passenger rail, and can be made to work. We want to apply that throughout the USA.’

While we still don’t know whether Brightline can be successful in its near-perfect situation in Florida–sharing track with a supportive parent freight company that is well-known for its fast, scheduled freights and high-quality infrastructure, a rarity in American railroading–it’s clear that the company is thinking big. Inasmuch as one can speak of a “Brightline model” that could theoretically give American intercity passenger rail a jolt, it would seem to consist of two overarching elements, one of customer service and one infrastructural. On the customer service end, Brightline clearly sees itself as a high-class service; it intends to make money and has invested in high-quality equipment to that end, offering assigned seating and two classes. The more interesting question, to me at least, is infrastructural. Given how near-perfect the FEC situation is for Brightline, are there, indeed, other corridors around the country which their model might fit? From the two interviews above, we can begin to glean a sense of the criteria that Brightline or a similarly minded company might apply in developing a new corridor.

Market:  A service like Brightline can’t just be plopped down anywhere. It has to reach “major population centers” that are currently “underserved” by intercity options, and that are wealthy enough to afford a premium service. Obviously there is some fungibility here, but there are also clearly minimum requirements that need to be met.

Distance: Reininger gave different numbers in the two interviews, but Brightline is clearly looking at mid-length corridors somewhere between 250 and 400 miles in length.

Minimal capex: I could be totally misreading Brightline’s intentions on this one–after all, they do intend to pursue a remarkable investment in a greenfield line to Orlando–but it seems fairly reasonable to say that they could not launch such a risky endeavor without the comfort of having FEC’s minimal-investment-needed to fall back on for the first stage (to be fair, they have sunk significant money into double-tracking and stations). For future expansions, though, it’s probably good to assume that someone operating on the Brightline Model would want to roll out service on a right-of-way that is already well maintained or that can be rehabbed without too much effort, and that allows rollout capital expenditure to be kept to a minimum.

Willing freight partner: This might well be the hardest criterion to meet. Brightline will save money by splitting track maintenance costs with FEC’s freight business, but American Class 1 railroads (the largest of the freight railroads) are notoriously unfriendly to passenger service. Surely, the Class 1s would be willing to negotiate in some circumstance (and might even find themselves relieved to be working with an organization that’s not as dysfunctional as Amtrak), but I suspect that Brightline expansion would come easier in partnership with a regional freight carrier like FEC or a government-owned line. Consider this one a flexible criterion.

Amtrak noncompete: Reininger’s wording in the Trains interview isn’t totally clear, but it doesn’t sound to me like Brightline is interested in immediately kicking off expansion with in-corridor competition with Amtrak. I’d bet that if Brightline expands outside Florida it will be on a corridor not already served by one of Amtrak’s corridor services, or where a state benefactor can kick Amtrak off relatively easily.

Ability to compete with driving: Reininger referred to metro areas that don’t have “capacity within their infrastructure systems to respond to (mobility) needs” in one interview and “overcrowded roads and interstates” in the other, so it’s fair to say that Brightline sees an opportunity to use America’s congestion problem to compete. And competing with driving is certainly easier than competing with flying, especially given Brightline’s choice of diesel-powered equipment on conventional right-of-way.

Given these criteria, then, where can we imagine, in this thought experiment, that Brightline might attempt to expand in the future? I don’t intend this to be in any way a comprehensive list of possible corridors, but it’s a start. The operative assumptions, in addition to the criteria above, are that a) Brightline would continue to operate similar diesel-powered equipment on conventional track and b) the company might eventually be open to partnering with government on some corridors.

The Front Range 

There have been various plans to introduce high-speed rail along Colorado’s Front Range, where much of the state’s population is clustered in a reasonably linear corridor encompassing Fort Collins, Boulder, Denver, Colorado Springs, and Pueblo.

The total length of the corridor is a little below what Brightline seems to be targeting, and much of the necessary existing trackage is controlled by Class 1s that may or may not be amenable to sharing. North of Denver, RTD is already obligated (and coming under fire for delaying) to improve the BNSF line through Boulder and Longmont to Fort Collins and might be open to private investment. South of Denver, the Joint Line offers extra capacity in places, especially with coal traffic on the downturn, but it still has a single-track bottleneck and is controlled by Class 1s. And of course there’s the matter of the foolish decision to turn the through-running Denver Union Station into a stub-end terminal. Still, the region remains wealthy, is growing, has a congestion problem, has shown a willingness to invest in rail, and is positively obsessed with PPP solutions. There’s also significant TOD opportunity–one major way for Brightline to make money–around the downtowns of each city along the Front Range.

Piedmont

Though currently operated by Amtrak, the state of North Carolina plays a significant role in the Piedmont corridor service linking many of the state’s major cities. Indeed, through a quirk of history the state actually owns the tracks. It’s a busy freight corridor, but a growing passenger market that’s also becoming wealthier, and it’s not impossible to envision the state wanting to upgrade passenger service in the future. North Carolina has been sinking money into double-tracking and other infrastructure improvements in recent years, so it’s possible capacity to expand passenger service will exist in the near future.

Hoosier State

This is perhaps the most obvious candidate; despite the collapse of Iowa Pacific’s attempt at running the train five days per week, returns were good during their tenure, and Indiana remains obsessed with privatization. The biggest challenge is certainly infrastructural; the trip from Chicago to Indy is just so sloooowww and CSX, which owns much of the track used, is rarely a cooperative partner. That being said many of the rights-of-way used are very straight and suitable for high-speed running if a private investor thinks they’re worth sinking money into.

Chicago, Fort Wayne, and Eastern

The arrow-straight former Pennsylvania Railroad mainline from Chicago into Indiana and Ohio is often mentioned as a strong candidate for passenger conversion; it is only tenuously necessary for freight service and is in fact leased from CSX to regional railroad CF&E at the moment. That being said CF&E’s rights end in the relative middle of nowhere in Ohio and Fort Wayne itself is a borderline candidate to be the sole terminus of a service operating under Brightline’s model. Access to larger cities in Ohio, such as Columbus or Cleveland, would almost certainly require working with a Class 1. And the line itself needs significant work. There are a lot of ifs here, but the line is in many ways the perfect 125 mph diesel corridor if they can be worked out.

Twin Cities-Duluth

As with the Front Range, there’s an active effort in place to bring passenger trains to this corridor. As with the Front Range, though, the needed ROW is controlled by a Class 1. And the Duluth-Superior area may not be wealthy enough to justify a for-profit premium service. A strong local belief that demand exists persists, though, and if enough money can be scraped together there’s also a parallel, mostly abandoned ROW that could be reactivated.

Memphis-Jackson-New Orleans

This corridor sprang to mind primarily because a large chunk of the northern section is outside of Class 1 control, albeit in horribly decrepit shape. South of Jackson, service in this corridor would need agreement from CN, and the whole region is relatively poor and might not be suited for a high-cost premium service.

Dark Horse: the Moffat Line (Denver-Salt Lake City)

I label this a dark horse mostly because the operating paradigm would be a little different from the other proposed here; the corridor is almost 600 miles long, as opposed to Brightline’s stated ideal of 250-400 miles. But I previously wrote about the Moffat Route’s potential as a passenger-primary corridor, and the decline of coal traffic that prompted that train of thought has only continued apace. This was, after all, the route of the last full-scale privately operated passenger train in the country; the two endpoints enjoy strong demand and cultural ties; and the restored Snow Train has been doing well. At 12-13 hours vs. 8 to drive, the current California Zephyr is not time-competitive, but with some work an improved version dedicated to just this segment might be able to close the gap some, especially in winter. Perhaps a couple of trains per day over the Rockies would complement a Front Range service well. But who knows! The daydreaming is the fun part of this.

Conclusions

The major conclusion I’ve come to in this brief attempt at analysis is that finding a good situation for expansion along the lines of what Brightline envisions in Florida is really, really hard. Many of the “good” corridors are already occupied by Amtrak; while it’s not really that hard to envision a good private-sector operator doing better with some corridor services than Amtrak has, there is significant political inertia behind the national operator. And Amtrak’s fares are, and will be, cheaper, which is a significant concern in areas where trains represent the more downmarket option.

The bigger concern for passenger service expansion, though, is domination of the needed infrastructure by freight railroads. In terms of national policy, it should be noted, this is not necessarily a bad thing; it should be a goal to keep freight on trains and off highways. But it does make rolling out new passenger services exceptionally difficult in many different phases. Brightline has a near-perfect situation going in Florida with the ability to share FEC infrastructure on a friendly basis; ultimately, I suspect, it will remain a Florida-only operation. But who knows! Five years ago, would anyone have expected a privately-funded passenger train operation to make it off the ground at all? If Brightline succeeds, and Texas Central gets off the ground, there might be two running in the US within the next several years. Now that would be something.

 

 

Advertisements

Notes on Boston-Springfield Service

Readers of this blog know I have a particular interest in intercity rail in New England stemming from growing up in New Haven. So when Eitan Kensky sent me a February presentation I hadn’t previously seen from the Northern New England Intercity Rail Initiative (NNEIRI, not to be confused with the Northern New England Regional Rail Association, or NNEPRA, which runs the Downeaster), I was seriously intrigued. There have been numerous efforts over the years to revive the Inland Regional service that Amtrak and predecessors once ran between Boston, Worcester, Springfield, Hartford, and New Haven, and this document presents the general outline of the group’s current vision for the return of such service. Much of the research seems to have been done by contractors HDR, and the predominant vision is clearly that of MassDOT, with secondary input from Vermont and other stakeholders.

NNEIRI study area map

NNEIRI study area map

Massachusetts has, of late, been focused on two major goals for non-Northeast Corridor intercity rail: a link to Montreal and restoration of Inland Regional service. The current study (logically) links these two together. Tough previous service to Montreal has run along the Central Vermont line, turning off the Boston & Albany at Palmer to serve Amherst before heading north through Vermont, the current vision has Boston-Montreal service using the recently rehabbed Connecticut River Line from Springfield to Greenfield before continuing north. It’s a little bit longer, but serves Springfield, Holyoke, Northampton, and Greenfield instead of just Amherst, and takes advantage of the state-owned Conn River trackage.

The predominant challenge to intercity rail in New England is that the trackage is in most places exceptionally curvy. The build alternatives envisioned for the NNEIRI service thus focused on regular-speed trains, with no ambitious plans for even moderate-speed (110 mph) options. It’s important to remember that “maximum speed” here means Maximum Authorized Speed, or MAS, rather than average speed. On curvy legacy tracks the trains are unlikely to obtain the maximum speeds for very long stretches, given FRA restrictions on tilt for conventional equipment (although the 90 mph MAS alternative does make brief mention of the possibility of acquiring tilt equipment).

Table of service alternatives

Table of service alternatives

A Boston-to-Springfield time of right around 2 hours would be extremely competitive with driving, which is about an hour and a half without traffic (yeah, right) and realistically usually at least a half-hour longer. It’s also about the same time as Peter Pan’s bus offerings, but a train would presumably offer a much higher level of comfort and reliability.

Costs would fall in the billion to billion and a half range for the bottom two alternatives, which seems on the high end for relatively simple double-tracking work within an existing right-of-way; I assume most of the capital expenses would be on the Vermont sections, since the B&A right of way is built to accommodate at least two tracks.

nneiri costs

Overall, the conclusion seems to have been that bumping MAS from 79 to 90 mph would result in considerable extra expense with little time saved or gain in ridership. The study team’s Draft Build Alternative is a modified Alt 2, with 79 mph MAS and slightly fewer trains:

draft build alternative

Eight trains per day would run through from New Haven to Boston, a kind of mini-Inland Regional service. These trains would function as extensions of the current New Haven-Springfield shuttle service. There would be one round-trip per day from Boston to Montreal, and another from New Haven to Montreal, while the Vermonter would continue as it currently operates, with an extension to Montreal. Springfield would get 9 round trips per day to Boston, and presumably the New Haven-Montreal train would have a timed connection with a westbound Boston-New Haven train at Springfield, giving Boston in effect two daily round trips to Montreal.

All trains are envisioned to make all local stops, which is interesting to me; I would have run the Inland Regional/shuttles as expresses in Connecticut, stopping only at Hartford. As it is, the additional 9 corridor trips will provided important added frequency to the NHHS/Hartford Line service that should be beginning in 2016. A 2011 NHHS document envisions full cross-ticketing between NHHS and shuttle/Regional trains, and the boost from NHHS’ 25-32 trains per day at launch to 34-41 including the corridor services is nothing to sniff at. However, that many trains would clearly require Connecticut to finish double-tracking the Hartford Line between Hartford and Springfield. That task isn’t itself all that complex but has been deferred to Phase II of the NHHS project (though it is included in Governor Malloy’s 5-year transportation ramp-up plan) because of the  considerable expense of rehabbing the Union Station viaduct in Hartford–which is, somewhat amazingly, believed to no longer be able to hold two trains at once–and the bridge over the Connecticut River.

Interestingly, study staff clearly believe that Springfield-Boston service alone would be a poor use of resources, labeling it “Low Ridership” and “Ineffective and Costly.” As Alex Marshall pointed out on Twitter, much of the envisioned ridership to New Haven is surely people from Worcester or the Metro West region who want a two-seat ride into New York City without doubling back into Boston to catch an NEC train.

Likewise, the study labeled plain Boston-Montreal service “Low Ridership,” while noting the potential for higher ridership in the New Haven-Montreal corridor. Despite decades of pleading for Montreal service, planners still seem to believe that Boston doesn’t quite deserve it. That’s not particularly surprising to me given how slow such service would be and how sparse population is along the corridors between the two cities. So for now, there will likely be just the one round trip per day, plus the possibility of a two-seat ride via transfer in Springfield, and that situation seems likely to stay the same for quite a while.

Other notes

Finish the Cross

As currently planned, the NNEIRI system looks like a sideways T, with the long axis pointing to Boston. I’m on record as a (self-interested) proponent of Albany-Boston service, and I think some of the improvements proposed here strengthen the case for finishing off a cross-shaped network with trains from Boston to Pittsfield and Albany. Double-tracking the Boston Line from Worcester to Springfield would leave less than 100 miles of single track from Springfield to Albany (it’s 102 track-miles, but there are existing sidings and stretches of multiple track). If trains can do Boston-Springfield in 2 hours, a time of 4 hours to Albany should be eminently achievable even without much in the way of speed improvements. With significant speed improvements (most of the line west of Springfield is limited to 40-50 mph, even though the trackage west of Pittsfield isn’t all that curvy or steep) a time in the 3:30 range–which my previous post identified as the time necessary to be competitive–should be achievable. That would open up the possibility of Boston-Toronto service via the Erie Canal corridor cities–a potential market for an overnight train?

Boston Line Capacity

One of the major ongoing dramas in New England intercity rail has been CSX’ reluctance to share the ex-B&A right-of-way with passenger service. Given current constraints, it is somewhat understandable; it’s a steep, curvy line that has suffered from decades of deferred maintenance (yes, part of that is CSX’ fault, but the neglect predates CSX ownership). CSX runs 25-30 trains per day on the line, which approaches the capacity of a mixed-use single-track line, even one equipped with advanced (by freight rail standards) CTC signaling:

From NCHRP Report 773

From NCHRP Report 773, “Capacity Modeling Guidebook for Shared-Use Passenger and Freight Rail Operations”

Double-tracking the line, however, offers enormous potential, jumping the capacity from an estimated 30 trains per day to 75. In other words, CSX could double current traffic–a situation no one sees as being around the corner in New England–and there would still be 15 slots per day for passenger traffic. More realistically, a fully double-tracked B&A could easily accommodate 40 freights, the 8 proposed Inland Regional trips, 6-8 trips to Albany, and the Lake Shore Limited–a total of under 60 trains per day west of Worcester.  Of course, fully double-tracking the line requires the states of Massachusetts and New York to cooperate, and the Cuomo administration has shown little interest in efficient passenger rail.

Pessimistic SPG-NHV times

The table of travel times above envisions a trip time of 1:40 from Springfield to New Haven given all local stops. This seems somewhat pessimistic to me, as the current shuttles and Vermonter are scheduled for 1:20 to 1:30 over the same route; perhaps the longer time takes into account that a few stops will be added under the NHHS scheme, but those should be counterbalanced by improved track speeds; it’s not a big deal, but I’m somewhat confused.

Who’s going to operate it?

Most commentary I’ve seen has assumed that any extension of rail service from Boston to Springfield would be operated by the MBTA. Running the trains through to New Haven would seem to preclude that possibility. Amtrak would seem the most logical choice, but the northeast state haven’t been thrilled with it of late; Connecticut, for example has opened the NHHS service to a bid competition. The NNEIRI network is an extremely complex system, involving at least three states, plus the province of Quebec and federal authorities regulating border crossings, the private railroads owning the tracks, and various other stakeholders. So perhaps now is the time to revive my call for a unified Northeastern passenger rail authority.

 

 

Boston to Albany–How Fast Can A Slow Trip Be?

Personal note: it’s been quite a while since I’ve posted here. Beginning of the semester sucks. But hopefully 2600+ words makes up for it 😉

Expansion of east-west passenger rail service in Massachusetts has been a topic of discussion for quite a long time. Politicians from decaying industrial cities like Worcester, Springfield, and Pittsfield want a reliable connection to Boston’s vibrant economy; travelers want an alternative to the fast-if-there’s-no-traffic-but-there’s-always-traffic Mass Pike, and the state’s liberal voters tend to be more supportive than average of infrastructure projects. There’s also a good bit of nostalgia for Massachusetts’ days as the technological and political haven of American railroading.

Today, there seems to be a good bit of momentum for extension of passenger service west of its current terminus at Worcester. All of the Democratic candidates for governor agree on the necessity of such service, and it given the state’s recent spree of line acquisitions for passenger service, seems likely to happen one of these decades. That seeming momentum got me thinking about the possibilities for a more thorough east-west service along CSX’ Boston Line, the former Boston & Albany division of the New York Central. Service to Springfield is one thing; getting up and over the sparsely inhabited, hilly, and curvy line across the Berkshires to reach Pittsfield and Albany is another entirely.

Of course, I have a personal stake in exploring this possibility; I live in Albany, many of my friends are in Boston, and I would love to have convenient rail service. But is it feasible? The situation I face as a consumer is thus:

  • Google Maps estimates a driving time of 2:39 from my apartment in Albany to South Station. Realistically, you have to leave 3-3.5 hours, because while the Mass Pike is fast and free-flowing from Albany well past Springfield, once you hit the interchange with 84 in Sturbridge, all bets are off.
  • Greyhound offers direct schedules in the 3:30 range, with a stop in Worcester, but there are only a few buses per day in each direction. There are also local Greyhound buses that stop in the Berkshires towns, but they require a transfer in Springfield to get to Boston, and the trip is over 4 hours. All Greyhound buses are subject to Mass Pike delays.
  •  The less said about Amtrak’s lone train on the route, the Boston section of the Lake Shore Limited, the better; this post is about the future. But: it’s currently scheduled for 5:45 eastbound and 5:40 westbound. So there’s that.

My hypothesis is that if a train could get between Boston and Albany in 3:30, it would attract high enough levels of ridership to keep it going; I’d probably ride at that time point. And of course anything faster would be a bonus. But can we get the trains going that fast? Albany to South Station is exactly 200 track miles (compared to 170 on the freeway, a major reason trains have had trouble competing in the corridor), so a 3:30 trip time corresponds to an average speed of 57 mph. On the one hand, 57 mph isn’t a particularly ambitious speed goal. On the other hand, Amtrak’s Lincoln Service, which uses predominantly flat, straight lines with stretches of 110 mph running, is scheduled for a 53 mph average speed between Chicago and St. Louis (over 284 miles), and Empire Service trains between New York and Albany are around 60 mph on average. So to achieve competitive travel times, Boston-Albany passenger trains must achieve average speeds comparable to, or even higher than, those on many of Amtrak’s higher-speed corridor services, many of which face fewer geographic obstacles. Is that doable? Let’s delve in.

As mentioned above, the Boston & Albany corridor is notoriously difficult for high (ish)-speed trains. The route opened in 1841 as one of America’s first long-distance railroads; its climb over the Berkshires also claimed the title of the world’s highest railroad at the time. The routing is tortuous and twisting, following river valleys to find an acceptable grade. That being said, unlike most American railroads (at that time and for about 50 years thereafter) the line was designed to an extremely high standard. Supervising engineer George Washington Whistler (the less-famous parent of the painter) insisted on curves as gentle as possible under the circumstances and clearance of the right-of-way for double-tracking from the very beginning.  In essence, Whistler and the owners of the B&A traded more severe grades for gentler curves–the rival Fitchburg Railroad/Hoosac Tunnel route 40 miles to the north made essentially the opposite choice,  with sharper curves but less severe grades. Those choices have made the B&A an operating nightmare for freight over the years, but they make it not totally hostile to passenger service, unlike the Hoosac Tunnel route.

For our purposes, though, the Hoosac Tunnel isn’t the competitor; the Mass Pike is. And as I already noted, the freeway’s route, built with the advantage of mid 2oth-century technology, is 30 miles shorter than the B&A. Here, too, though, the B&A has at least one advantage. Unlike the Mass Pike, the railroad serves the downtowns of the three major Massachusetts cities along the route–Worcester, Springfield, and Pittsfield–directly. In Worcester and Springfield, freeway spurs lead to downtown, so the distance of the Pike isn’t a big deal, but Pittsfield has no direct freeway access and is a good 20-minute drive off the Pike. The lack of  immediate freeway access also means that buses cannot serve the Boston-Albany corridor in a linear manner. That’s why Greyhound doesn’t run buses between Boston and Albany with stops in Worcester, Springfield, and Pittsfield: the repeated backtracking to the Pike would make it an unacceptably long trip. Additionally, these cities are essentially the only feasible stops on a Boston-Albany service, and they fall nicely into an every-50-miles pattern: Pittsfield is 49 track-miles from Albany, Pittsfield-Springfield is 53 miles, Springfield-Worcester 54, and Worcester-South Station 44. The Lake Shore Limited makes an additional stop at Framingham, halfway between Worcester and Boston; that stop could probably eliminated with a timed transfer to/from a local commuter rail train at Worcester.  The only other possible stops that I can imagine are Palmer, MA and Chatham, NY, but neither really warrants a stop on an intercity train. This is abnormally few intermediate stops for an Amtrak corridor service, which typically stop every 20-30 miles. The less-frequent stops might–might–help trains maintain a higher average speed, even if top speeds aren’t all that great.

But just how fast can we get the trains going? I know I promised not to speak much of the Boston section of the Lake Shore Limited, but its current schedule is the place to start.

LSL Boston Schedule

One thing is immediately clear: this schedule is massively padded in both directions. If, following my division of the line into four segments (Albany-Pittsfield, Pittsfield-Springfield, Springfield-Worcester, and Worcester-South Station), we look at the two terminal segments, we can see the insertion of the padding. Boston–Worcester is scheduled for 1:03 outbound (westbound)–and 2:13 inbound (eastbound). Likewise, Albany-Pittsfield is scheduled for 1:04 eastbound, but 1:59 westbound. If we eliminate the massive padding, we can immediately cut a little over an hour off of the Lake Shore‘s scheduled time, cutting it to a still-uninspiring (and non-competitive) 4:45 or so in each direction. Of course, the padding in the current schedule exists for a reason; the Lake Shore‘s on-time performance is notoriously horrific, earning it the nickname Late Shore Limited. Any scenario that envisions increased passenger traffic will certainly involve re-installing double track along the entire B&A corridor (not a problem in terms of ROW), with the state paying in return for absolute passenger dispatching priority. Planned track improvements now that the state owns the Worcester Line between South Station and Worcester should cut another 15 minutes or so off of travel time, leaving us with a nice, round time of 4:30–still an hour slower than might be considered competitive.

One way to improve travel times is by increasing track maintenance to levels that will allow higher speeds. Currently, MBTA is struggling to boost its portion of the Worcester Line from FRA Class III (6o mph for passenger) to Class IV (80 mph for passenger) standards; but more can certainly be done. Most of the rest of the line seems to be maintained to Class III standards, but the ingredients exist for converting it to allow for higher passenger speeds: the entire line west of Framingham is signalled with (antiquated, but upgradeable) cab signals, and there are relatively few grade crossings due to the age of the line. That being said, upgrading absolute train speeds will have relatively little effect because of the line’s severe curvature; with the exception of the more-or-less tangent 20-mile Palmer-Springfield segment, the limiting factor on train speeds is generally curvature, not track or ballast structure. Certainly, building the theorized second track to Class IV or V (V requires cab signals, but luckily the Boston Line has them) would help, but is there a better way to boost average, rather than absolute, top train speeds?

For the answer to that question, we can turn to the opposite coast, where for the last decade and a half Amtrak has been happily operating tilting Talgo trainsets on behalf of the states of Washington and Oregon on the Cascades. These Spanish-designed trainsets are lightweight (though not as lightweight as they could be, thanks to FRA regulations) and their tilt mechanism allows them to navigate curves faster than conventional trains. Various factors–expense, Talgo’s insistence on doing maintenance itself, mechanical discontinuity with other fleets, lower capacity–have kept the Talgos from being adopted more widely in this country, but they’re a very, very strong fit for a curvy, hilly route like the Boston & Albany. The criteria for their ability to save time are complex, but as this Trains Magazine explainer puts it: “Tilting reduces trip time only when the route has a reasonable concentration of curves with curve speeds between 50 and 80 mph. In this speed range, a Talgo-type train will be able to negotiate a curve at speeds 5-10 mph faster than conventional cars. Generally, tilting does not generate significant time savings unless the curve density on a route is 30 percent or higher.” This description could be written for the B&A. There are virtually no tangents of any significant length, but relatively few of the curves are so sharp that they necessarily drop the speed of the train below 50 mph. Equipping corridor trains on a Boston-Albany route with Talgo trainsets could do a lot to boost average speeds–but how much?

The current Cascades schedule shows Talgo-equipped trains saving only about 10 minutes over the Superliner-equipped Pacific Starlight, but that’s a product of ongoing summer trackwork. Historically, Talgo schedules have saved 35 to 45 minutes, or about 15%, on the 187-mile Seattle–Portland segment, which is actually less curvy than the B&A (Talgos save little to no time on the very straight segments between Portland and Eugene, and only some north of Seattle). Knocking 15% off of the theorized 4:30 unpadded  Lake Shore Limited time would give us a time of 3:50 or so, getting closer to our goal but not quite there yet, and still over an hour longer than a direct Boston-Albany bus. However, as mentioned the Portland-Seattle segment isn’t actually that comparable to the B&A, being less curvy and with lower potential maximum speeds because of the lack of cab signals. And sure, there is no other modern experience with Talgo operations in the US. A theoretical application of Talgo equipment, though, is perhaps the next-best thing, and that’s what we find in Pennsylvania. Found via this Sic Transit Philadelphia post, Samuel Walker of Test Plant managed to get a Talgo engineer’s estimate of time savings from using their equipment on the old Pennsylvania Railroad mainline between Harrisburg and Pittsburgh, a route that in age and alignment is very comparable to the B&A. By the engineer’s calculation, Talgo equipment could cut the 254-mile Harrisburg-Pittsburgh run from 5:30 to 4:10, or from 4:56 to 3:36 if the 34-minute schedule pad is eliminated. That’s a savings of 25% before padding and 28% after. If we cut 25% off of the paddingless 4:30 Boston-Albany running time…we get a time of 202.5 minutes, or 3:22.5–just below the magical (to me!) 3:30 time cutoff. Again, that’s with nothing assumed as to track quality other than the already planned upgrades inside Worcester and the installation of a second track built to Class IV speeds west of Worcester.

Of course, those upgrades are far from nothing–probably on the order of hundreds of millions, if not multiple billions, of dollars. But if Massachusetts can find the money for a second track and signal upgrades along the B&A and if state politicians are willing to negotiate hard with CSX over dispatching priority and if  Amtrak or the state are willing to take a risk on Talgo equipment and if the Talgos prove able to do for the B&A what they could do for Pennsylvania…I see no particular reason that a functional Boston-Albany service couldn’t be established in relatively short order. A time of 3:22 end-to-end isn’t magical, but given that a train would be able to hit Pittsfield, Springfield, and Worcester within that time frame. And while a full 3:22 might be at the high end of the time savings that Talgo can offer, even if the time savings are more in the Cascades range of 15% a combination of new equipment and more extensive track upgrades should be able to get travel times down into the 3:30 range. That’s certainly better than any bus can do while stop at all three intermediate cities.

So I do think a renewed, relatively fast Boston-Albany service is possible. It would require significant investment, but it seems to be doable. The main advantage of a train over buses is that one service will be able to stop at all of the major cities in the corridor. Potentially, such a service could become the backbone of a frequent intercity rail network serving the entire state, with the Boston-Albany trains making connections at Springfield and Pittsfield to DMU services in the Pioneer Valley and Berkshires. That’s far, far in the future, but it would be an enormous mobility “win” for the entire state.

A couple of notes: 

1. One particular challenge for the introduction of Talgo equipment to the line might be the presence of high-level platforms. There’s no question that the next-generation trains on the line will be built for high-levels; South Station, Back Bay, Worcester, and Albany have full high-level platforms and Springfield is getting them as part of the NHHS project, not to mention that Amtrak is going to an all-high-levels policy in the Northeast. Of current intermediate stops, that leaves only Framingham and Pittsfield. In Pittsfield, building a side track for a high-level platform so as to maintain freight clearances shouldn’t be too hard. Framingham is a little more of a challenge; it currently has mini-highs and will still be on a freight clearance route, which perhaps further militates for not stopping there. That being said, Talgos are low-slung and there are no examples of high-level-platform-equipped ones operating in the US, so that might increase costs some.

2. One of the problems with the current setup on the Worcester Line is that, while there are three tracks in segments, much of the ROW was cut down to two tracks from Newton in to accommodate the Mass Pike. There are, further, very few sets of crossovers. One of these things can be remedied; the other realistically cannot. More crossovers it is (this will help MBTA trains more than intercity service!).

3. CSX may not love the idea of ceding half of their ROW for a second track to be committed mostly to passenger trains, but it’s not like Massachusetts doesn’t have leverage. The state has already paid for full double-stack clearance, and along with that carrot can hold out the stick of capital investment in helping the Pan Am Southern Alliance clear the Hoosac Tunnel route for higher speeds and double-stacks. CSX doesn’t want to lose its huge advantage in the Boston market; the state shouldn’t be afraid to play hardball, perhaps even asking CSX to pick up some of the tab for the second track.