# Amicus Curiae Brief — Pierce County v. Guillen

> Briefs, arguments, decisions, and more.

URL: https://www.frixlaw.com/law-library/documents/brief%3Amicro_IA40385014_0545%3A17

## Record

- **Collection:** Supreme Court brief
- **Document type:** Amicus Curiae Brief
- **Published:** January 1, 2003
- **Citation:** 537 U.S. 129

## Text

\ Suprome Overt Ua.
\D PILED
ae
No. 01-1229 JUL 3 Mp

In The

Supreme Court of the Ani ates —
+
PIERCE COUNTY,
Petitioner,
V.

IGNACIO GUILLEN, AS LEGAL GUARDIAN FOR
JENNIFER GUILLEN AND ALMA GUILLEN, MINORS;
AND MARIANO GUILLEN, AS LEGAL GUARDIAN FOR

PAULINA GUILLEN,

Respondents.

+

On Writ Of Certiorari To The
Supreme Court Of Washington

S

AMICUS BRIEF OF THE STATE OF LOUISIANA AS
AMICUS CURIAE IN SUPPORT OF PETITIONER

+

RICHARD P. IEYOUB

Attorney General
JOHN C. YOUNG*
JAMES R. DAWSON

Assistant Attorneys General
626 N. 4th Street, Fifth Floor -
Baton Rouge, Louisiana 70804-9095
(225) 342-8717

and

LAWRENCE A. DURANT
General Counsel, State of Louisiana,
Department of Transportation and
Development
P. O. Box 94245
1201 Capitol Access Road
Baton Rouge, Louisiana 70804-9245
(225) 379-1207

*Counsel of Record for Amicus Curiae

COCKLE LAW BRIEF PRINTING CO. (800) 225-6964
OR CALL COLLECT (402) 342-2831 al)
Y 4 id i

Ege Pty Behe Fon Pee Te te te
PRES FasG Mh af >

TABLE OF CONTENTS ~—

Page
eS GI sictetenecnnionintennmnmeniianin i
TAs OF ALTER E EEE ccccccccvcccceccccccccscvcccccocccesene iv
INTEREST OF AMICUS CURIAE .............ccccseceeeeees 1
FO 2
ITE SeeT

—_—— ry

App. 6

Crash Data Elements Collected at the
PRRIIID.. ccccocaccsenescsennscsesneqetasncsseensenenemesenentns 21

Vehicle Data Elements Collected at the
RII... .ccosccsnssesesnenesecnsensenseossemensaneseneetns 29

Person Data Elements Collected at the
IN... ssssanadnensenenendasnsunniatnusdanesatenseeennant 41
Crash Derived Data Elements ................. 53
Vehicle Linked Data Element .................. 57
Vehicle Derived Data Elements................ 57
Person Linked Data Elements ................. 61
Roadway Linked Data Elements.............. 63
EOD —occccccncscsnsncssessnssnsneneoescsossnsnssssnsonessenseesens 72
LIST OF APPENDICESG.............ccsssscccssseseeereesseeeeesers 102
Appendix A: State and Province Codes........... 102
Appendix B: Dates and Times .................0:+++++ 105
Appendix C: Names .............:ccccccceeeeeeeeeeeeeeeeees 106
Appendix D: Addresses...............::ccsseseeeeeeeeees 108
Appendix E: Vehicle Damage Areas................ 110

Appendix F: Violation and Conviction Codes.. 111
Appendix G: Data Elements Useful for Data

LAM AGO...0.00ccscccccccccescccccesscorccccsessssooecssessssoosese 118

Appendix H: Diagram of Trafficway ............... 120

Appendix I: Definitions for Truck Configura-

tions and Placards ..............cccceccccrcccreceeseeeeeess 121

Appendix J: Diagram of Work Zone Area........ 122
* - -

App. 7

Executive Summary

Statewide motor vehicle traffic crash data systems provide
the basic information necessary for effective highway and
traffic safety efforts at any level of government — local,
state or federal. State crash data are used to perform
problem identification, establish goals and performance
measures, determine progress of specific programs, and
support the development and evaluation of highway and
vehicle safety countermeasures.

Unfortunately, the use of state crash data is often hin-
dered by the lack of uniformity between and within states.
While standards exist for collection of crash data, their use
and application is inconsistent. For example, states do not
collect the same information on their crash reporting
forms, crash and data element definitions may differ,
similar data elements may have different meanings,
and/or others may have the same meanings but different
values. Inconsistent data within a state, or between
multiple states, can result in incorrect interpretations,
thus limiting the usefulness of the information.

Many states have recently revised their crash data report-
ing form, and others are now in the process of doing so.
Several states, during their revision process, have con-
tacted National Highway Traffic Safety Administration
(NHTSA) or Federal Highway Administration (FHWA)
seeking guidance. At national meetings, there have been
informal] requests for national guidelines for states to use
when revising crash forms or working with software
vendors. The Intermodal Surface Transportation Effi-
ciency Act (ISTEA) of 1991 required DOT to “ensure
national uniform data” and to “establish minimum crite-
ria” for reporting of highway deaths and injuries. Renewal
of this legislation as the 1998 Transportation Equity Act
for the Twenty First Century (TEA21) provides incentives

App. 8

for states developing plans that include implementation of
model data elements approved by the Secretary of Trans-
portation. |

NHTSA and FHWA are cooperating with the National
Association of Governors’ Highway Safety Representatives
(NAGHSR) to develop model minimum uniform crash
criteria (MMUCC). Development of MMUCC has been
structured to obtain maximum input from all sectors of the
highway safety community. Over a 20 month period, a
straw model was proposed and then revised according to
feedback received at meetings, via the Web, email, phone,
mail, etc. before producing this final version. ©

MMUCC includes 75 minimum data elements that need to
be collected by police at the crash scene and an additional
38 data elements that can be derived (11 data elements)
from those that are collected at the scene or obtained by
linking (27 data elements) to other data files, e.g., roadway
data, injury data, etc. The total 113 data elements repre-
sent a “model” data set which can be expanded as neces-
sary to meet a state’s specific needs.

A study of the feasibility of implementing MMUCC evalu-
ated the data elements collected by the 17 states providing
crash data to NHTSA for its State Data System. These
seventeen states are currently collecting about 60% of the
75 MMUCC data elements needing to be collected by
police at the scene. And on average, they collect an addi-
tional 28 data elements not included in MMUCC.

Implementation of MMUCC will facilitate improved crash
data for highway and traffic safety injury control and
public health purposes at the local, state, and federal
levels.

* - *

App. 9

Acknowledgments

The development of the Model Minimum Uniform Crash
Criteria (MMUCC) is being sponsored by the National
Association of Governors’ Highway Safety Representatives,
the National Highway Traffic Safety Administration, and the
Federal Highway Administration. Numerous state and local
agencies and organizations have contributed staff to its
development. The participation of the following individu-
als is recognized.

Frank Carlile Florida Department of Trans-
portation

David Dickens Charleston West Virginia
Police

Doug Donscheski Nebraska State Patrol

Scott Falb Iowa Department of Trans-
portation

Rosa Gill North Carolina State Division
of Motor Vehicles

Dick Harmon Iowa Bureau of Emergency

; Medical Services

Don Hillis Missouri Department . of
Transportation

David Kleppe North Dakota State Highway
Patrol

David Lawrence California Center for Child-
hood Injury Prevention

Lance Mathess Ohio State Patrol

Creighton Miller South Dakota Office of Acci-
dent Records

Virginia Department of Motor
Vehicles

Washington Traffic Safety
Commission

Maryland State Highway Ad-
ministration

David Mosley
Phil Salzberg
Manu Shah

a+ Powe

°° SESE NIN»

en -

— <r | ee -

App. 10

James Templeton Texas Department of Public

Robert Thompson

John Watson
Ralph Craft
Dennis Flemons
Carl Hayden
Mike Griffith
Janet Johnson
Sandy Johnson
Janet Kumer
Tina Morgan
Ed Milton
Jack Oates
Barbara Rhea
Jackie Schraf
David Sleet
Carol Tan Esse

Dennis Utter

Safety

Iowa Governor’s Traffic Safety
Bureau

New York State Department
of Transportation

Federal Highway Administra-
tion

National Highway Traffic Safe-
ty Administration

Federal Highway Administra-
tion

Federal Highway Administra-
tion

National Highway Traffic Safe-
ty Administration

National Highway Traffic Safe-
ty Administration

Federal Highway Administra-
tion

National Highway Traffic Safe-
ty Administration

National Highway Traffic Safe-
ty Administration

National Highway Traffic Safe-
ty Administration

National Highway Traffic Safe-
ty Administration

National Highway Traffic Safe-
ty Administration

Centers for Disease Control
and Prevention

Federal Highway Administra-
tion

National Highway Traffic Safe-
ty Administration

David Bozak
Noel Bufe

Charles Compton
Barbara Harsha
Roy Lucke

Gary March
Matt Snyder

Richard Pain
Charles Peltier

Patricia Waller

App. 11

InfoGroup, Inc.
Northwestern University Traf-

fic Institute

University of Michigan Trans-
portation Research Institute
National Association of Gover-
nors’ Highway Safetu Reps
Northwestern University Traf-

fic Institute

March & Associates
International Association of
Chiefs of Police

Transportation Research Board
International Association of
Chiefs of Police

University of Michigan Trans-
portation Research Institute

+

*

_~

~ lll

App. 12

INTRODUCTION

Background

A motor vehicle crash report describes characteristics of
the crash, the vehides and people (drivers, injured and
uninjured occupants and injured pedestrians and bicy-
clists) involved. On it, the police officer also records the
results of his or her investigation of the crash. By using
evidence found at the scene, and by interviewing partici-
pants and witnesses the inveshgating officer may answer
such questions as:

¢ “in what directions were the involved vehicles
and pedestrians moving prior to impact?”;

¢ “What occurred at the time of impact?”; and,

¢ “What factors may have contributed to the
crash?”

Data recorded on crash reports are computerized into a
central, electronic crash data file at the state level. These
statewide motor vehicle crash databases provide the basic
information necessary for developing effective highway
and traffic safety programs. Data from state crash data
systems are used by local, state and federal agencies to:

¢ identify and prioritize highway and traffic
safety problem areas;

¢ assess the effectiveness of laws and programs
intended to reduce the frequency and severity
of motor vehicle crashes and injuries; and,

e assess the relationship between vehide and
highway characteristics, crash propensity, and
injury severity to support either the develop-
ment of countermeasures or their evaluation.

App. 13

At the Federal level individual crash reports also provide
the basis for national crash information systems, either as
the sampling frame or as a source of data. Data from these
national systems are utilized in highway safety decision
making by agencies at all levels of government.

Problem

Crash data lack uniformity between the states and, often,
within a state. Beyond a basic set of data elements, states
collect different data elements on their crash reports.
Where there are similar data elements, they often have
different meanings. Or the names may be the same but
the attribute values vary. Within a state, local police may
interpret crash element definitions differently when
documenting the same type of event. Reporting thresholds
for the types of traffic crash for which data are collected
also differ among states and may even be implemented
differently within a State.

Lack of uniform reporting makes the use and comparison
of state crash data difficult. Different elements and defini-
tions within a state can result in inconsistent data and,
potentially, incorrect interpretations of data. The same is
true when states have different reporting requirements
and dissimilar crash data elements — accurate compari-
sons are difficult, and states can not draw on the experi-
ence of other states. When analyses use two or more state
crash data files, results have to be examined closely to
ensure that they are not due to differences in the data
collected and coded by these states.

Existing national standards for collecting information
about motor vehicle traffic crashes are not uniformly
implemented. The Manual on Classification of Motor

Detintha, :
—

wT) te
ee

App. 14

Vehicle Traffic Accidents, the American National Stan-
dards Institute (ANSI) Standard D16.1, was developed to
“promote uniformity and comparability of motor vehicle
accident statistics.” ANSI Standard D20.1, Data Element
Dictionary for Traffic Records Systems, was developed to
“provide a common set of coding instructions for data
elements related to highway safety ...” While the goals of
these standards are to promote uniformity and compara-
bility of motor vehicle traffic crash statistics, their use and
application is inconsistent between states and even within
a state.

States periodically revise their crash reporting forms_tIn a_
recent study conducted by the National Association of
Governors’ Highway Safety Representatives (NAG HSR)
for the National Highway Traffic Safety Administration
(NHTSA), eighteen states indicated that they are in the
process of revising their crash reporting form, or will
revise it, by 2000. Many are being spurred to do so by the
availability of new technclogies such as hand-held com-
puters for data collection. Others are doing so in an effort
to reduce the reporting and processing burden on state
and local police agencies. Several states, during their
revision process, have contacted NHTSA or the Federal
Highway Administration (FHWA) to inquire as to what
elements these agencies -ecommend to be collected on
crash reporting forms. At recent national meetings and
forums, traffic safety information collectors and users have
asked for guidelines for states to use when revising their
crash forms or when working with software vendors. The
National Safety Council’s (NSC) Traffic Records Commit-
tee studied the issues related to collection and use of
highway safety information and issued a report entitled A
NATIONAL AGENDA for the Improvement of Highway

App. 15

Safety Information Systems. Goal VI of the National
Agenda calls for establishing and promoting “technical
standards of highway safety information systems.” It
specifically recommends promoting “the use of . . . existing
standards and other recommended guidelines.”

Section 2002(a) of The Intermodal Surface Transportation
Efficiency Act of 1991 (ISTEA) addressed the issue of
collection and reporting by states of data on traffic related
deaths and injuries and directed the Secretary to establish
a program collecting such information from the states. It
stated that, “The purposes of the program are to ensure
national uniform data on such deaths and injuries and to
allow the Secretary to make determinations for use in
developing programs to reduce such deaths and injuries
and making recommendations to Congress concerning
legislation necessary to implement such programs.” The
section went on to say that “The Secretary shall establish
minimum reporting criteria for the program;”

The traffic and highway safety communities were asked to
respond to the legislative language in Section 2002(a) of
the ISTEA by means of a federal regulatory notice. Re-
sponders indicated support of uniformity as a concept, but
not as a federal requirement. ISTEA was renewed in June
1998 as the Transportation Equity Act for the 21st Cen-
tury (TEA21). This legislation requires the Secretary of
Transportation to recommend model data elements for
crash reporting and provides funding incentives to states
which demonstrate in a plan how they will implement
them.

—,)

-

App. 16

Benefits of MMUCC to the Highway Safety Com-
munity

Uniform criteria, if adopted by states, would assist all
levels of users. The advantages of the standardized,
statewide elements and definitions introduced by MMUCC

include:

e Easier to support state and local highway safety
programs because of more consistent and accurate
data;

e Possibility for interstate comparisons and analyses;

e Improved collaboration across health and transporta-
tion sectors resulting in improved crash data for public
health and injury control purposes;

e Enhanced decision making for targeting resources as
part of 402, Safe Communities, etc., implementing per-
formance measures, and evaluaiing program effective-
ness;

e Feasibi!ty of linkage to medical outcome global posi-
tioning systems, and other highway traffic safety related
data, thereby helping identify the cost of specific crash,
vehicle, roadway and person characteristics and, ulti-
mately, who pays;

e Collaborative approach so that states learn from each
other by sharing their successes, identifying their
common problems and working together on joint pro-
gram priorities;

e Routine monitoring of emerging problems or issues as
changes, such as vehicle or highway modifications, are
implemented; and,

e Development of common software for crash data entry.

App. 17

At the national level, comparable state data would expand
NHTSA and FHWA analytical capabilities. The collection
and coding of information in Federal data systems, most of
which are used by state and local agencies, would improve,

possibly leading to further revisions and economies in eae
the data are collected.

bad * x

App. 18
LIST OF MODEL MINIMUM
UNIFORM CRASH CRITERIA

Crash Data Elements Collected at the Scene ........... 21
| Cl. Crash Case Identifier ..................:c:00eeeeee 21
; C2. Crash Date and Time .................ccccccceeees 21
; I cca 21
C4. Crach City Piac)........cccccccccscccscccccccccccsccces 22
C5. Crash Roadway Location ...............:0c:00++ 22
. Oe, | | aaa 22
. C7. Location of First Harmful Event ............. 23
C8. Manner of Crash/Collision Impact........... 23
' C9. Source of Information. .................::s0++ 24

: C10. Date and Time Crash Reported to Police
j AGENCY ............cccccccrcrrescccerseeresessenseeseesscees 24
C11. Weather Comdition ........c0cccccccccccccsscsssccee 24
‘ C1S. Asmbbbemt LAGI ..ccccccccccccccccccccccccesescescosseses 25
; C13. Road Surface Condition....................0:0008 25
: C14. Contributing Circumstances, Environment... 26
C15. Contributing Circumstances, Road.......... 26
C16. Type of Roadway Junction. ..................0++ 26
0) A 27

C18. Work Zone Related (Construction/Main-
Ree RFN) .ccoccccccccvecccsnccccscsscccscessecess 27
Vehicle Data Elements Collected at the Scene ......... 29
Vl. Vehicle Unit Number Unique toCrash.... 29
V2. Vehicle registration State and Year......... 29
V3. Vehicle License Plate Number................. 29
We, —«-_ Fre BD cecccccncccnccescosscuvesctnenecscesosenine 29

V5. Commercial Trailer Registration State
ted TERED .ccccccusicscnesntesenecnsiaennadeaabaenaiiaa 30

V6. Commercial Trailer License Plate Num-
Ta iasaamaeesiaindteinc tea iinestaieiaes emmeiaineetniiaiacaiaaiaaila 30
x: 30

App. 19

V8. Carrier Street Address ..................::ccc0008 31
V9. Carrier Identification Number................. 31
V10. Vehicle Configuration.....................:cc00008 31
IIIT TIED cn scccnsconcscncsesssonsesooossoes 32

V12. Gross Vehicle Weight Rating of Power
ELLE 32
V13. Total Occupants In vehicle...................... 33
ee 33
eee Ee 33

V16. Hazardous Materials Placard (Cargo
EE eee EE 34

V17. Hazardous Materials Released (Cargo
EE 34
V18. Vehicle Authorized Speed Limit.............. 35
V19. Direction of Travel Before Crash............. 35
V20. Traffic Control Device Type..................... 35
V21. Vehicle Maneuver/Action......................04. 36
I aicrnininnccccencnesescqnsscosocees 36
V2S. Sequence of Events..............ccccccccoccscssecees 37
V24. Most Harmful Event for this Vehicle....... 38
V25. Direction of Force to Vehicle.................... 39
V26. Underride/Override ....................cccceeeeeeees 39
Vee. BOBS TIGERS ATOR 0000050ccccccccccccscccccccceces 40
Too scans ensesseucooosonoosecs 40
Person Data Elements Collected at the Scene.......... 41
Level 1: All Persons Involved ....................cccceeeeeees 41
ea 41
i renensnannnnsen 41
ss crrermensensnnnneee 41
a 42
ons cc ccctucuessanncnqneoessoeese 42

P5. Occupant’s Vehicle Unit Number Unique
EEE 42
i cnc mennenemenenscoscocosees 42
P7. Occupant Protection System Use............. 43
sn ccscctnesneossunenescosncsosossess 43
EE 44

—

App. 20

A, SE .cccnensenvennsnsensussoousssesnnsnesneasseusnssten 44
I i rnticiceetrrrenererteetnmneess 44
P1l. Driver License State/Province ................. 44
P12. Driver License Number ........................4+. 45
Teen 45
P14. Contributing Circumstances, Driver........ 45
Se a 46
Eee noe 46
SE eeneeeoEre 47
Level 4: All Drivers and Non-motorists................. 47
P18. Alcohol/Drug Suspected ...................000008 47
eee eree 48
TIE WIth cccncusnsnacnnsconsnsneesneenussensoenscsesssanenetens 48
Ae IIs nesrerrnernrannemenenmnnneneinennsts 49
P21. Non-motorist Number........................00005 49
5 SEE 49
P23. Non-motorist Action .................ccccccceeeeeees 49

P24. Contributing Circumstances, Non-
EE eer 50
P25. Non-motorist Condition .........................4 50
P26. Non-motorist Location Prior tolmpact.... 51
P27. Non-motorist Safety Equipment.............. 51
P28. Number of Vehicle Striking Non-motorist 52
I Oe Gare ID ccccncccercscnprenesescsssssemsensssesecssscees 52
P29. Transported to Medical facility By........... 52
Crash Derived Data Elements........................:cc0c0000 53
is SITE ocnssscnsnsgpensuscnensnnenssansnesnenieett 53
Ye ome 53
CD3. Number of Motorists. .......................::cceeeeee 54
CD4. Number of Non-motorists........................... 54
CD5. Total Nonfatal Injuries ...........................4 54
A 55
CD7. Alcohol/Drug Involvement.......................... 55
Be i cceccncasecnnntnnenssencseccensqesnsetinssesen 55

App. 21

Vehicle Linked Data Element.......................cccsseeeeees 57
VL1. Vehicle Identification Number ................... 57
Vehicle Derived Data Elements.........................0c0000 57
Wes RIT TID ccccncssnsenscnnenanenennsevenseces 57
. i — cana emeem 57
VD3. Vehicle Body Type................ccccccccssecessseeees 58
Person Linked Data Elements.........................c.0000e0 61
re I iiainccnnitinirterniirneteanccneasenmumiennennes 61
PL1. Driver License Claas .........ccccccccccccccscsceses 61
PL2. Driver License Restrictions..................... 62
PL3. Driver License Status..........................00 62
Level 6: All Injured Persons.......................cccceeeee0s 63
Sf EEC One een 63
ee BN I ccccceccnscntnncnntccnnnescensenie 63
Roadway Linked Data Elements ..........................005. 63
RL1. Bridge/Structure Identification ................ 64
RL2. Horizontal Alignment...........................00. 64
a iinet a iniiniinertniesinintitiies 64
RL4. Part of National Highway System ............ 65
RL5. Functional Classification of Highway ....... 65
Is, ici aia ialiainnaniia 65
RL7. Annual Average Daily Traffic................... 66
RL8. Trafficway Description .........................00. 66

RL9. Average Widths of the Shoulder(s) and
ci ntcieeincintincteaeenhina teint aiaeitintinieciicenaiiaciaiaate 66
RL10. Average Width of Median......................... 67
TEST Ae nee 67
Sy I iicninsttecnieiaialieniandiniadiiiiin 67
RL13. Roadway Lighting ........................cccceeseeee 67
RL14. Pavement Markings, Longitudinal ........... 68
ESS ee nr eeeoen eee 68
RL16. Delineator Presence........................cc00000+ 69
A Enea 69

RL18. Traffic Control Type at Intersection ......... 69

App. 22

GBBT cececcnnccccesceccnscenseescsecseccecsscsessessssssossosees 70
Side-Road Number of Lanes ..................... 70
Mainline Approach Volumes..................... 71
sdepaceannnnnsnmnceemmninmmmnmnnmennunnaents 72

---

Source: Frix Law Library, https://www.frixlaw.com/law-library/documents/brief%3Amicro_IA40385014_0545%3A17. Public record. Not legal advice.
