Tag Archives: FTA

USDOT rejects NTSB recommendation to shift WMATA to FRA oversight

US DOT Logo - Image from Wikipedia.

US DOT Logo – Image from Wikipedia.

Well, that was fast. Secretary of Transportation Anthony Foxx rejected the NTSB’s urgent recommendation to shift safety oversight for WMATA to the Federal Railroad Administration. From the Washington Post:

The Transportation Department “does not believe that the NTSB recommendation is either the wisest or fastest way to bring about the necessary safety improvements” at Metro, said Foxx spokeswoman Suzanne Emmerling.

“While we have made similar findings of oversight and management deficiency in recent inspections and audits, we disagree with their recommendation,” she said in an e-mail.

Rather than transfer Metro oversight from one agency to another within the Transportation Department, Foxx has a different plan, Emmerling said. She offered no details of the plan but said, “We are examining all options to make [Metro] safer immediately, and will release a plan very soon.”

Part of the reasoning from Foxx includes the very different characteristics of mainline railroads and rapid transit systems, as well as the different regulatory systems require a different approach. Foxx and the USDOT do not disagree about the first of the NTSB’s conclusions, that WMATA’s safety oversight is inadequate, but he does disagree on the second element: the FRA. The Washington Post cites this statement from the Federal Transit Administration:

“We take all recommendations of the NTSB seriously, but in this case, the NTSB is recommending shifting safety oversight from one agency to another,” the FTA said in a statement. “And these agencies have different authorities and areas of expertise. The NTSB is not wrong to assert that urgent action is needed; we just believe that there is an even more effective and faster way to achieve the safety goals we all share.”

Stay tuned.

UPDATE – Oct 10:

In lieu of the NTSB’s recommendation, Secretary Foxx informed the NTSB that the FTA will take over WMATA Safety Oversight from the Tri-State Oversight Committee effective immediately. This is an unprecedented step for the FTA. You can read Secretary Foxx’s letter here. Part of Foxx’s rationale includes the recognition that “WMATA does not have an understanding or familiarity with FRA regulations,” an implict admission of the wide gulf between regulations appropriate for rapid transit vs. those on the books for mainline railroads.

According to the letter, the FTA will retain direct safety oversight until WMATA’s jurisdictions can create an effective State Safety Oversight agency. This is not a new recommendation; the creation of a new, independent safety oversight agency was proposed following the 2009 Fort Totten crash and mandated by Federal law in 2013. WMATA’s contributing jurisdictions have been slow to act in creating, empowering, and funding this agency, dubbed the Metro Safety Commission.

WMATA, the NTSB, and the FRA: or, what do you mean the Metro doesn’t count as a railroad?

FRA Type II Safety Glass in a WMATA rail car. Photo from nevermindtheend.

FRA Type II Safety Glass in a WMATA rail car. Photo from nevermindtheend.

Last week, the National Transportation Safety Board issued an urgent recommendation to the US Department of Transportation and the US Congress to re-classify WMATA to be regulated under the authority of the Federal Railroad Administration. The NTSB usually waits until their full report on an incident is complete to make recommendations. If the preliminary conclusions from a report warrant immediate action, they will issue an urgent recommendation – this recommendation falls into the urgent category. The NTSB’s reports are thorough, but usually not released quickly (the full report from WMATA’s June 2009 Fort Totten crash was approved in July 2010). There will likely be more recommendations in the NTSB’s final report.

Looking at the NTSB’s letter, there are two distinct conclusions:

  1. WMATA’s existing safety oversight is inadequate.
  2. The Federal Railroad Administration has the appropriate regulatory tools to address these inadequacies, and therefore should have safety oversight over WMATA.

The letter documents the numerous occassions the NTSB has asked for strengthened safety oversight: “In general, the NTSB investigations of WMATA found that although safety program plans were in place, they were not effectively implemented and overseen.”

The curious part is the specificity of the second recommendation. Instead of suggesting that the existing safety oversight authorities through the Federal Transit Administration be strengthened to include the kinds of tools available to the FRA, the NTSB instead recommended a dramatic shift. The NTSB’s previous investigations specifically recommended that Congress act to increase safety oversight for the Federal Transit Administration:

In the NTSB’s investigation of the June 22, 2009, WMATA accident near the Fort Totten station, we called for increased regulatory oversight of rail transit properties and recommended that the DOT seek the authority to provide safety oversight of rail fixed guideway transportation systems, including the ability to promulgate and enforce safety regulations and minimum requirements governing operations, track and equipment, and signal train control systems.

Unsatisfied with both the pace of progress as well as the likelihood of resolving this conundrum soon, the NTSB is recommending shifting WMATA to the FRA’s jurisdiction as the most expedient option. Neither the legislation to expand safety oversight under the FTA, nor the region’s plans to replace WMATA’s existing safety oversight committee with the Metro Safety Commission would rise to include the regulatory tools available to the FRA:

Based on testimony from representatives of the TOC and the FTA during the NTSB’s June 23, 2015, investigative hearing on the January 12, 2015, WMATA Metrorail accident, the NTSB further concludes that neither the regulatory changes the FTA can make as a result of MAP-21 nor the proposed creation of a Metro Safety Commission will likely resolve the deficiencies identified in safety oversight of WMATA.

The only rapid transit system under FRA regulation is the PATH system connecting New York and New Jersey. Only four rail rapid transit systems that cross state lines – WMATA, the PATCO Speedline between Philadelphia and New Jersey, Metrolink in St. Louis, and PATH.

The NTSB suggests that PATH’s regulation under the FRA is due to the cross-jurisdictional nature of the service, but this doesn’t seem correct. In the NTSB’s accompanying blog post for the letter, they make the case that other transit agencies are regulated under the FRA (even though the use of the plural here is incorrect – there is only PATH):

There is precedent for the FRA oversight of WMATA that we have recommended because there are some transit agencies in this country that are currently under FRA safety oversight. For example, the FRA provides direct oversight over the New York and New Jersey PATH system instead of using state safety oversight agencies.

PATH’s regulatory jurisdiction is an anachronism. Because PATH previously shared a short section of track with the Pennsylvania Railroad, it was also considered a railroad. And while it remains under FRA jurisdiction, it only operates as a rapid transit system under several waivers that grandfather the system from FRA regulations aimed at mainline freight and passenger railroads.

Even with waivers, the impact of this unique set of regulations is substantial:

Before each run, PATH workers must test a train’s air brakes, signals and acceleration, Mike Marino, PATH’s deputy director, said in a telephone interview. When a train gets to its terminus, workers repeat the test.

In addition, every 90 days all of PATH’s rail cars undergo a three-day inspection at a facility in Harrison, New Jersey. Brakes, lights, communications, heating and air conditioning, signals and odometers are all checked, Marino said.

Many of these FRA regulations carry over from past generations of railroading. They’re extraordinarily detrimental to the progress of high-speed rail and passenger rail. This memo gives some regulatory background to the FRA’s role. It specifically discusses light rail transit operations and the potential for shared use of mainline rail tracks (as PATH used to do), and by doing so highlights exactly how many FRA regulations make little sense (by mutual agreement between the FRA and transit operators) for rail transit operations. Numerous waivers of these regulatory requirements would be required from the start.

Like PATH, WMATA is not a mainline railroad. It’s not hard to understand why the NTSB would think that the FRA’s authority to inspect, fine, and shut down non-compliant operators is necessary; but those authorities also come with a rulebook that won’t make much sense to apply to WMATA.

Ultimately, the division between what is under the FRA’s jurisdiction is almost entirely arbitrary:

FRA will presume that an operation is a commuter railroad if there is a statutory determination that Congress considers a particular service to be commuter rail. For example, in the Northeast Rail Service Act of 1981, (3), Congress listed specific commuter authorities. If that 45 U.S.C. 1104 presumption does not apply, and the operation does not meet the description of a system that is presumptively urban rapid transit (see below), FRA will determine whether a system is commuter or urban rapid transit by analyzing all of the system’s pertinent facts. FRA is likely to consider an operation to be a commuter railroad if:

  • The system serves an urban area, its suburbs, and more distant outlying communities in the greater metropolitan area,
  • The system’s primary function is moving passengers back and forth between their places of employment in the city and their homes within the greater metropolitan area, and moving passengers from station to station within the immediate urban area is, at most, an incidental function, and
  • The vast bulk of the system’s trains are operated in the morning and evening peak periods with few trains at other hours.

Examples of commuter railroads include Metra and the Northern Indiana Commuter Transportation District in the Chicago area; Virginia Railway Express and MARC in the Washington area; and Metro-North, the Long Island Railroad, New Jersey Transit, and the Port Authority Trans Hudson (PATH) in the New York area.

Despite PATH’s history, it’s regulated by the FRA because Congress said so. The three specific criteria listed don’t particularly apply to PATH, or WMATA, or any other rapid transit system (nor some mainline rail systems that offer a high level of all-day passenger service).

A few things to note:

The NTSB can only make recommendations. The NTSB is not a regulatory agency, they are charged only with investigating safety-related transportation incidents. Their independence is by design – any regulatory agency must consider both costs and benefits to a regulation, while the NTSB’s purpose is to conduct independent investigations and offer their recommendations solely on the basis of improving safety.

This particular recommendation is for the USDOT to seek reclassification of WMATA as a ‘commuter railroad’ via congressional action. Perhaps in considering any action, Congress might consider addressing the other shortcomings in transit safety oversight.

Despite the FRA’s impact on PATH operations, it’s worth considering if additional safety inspections might help improve WMATA’s operational discipline. The FTA’s Safety Management Inspection report (the first such safety report for the FTA, under the new safety role authorized by Congress as a part of MAP-21 but deemed insufficient by the NTSB) identified several shortcomings in WMATA’s procedures and practices. Stronger safety oversight might help address those problems; the question is if the FRA is the right regulatory body and if their rulebook is the right one to use.

Precisely.

Minneapolis LRV, a project built with New Starts before the total focus on the CEI.  CC image from joelplutchak on flickr.

Minneapolis LRV, a project built with New Starts before the total focus on the CEI. CC image from joelplutchak on flickr.

Following up from previous discussions of precision and accuracy, Elana Schor at Streetsblog delves deeper into the subject.

While addressing the U.S. Conference of Mayors, assistant transport secretary for policy Polly Trottenberg was asked by the mayor of Clearwater, Florida, to outline how the agency might “quantify livability” in its upcoming rulemaking.

“Not everything can be measured,” Trottenberg said, adding that her colleagues wanted to avoid making the “mistake of false precision.”

She also addressed the pitfalls of relying on in-house economic predictions to assess transit projects. Several local rail lines have quickly exceeded initial federal ridership projections, casting doubt on the models used for the so-called New Starts program.

“Sometimes we’ve gotten so tangled up in the perfect mathematical science — we did it in New Starts,” Trottenberg said.

Data is good.  But we cannot limit our information inputs to just quantitative measures.  And when we do use them, we need to understand their limits.  I’m eager to see how the FTA decides to evaluate the livability criteria, but the acknowledgment that the numbers have limits is a big step forward.

Cost-effectiveness

Streetcar tracks, H St NE - CC image from flickr

Streetcar tracks, H St NE - CC image from flickr

Over the past couple of days, there have been lots of reactions to the DOT’s decision to lessen the importance of their cost-effectiveness measures in decisions on new transit starts funding (TTP, Yglesias, TNR, TOW, Streetsblog), almost all of them positive. There are, however, some key points to consider.  With the emphasis on livability as opposed to cost-effectiveness, the question will now be about measuring that livability.  Jarrett Walker notes:

Great news, perhaps, but I look forward to seeing how FTA is going to turn something as subjective as livability into a quantifiable measure that can be used to score projects, particularly since the payoffs lie in development that a proposed transit line might be expected to trigger, but that usually isn’t a sure thing at the point when you’re deciding to fund the line.  And of course, travel time does still matter.

Measurement is indeed the key.  Part of the problem of the Bush Administration’s emphasis on the CEI was an expansive definition of costs and a rather narrow definition of ‘effectiveness.’

The other problem is one that Donald Shoup talks about extensively in his book, The High Cost of Free Parking.  Namely, often imprecise data points are given undue precision in a bias towards quantifiable results and numbers – precision and accuracy are two different things, and it is important not to conflate them:

HOW FAR IS IT from San Diego to San Francisco? An estimate of 632.125 miles is precise—but not accurate. An estimate of somewhere between 400 and 500 miles is less precise but more accurate because the correct answer is 460 miles. Nevertheless, if you had no idea how far it is from San Diego to San Francisco, whom would you believe: someone who confidently says 632.125 miles, or someone who tentatively says somewhere between 400 and 500 miles? Probably the first, because precision implies certainty.

This doesn’t disprove Jarrett’s point – there are still metrics that can be used for more qualitative factors – but the larger issue here is a move away from false precision and towards outcomes that are more accurate – outcomes that better reflect the true (qualitative and quantitative) nature of cities.

With that in mind, it’s interesting to read some reactions published in the National Journal (h/t Planetizen).

Anthony Shorris: The new approach laid out by Secretary Lahood should force a re-thinking of all of our evaluative tools — cost-benefit analysis, alternatives analysis, environmental impact statements — with an eye toward re-balancing them away from an excessive reliance on only those measures that can be readily quantified.  This re-thinking should be inter-departmental (including other agencies and OMB) and inter-disciplinary (including the perspectives of urban planners and designers as well as economists).  One thing the financial crash should have taught us is that there are limitations to even the most seemingly sophisticated financial models, and that apparently crisp spreadsheets are no substitute for the prudent exercise of judgment that the American people have a right to expect of their leaders.

William Millar, APTA: With the action taken by DOT to consider all the factors required by law, transit projects can now be looked at from a holistic perspective. By judging a project on the multiple benefits it offers (i.e. mobility, economic development, environmental impact, land use improvements etc.), a well-rounded and more informed decision can be made. By removing the barrier that the Bush Administration implemented, the process is now in alignment with how it was originally intended to be.

Projects must still be cost effective and meet at least an overall medium rating in project justification and local financing. However, now, instead of a narrow prism through which to judge a project, a wider lens will offer a larger perspective. It should encourage innovative projects to be proposed and funded.