FMCSA should delay CSA 2010 release
Vicarious liability, misused data are a bad mix
By Henry Seaton
Q We heard that on behalf of some small trade associations you have opposed implementation of Comprehensive Safety Analysis 2010. If so, why?
A Neither I nor the parties I represent oppose in principle the use of CSA 2010 methodology for its intended purpose as a progressive intervention tool to be used by the Federal Motor Carrier Safety Administration in determining which carriers are fit and safe for use. But all parties would acknowledge, I believe, that the CSA 2010 methodology, the data it collects, the weight assigned to that data, the peer groupings and the algorithms used by the agency in coming up with percentile rankings is a complex work in progress; 800 changes to the system were made in August.
On behalf of small carriers, we have expressed a number of different concerns about the science and the math behind the methodology and ultimately want to ensure that the data is as fair and accurate as possible. But that issue is better reserved for the rulemaking proceeding that FMCSA must complete before it can use the methodology for rating carriers.
While ultimately the devil may be in the details, problems with the CSA 2010 methodology are not the source of our angst. Rather, it is what many believe is the premature and unwarranted release of the data to the public as currently scheduled for early December. While the issue of the proposed release of the data may be resolved or in litigation by the time this column is published, it is important that the readers understand that the issue is more nuanced than blanket opposition to CSA 2010 methodology.
Disclosure could cost thousands of carriers business and jobs.
Over the summer, the industry first began to recognize the unintended consequences of public release of CSA 2010 data when provisions began appearing in shipper/broker and shipper/carrier contracts that effectively would terminate the contracting broker’s or carrier’s access to business if the carrier was marginal or deficient in any of the seven CSA 2010 Behavior Analysis and Safety Improvement Categories (BASICs) when published or if the broker used such carriers.
The reason for these contractual provisions and the consequences on the industry as a whole immediately became clear. Large shippers, brokers and equipment providers are frightened of vicarious liability and the possibility that plaintiff’s bar will name them in a truck accident case as liable for having selected or retained unsafe carriers negligently. Large shippers and brokers, and the counsel who advise them, accordingly were alarmed by the release of CSA 2010 data and the real possibility that plaintiff’s bar would use the published data to argue that the shipper or broker was required to second-guess FMCSA’s ultimate decision.
Based upon the enforcement levels set by FMCSA in each of six BASICs – the crash indicator BASIC will not be disclosed publicly – about two-thirds of the for-hire carriers placed in peer groups thus could be barred from access to the marketplace with a resulting loss of business and jobs. It is this unintended consequence of public release of CSA 2010 data that truly is alarming.
Since the decision to release the data in December had the unforeseen consequences of blackballing carriers the agency otherwise found safe to operate, we filed a formal motion to postpone with the agency asking that public release of the data be delayed and the issue be considered as part of the impended rulemaking. That motion can be found at www.transportationlaw.net/CSA2010.html.
To its credit, the agency met with us in October to discuss our concerns and requested proposed acceptable language that would treat our vicarious liability concerns and permit release of the data as scheduled. Unfortunately, the agency’s Nov. 18 notice of its intended modifications, while a step in the right direction, does not allay our concerns or provide a sufficient disclaimer to preclude CSA 2010 data and percentile rankings from being used improperly in vicarious liability lawsuits.
Also of Interest »