16.06.2013 Views

For The Defense, December 2011 - DRI Today

For The Defense, December 2011 - DRI Today

For The Defense, December 2011 - DRI Today

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Trucking Law<br />

FMSCA Safety<br />

Evaluation<br />

By Philip M. Gulisano<br />

and Thomas J. Lang<br />

More data available to the<br />

public and to plaintiffs’<br />

attorneys means motor<br />

carriers must proactively<br />

monitor safety status,<br />

investigate violations and<br />

crashes immediately, and<br />

take corrective action.<br />

CSA—<br />

<strong>The</strong> Final<br />

Version?<br />

We have been talking for some time about “CSA 2010,”<br />

the program created by the Federal Motor Carrier Safety<br />

Administration (FMCSA) to focus attention on the specific<br />

behaviors of drivers and motor carriers that lead to<br />

crashes. <strong>The</strong> program, now just called<br />

“CSA,” which stands for “compliance,<br />

safety, and accountability,” was first rolled<br />

out by the Administration in 2008 for a trial<br />

run in four states: Colorado, Georgia, Missouri,<br />

and New Jersey. In 2009, the FMCSA<br />

added Delaware, Minnesota, Maryland,<br />

Montana, and Kansas. Currently, a portion<br />

of the CSA, the safety measurement<br />

system, is fully active in all 50 states and<br />

warning letters are being received by carriers<br />

in each state. However, all interventions<br />

are not fully implemented in each state due<br />

to the need for additional training of enforcement<br />

staff. <strong>The</strong> FMCSA expects that<br />

all interventions will be fully implemented<br />

shortly. Additionally, the safety fitness determination<br />

prong of CSA must still undergo<br />

federal rulemaking, which we expect<br />

will be released by the FMCSA before publication<br />

of this article. Once all of these steps<br />

are completed, the entirety of the CSA program<br />

should be fully implemented throughout<br />

the entire United States.<br />

<strong>The</strong> CSA program takes a new approach<br />

to the way that information regarding<br />

motor carrier performance such as roadside<br />

inspection data, driver logs, and crash<br />

history is collected and used to attempt to<br />

determine compliance with federal rules<br />

and potential safety issues. This article<br />

presents an overview of the CSA program,<br />

the methodology that it uses to measure<br />

safety compliance and make intervention<br />

decisions, and some potential issues that<br />

all motor carriers and the attorneys advising<br />

them need to understand, not only<br />

to maintain and to reinforce safe driving<br />

practices, but also to take proactive<br />

approaches to litigation.<br />

Patti Gillette, Director of Safety for<br />

the Colorado Motor Carrier Association,<br />

was active on the forefront of the initial<br />

CSA program testing in Colorado and has<br />

extensive experience with the program. Dr.<br />

Gillette travels around the country educating<br />

motor carriers and drivers on the particulars<br />

of the CSA program and agreed to<br />

■ Philip M. Gulisano is a founding member of, and Thomas J. Lang is an associate at, Burden, Gulisano<br />

& Hickey, LLC in Buffalo, New York. Mr. Gulisano has over a decade of experience representing trucking<br />

industry clients in the defense of catastrophic personal injury, cargo and loss transfer claims. He serves as<br />

the webcast chair for the <strong>DRI</strong> Trucking Law Committee. Mr. Lang also focuses his practice on representing<br />

trucking industry clients in defense of personal injury and loss transfer claims.<br />

<strong>For</strong> <strong>The</strong> <strong>Defense</strong> ■ <strong>December</strong> <strong>2011</strong> ■ 71

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!