Standing General Order 2021-01 Incident Report.
You can download Standing General Order 2021-01 incident reports in CSV format from the NHTSA public website.
This file contains the change log to the CSV files and the definitions for each data field.
Understanding the terms and requirements of the General Order, the data it aims to obtain, and the limitationsof those data are crucial for accurate interpretation and analysis. The following should be considered whenreviewing these data and other information. See the Standing General Order on Crash Reporting page on
NHTSA.gov for more details.
• Reporting requirements are different for ADAS and Level 2 ADAS.
• Access to crash data may affect crash reporting.
• Incident report data may be incomplete or unverified.
• Redacted confidential business information and personally identifiable information. Redactions
within the data are noted as “[REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION],”“[MAY CONTAIN PERSONALLY IDENTIFIABLE INFORMATION],” or “[XXX],” depending on the nature of
the material redacted.
• The same crash may have multiple reports.
• Summary incident report data are not normalized.
Change Log• September 16, 2024: Data release of reports received through August 15, 2024.
•

August 15, 2024: Data release of reports received through July 15, 2024.

•

July 15, 2024: Data release of reports received through June 17, 2024.

•

June 17, 2024: Data release of reports received through May 15, 2024.

•

May 15, 2024: Data release of reports received through April 15, 2024.

•

April 15, 2024: Data release of reports received through March 15, 2024.

•

March 15, 2024: Data release of reports received through February 15, 2024.

•

February 15, 2024: Data release of reports received through January 16, 2024.

•

January 16, 2024: Data release of reports received through December 15, 2023.

•

December 15, 2023: Data release of reports received through November 15, 2023.

•

November 15, 2023: Data release of reports received through October 16, 2023. In recent releases,
different versions of a report with more than one version may have been spread across each of thethree CSV files (for ADAS, ADS and OTHER). With this release, clustering of versions has been restored
where all versions of a given report appear only in one of the CSV files for convenience. The latest
version of the report determines which of the three CSV files it goes into.

•

October 16, 2023: Data release of reports received through September 15, 2023.

•

September 15, 2023: Data release of reports received through August 15, 2023.

1•August 15, 2023: Data release of reports received through July 15, 2023.

•

July 17, 2023: Data release of reports received through June 15, 2023. Due to new data elements to
support the Second Amended Standing General Order 2021-01 (which was issued on April 5, 2023 andtook effect on May 15, 2023), the following changes have been made to the CSV reports. Pleasereference the Data Dictionary section of this document for detailed descriptions of the data elements.
oReport Type
 A new “5-Day” report type was added.
 The “Monthly – No Incident” report type was renamed to “No New or Updated Incident
Reports”.
 The “Monthly Update” and “Other Update” were renamed to “Update”.

oADAS/ADS Version
 Renamed the existing ADAS/ADS version field to reflect system level version information
and added two new ADAS/ADS version fields for hardware and software, respectively.
 Relevant fields (all hardware and software fields are new while the system fields are arenaming of the existing fields)• ADAS/ADS System Version (renaming of ADAS/ADS Version)• ADAS/ADS System Version – Unk (renaming of ADAS/ADS Version - Unknown)• ADAS/ADS System Version CBI (renaming of ADAS/ADS Version CBI)• ADAS/ADS Hardware Version• ADAS/ADS Hardware Version – Unk• ADAS/ADS Hardware Version CBI• ADAS/ADS Software Version• ADAS/ADS Software Version – Unk• ADAS/ADS Software Version CBIoOther entities that may be aware of this incident
 Added a new field that identifies any other Reporting Entity/entities that has or should
be expected to submit a report for the same incident.
 Relevant fields (all new)
• Other Reporting Entities?
• Other Reporting Entities? - Unk• Other Reporting Entities? - NAoFederal statutory or regulatory exemption Added a new field that reflects whether the subject vehicle was manufactured,
imported, introduced into interstate commerce, or operated on public roads pursuant
to a Federal exemption or exception.
 Relevant fields (all new)
• Federal Regulatory Exemption?
• Other Federal Reg. Exemption• Federal Reg. Exemption - Unk• Federal Reg. Exemption - NooState or local permit Added a new field to indicate if the reporting entity was operating the subject vehicle
under any permit related to automation issued by a State or local regulatory authority.
 Relevant fields (all new)
2

•
•
o

State or Local Permit?
State or Local Permit

Renamed the “Highest Injury Severity” field to “Highest Injury Severity Alleged”.

•

June 15, 2023: Data release of reports received through May 14, 2023. Due to new data elements to
support the Second Amended Standing General Order 2021-01 (which was issued on April 5, 2023 andtook effect on May 15, 2023), this data release only includes data NHTSA has received through May 14
with the original data elements, rather than through May 15, 2023. Beginning with the data release on
July 17, 2023, new data elements will be included for reports received since May 15, 2023. Detailed
descriptions of the changes will also be included in the change log entry for the July 17, 2023 release(this section of this document).

•

May 15, 2023: Data release of reports received through April 15, 2023.

•

April 18, 2023: A CSV file formatting anomaly was discovered with the April 17th data release (for Report
ID 1042-2343 Version 2 in the SGO-2021-01_Incident_Reports_ADAS.csv file) and fixed. There was nochange to any data.

•

April 17, 2023: Data release of reports received through March 15, 2023. Note: Report ID 30610-4815
Version 1 was submitted by Zoox on February 14, 2023 but was not reflected in last month’s data
release due to a system issue. It was resubmitted on March 14, 2023 and is now included starting withthis month’s data release.

•

March 15, 2023: Data release of reports received through February 15, 2023. In previous data releases,
some reports for a few reporting entities appeared under slightly differing names for the entity. These
have been consolidated for clarity. As a result, all Isuzu, Kia, Lucid, Ghost and QCraft reports now appear
under “Isuzu Motors Limited”, “Kia America, Inc.”, “Lucid USA, Inc.”, “Ghost Autonomy Inc.” and“QCraft.ai”, respectively.

•

February 15, 2023: Data release of reports received through January 15, 2023.

•

January 17, 2023: Data release of reports received through December 15, 2022.

•

December 15, 2022: Data release of reports received through November 15, 2022.

•

November 15, 2022: Data release of reports received through October 15, 2022.

•

October 15, 2022: Data release of reports received through September 15, 2022. This release also
includes updated narratives in some previously released reports.

•

September 15, 2022: Data release of reports received through August 15, 2022. This release also
includes updated narratives in some previously released reports.

•

August 15, 2022: Data release of reports received through July 15, 2022.

•

July 15, 2022: Data release of reports received through June 15, 2022. This release also includes updated
narratives in some previously released reports. Narratives for some reports were cut off due to bad
characters in the text of the narrative in the June 15 initial release.
3•June 15, 2022: Initial release of reports received through May 15, 2022.

Data Dictionary
The following are the data element definitions for the Standing General Order (SGO) 2021-01 CSV files.
Field #
1

Name
Report ID

Type/Size
TEXT(240)2Report Version

NUMBER(9)3Reporting Entity

TEXT(128)

4

Report TypeTEXT(80)

5Report Month

NUMBER(2)6Report Year

NUMBER(4)7Report Submission Date

TEXT(20)

4

Description
A unique report number generated by
NHTSA to track initial and updated reports
for a given incident.
The Incident Report version. When aReporting Entity updates a previously filed
report, a new version is created andsequentially numbered by the portal.
The full name of the Reporting Entity filingthe report. The full name of the Reporting
Entity should match the name of thecompany as it is identified in the SGO.
The Incident Report type, as selected by theReporting Entity. Possible values: 1-Day, 5Day, Monthly, No New or Updated Incident
Reports, 10-Day Update, Update.
The reporting month, as entered by theReporting Entity, as indicated by its two digit
numeric value (01-12). For monthly reports
filed under Request Nos. 2, 3, or 4 of the
SGO, the report month is the month when
the Reporting Entity received notice of anincident or update (Request Nos. 2 or 3) or
did not receive notice of any incidents or
updates (Request No 4). This field will beblank for 1-Day reports.
The reporting year, as entered by theReporting Entity, as indicated by its 4 digits
numeric value. For monthly reports filed
under Request Nos. 2, 3, or 4 of the SGO, thereport year is the year of the month when
the Reporting Entity received notice of anincident or update (Request Nos. 2 or 3) or
did not receive notice of any incidents or
updates (Request No 4). This field will beblank for 1-Day reports.
The month and year in which the incident
report was submitted by the Reporting Entity[MMM-YY]. This is captured by the NHTSA
portal at submission time and is not enteredby the Reporting Entity.

Field #
8

Name
VIN

Type/Size
TEXT(44)

9

VIN - Unknown

TEXT(1)

10

Serial Number

TEXT(128)

11

Make

TEXT(25)

12

Model

TEXT(256)13

Model - Unknown

TEXT(1)14

Model Year

NUMBER(4)15Model Year – Unknown

TEXT(1)

5

Description
The vehicle identification number for the
subject vehicle, as reported by the Reporting
Entity. The entry for Field 8 includes only the
first 11 characters of the VIN because NHTSA
has concluded that the inclusion of the last 6
characters of a VIN is information may leadto the identification of individuals involved ina crash.
The entry for Field 9 reflects whether theReporting Entity reported that the VIN or
serial number is unknown. This field will
include a “Y” if the Reporting Entity reported
that the VIN or serial number was unknown
and will be blank if the Reporting Entity
made no such report.
The serial number, if any, for the subject
vehicle, as entered by the Reporting Entity. A
blank entry for Field 10 typically means that
the Reporting Entity entered a VIN in
response to Field 8 rather than a serial
number in response to Field 10. A blankentry may also mean that the Reporting
Entity reported that the VIN or serial number
was unknown in response to Field 9.
The make of the subject vehicle as branded,
as reported by the Reporting Entity.
The model of the subject vehicle as branded,
as reported by the Reporting Entity.
The entry for Field 13 reflects whether theReporting Entity reported that the model ofthe subject vehicle is unknown. A blank entry
for Field 13 typically means that theReporting Entity entered a model in response
to Field 13. This field will include a “Y” if theReporting Entity reported that the model ofthe subject vehicle is unknown.
The model year of the subject vehicle, asreported by the Reporting Entity.
The entry for Field 15 reflects whether theReporting Entity reported that the modelyear of the subject vehicle is unknown. A
blank entry for Field 15 typically means that
the Reporting Entity entered a model year in
response to Field 15. This field will include a“Y” if the Reporting Entity reported that theField #Name

Type/Size

Description
model year of the subject vehicle isunknown.

16

Same Vehicle ID

TEXT(64)

17

Mileage

NUMBER(9)18

Mileage - Unknown

TEXT(1)

19

Driver / Operator TypeTEXT(80)

A unique identifier generated by NHTSA forthe subject vehicle. Because NHTSA is not
making public the entire VIN for a subject
vehicle, this unique identifier permits data
users to determine whether a subject vehicle
was involved in other reported incidents.
The odometer reading of the subject vehicle
in miles at the time of the incident, asreported by the Reporting Entity.
The entry for Field 18 reflects whether theReporting Entity reported that the mileage ofthe subject vehicle at the time of the incident
was unknown. A blank entry for Field 18
typically means that the Reporting Entity
entered an odometer reading for the subject
vehicle at the time of the incident inresponse to Field 18. This field will include a“Y” if the Reporting Entity reported that themileage of the subject vehicle at the time of
the incident was unknown.
The Reporting Entity’s report of theindividual responsible for the operation,
fallback operation, or any part of the
dynamic driving task (DDT) for the subject
vehicle at the time of the incident. Possible
values Consumer: Any individual who is operating acommercially available Level 2 ADAS / ADS
and is not engaged in any activity on behalfof a motor vehicle or motor vehicle
equipment manufacturer at the time of theincident.
In-Vehicle (Commercial / Test): An individual,
other than a consumer, located within thesubject vehicle.
Remote (Commercial / Test): An individual,
other than a consumer, not located within
the subject vehicle who is capable ofproviding remote driving, fallback, and/or
assistance.
In-Vehicle and Remote (Commercial / Test):
A combination of both In-Vehicle

6

Field #Name

Type/Size

20

ADAS/ADS System Version

TEXT(512)

21

ADAS/ADS System Version - Unk

TEXT(1)22

ADAS/ADS System Version CBITEXT(1)23

ADAS/ADS Hardware Version

TEXT(512)

7

Description(Commercial / Test) and Remote(Commercial / Test) individuals.
None: No individual is responsible for any
part of the DDT at the time of the incident.
Other, see Narrative
Unknown
The Reporting Entity’s report of the systemversion number of the ADAS or ADS in use on
the subject vehicle at the time of theincident. If the entry states “[REDACTED,
MAY CONTAIN CONFIDENTIAL BUSINESSINFORMATION],” this indicates that theReporting Entity has made and submitted aclaim that this information is confidential
business information that is protected frompublic disclosure. This entry does notindicate that NHTSA has adjudicated any
such claim.
The entry for Field 21 reflects whether theReporting Entity reported that the
information requested in response to Field
20 (ADAS/ADS System Version) was
unknown. A blank entry for Field 21 typicallymeans that the Reporting Entity enteredinformation in response to Field 20. This field
will include a “Y” if the Reporting Entity
reported that the information requested in
response to Field 20 was unknown.
The entry for Field 22 reflects whether theReporting Entity made a claim that the
information it submitted in response to Field
20 (ADAS/ADS System Version) constitutes
confidential business information that is
protected from disclosure. A “Y” in Field 22
indicates that the Reporting Entity claimed
that the information it submitted in response
to Field 20 constitutes confidential businessinformation. A blank entry in Field 22
indicates that the Reporting Entity made nosuch claim.
The Reporting Entity’s report of the
hardware version number of the ADAS or
ADS in use on the subject vehicle at the timeof the incident. If the entry states“[REDACTED, MAY CONTAIN CONFIDENTIAL
BUSINESS INFORMATION],” this indicatesField #Name

Type/Size

24

ADAS/ADS Hardware Version - Unk TEXT(1)25

ADAS/ADS Hardware Version CBITEXT(1)26

ADAS/ADS Software Version

TEXT(512)27

ADAS/ADS Software Version - Unk

TEXT(1)

8

Descriptionthat the Reporting Entity has made andsubmitted a claim that this information is
confidential business information that is
protected from public disclosure. This entry
does not indicate that NHTSA has
adjudicated any such claim.
The entry for Field 24 reflects whether theReporting Entity reported that the
information requested in response to Field
23 (ADAS/ADS Hardware Version) was
unknown. A blank entry for Field 24 typicallymeans that the Reporting Entity enteredinformation in response to Field 23. This field
will include a “Y” if the Reporting Entity
reported that the information requested in
response to Field 23 was unknown.
The entry for Field 25 reflects whether theReporting Entity made a claim that the
information it submitted in response to Field
23 (ADAS/ADS Hardware Version) constitutes
confidential business information that is
protected from disclosure. A “Y” in Field 25
indicates that the Reporting Entity claimed
that the information it submitted in response
to Field 23 constitutes confidential businessinformation. A blank entry in Field 25
indicates that the Reporting Entity made nosuch claim.
The Reporting Entity’s report of the software
version number of the ADAS or ADS in use on
the subject vehicle at the time of theincident. If the entry states “[REDACTED,
MAY CONTAIN CONFIDENTIAL BUSINESSINFORMATION],” this indicates that theReporting Entity has made and submitted aclaim that this information is confidential
business information that is protected frompublic disclosure. This entry does notindicate that NHTSA has adjudicated any
such claim.
The entry for Field 27 reflects whether theReporting Entity reported that the
information requested in response to Field
26 (ADAS/ADS Software Version) was
unknown. A blank entry for Field 27 typicallymeans that the Reporting Entity entered

Field #Name

Type/Size

Description
information in response to Field 26. This field
will include a “Y” if the Reporting Entity
reported that the information requested in
response to Field 26 was unknown.

28

ADAS/ADS Software Version CBITEXT(1)

29

Other Reporting Entities?

TEXT(2000)

30

Other Reporting Entities? - Unk

TEXT(1)

31

Other Reporting Entities? - NA

TEXT(1)32

Federal Regulatory Exemption?

TEXT(48)

33

Other Federal Reg. Exemption

TEXT(128)

The entry for Field 28 reflects whether theReporting Entity made a claim that the
information it submitted in response to Field
26 (ADAS/ADS Software Version) constitutes
confidential business information that is
protected from disclosure. A “Y” in Field 28
indicates that the Reporting Entity claimed
that the information it submitted in response
to Field 26 constitutes confidential businessinformation. A blank entry in Field 28
indicates that the Reporting Entity made nosuch claim.
The entry for Field 29 identifies any otherreporting entity/entities that has or should
be expected to submit a report for this same
incident.
The entry for Field 30 identifies any otherreporting entity/entities that has or should
be expected to submit a report for this same
incident as Unknown.
The entry for Field 31 identifies any otherreporting entity/entities that has or should
be expected to submit a report for this same
incident as Not Applicable.
The entry for Field 32 reflects whether thevehicle was manufactured, imported,
introduced into interstate commerce, or
operated on public roads pursuant to a
Federal exemption or exception. Possible
values: Part 555 Exemption (49 CFR 555 and49 U.S.C. 30113), Part 591 Exemption
granted by permission letter from NHTSA,Part 591 Exemption for certifying
manufacturers, FAST Act Exception for
testing or evaluation, Other Federal
Exemption or Exception (specify below).
If “Other Federal Exemption or Exception” isselected, the name of the Federal exemption
or exception is reflected in Field 33.
The entry for Field 33 reflects whether theReporting Entity reported that “Other
Federal Exemption or Exception (specify

9Field #Name

Type/Size

34

Federal Reg. Exemption - Unk

TEXT(1)35

Federal Reg. Exemption - No

TEXT(1)

36

State or Local Permit?

TEXT(48)

37

State or Local Permit

TEXT(128)38

ADS Equipped?

TEXT(48)

39

Automation System Engaged?

TEXT(48)

40

Operating Entity

TEXT(128)

10

Description
below)” was identified in Field 32. The
Reporting Entity shall use this field to provide
the name of the Federal exception.
The entry for Field 34 identifies whether thevehicle was manufactured, imported,
introduced into interstate commerce, or
operated on public roads pursuant to a
Federal exemption or exception as Unknown.
The entry for Field 34 identifies whether thevehicle was manufactured, imported,
introduced into interstate commerce, or
operated on public roads pursuant to a
Federal exemption or exception as No.
The Entry for Field 36 indicates if thereporting entity was operating the subject
vehicle under any permit related toautomation issued by a State or local
regulatory authority. Possible values: Yes,
No, Unknown.
The Entry for Field 37 indicates the name ofState or local regulatory authority permit thereporting entity was operating the subject
vehicle under.
The Reporting Entity’s report of whether the
subject vehicle equipped with an ADS.
Possible values: Yes, No, “Unknown, see
Narrative”.
The Reporting Entity’s report of the highestlevel driving automation system engaged at
any time during the period 30 seconds
immediately prior to the commencement of
the crash through the conclusion of thecrash. Possible values: ADAS, ADS,
“Unknown, see Narrative.”
The Reporting Entity’s identification of theentity constituting the “operator” of thesubject vehicle at the time of the incident.
The term “operator” is defined in the SGO.
The operator may be a different entity thanthe Reporting Entity. Markings of “[XXX]”
indicates some of the information reportedby the Reporting Entity has been redacted by
NHTSA because NHTSA has concluded that it
may constitute (or lead to the disclosure of)
personally identifiable information (PII) thatis protected from disclosure, pursuant to theField #Name

Type/Size

Description
Freedom of Information Act (FOIA), 5 U.S.C.
552(B)(6).

41

Operating Entity - Unknown

TEXT(1)42 - 49

Source42

Source - Complaint/Claim

TEXT(1)43

Source – Telematics

TEXT(1)

44

Source - Law Enforcement

TEXT(1)The entry for Field 41 reflects whether theReporting Entity reported that the
information requested in Field 40 (Operating
Entity) was unknown. indicates whether the
Operating Entity is unknown.
The entries for Fields 42-49 reflect theReporting Entity’s report of the source fromwhich it first received notice of the incident.
Notice is a defined term in the SGO. An entryof “Y” in response to any of Fields 42-49
indicates the source from which theReporting Entity first received notice, asreported by the Reporting Entity.
The entry for Field 42 reflects whether theReporting Entity reported that it firstreceived notice regarding the incident from acommunication of any kind addressed to theReporting Entity and made by a consumer orother individual or a written request or
written demand for relief. A “Y” in Field 42
reflects the Reporting Entity’s report that
this was the source of its first notice of theincident, and a blank entry in Field 42 reflects
the lack of any such report by the Reporting
Entity.
The entry for Field 43 reflects whether theReporting Entity reported that it firstreceived notice regarding the incident from acommunication in the form of electronic
data transmitted from the subject vehicle to
the Reporting Entity. A “Y” in Field 43 reflects
the Reporting Entity’s report that this was
the source of its first notice of the incident,
and a blank entry in Field 43 reflects the lackof any such report by the Reporting Entity.
The entry for Field 44 reflects whether theReporting Entity reported that it firstreceived notice regarding the incident from acommunication in writing, including
communications in electronic form, from alaw enforcement agency. A “Y” in Field 44
11

Field #Name

Type/Size

45

Source - Field Report

TEXT(1)46

Source - Testing

TEXT(1)47

Source - MediaTEXT(1)48

Source - OtherTEXT(1)

12

Description
reflects the Reporting Entity’s report that
this was the source of its first notice of theincident, and a blank entry in Field 44 reflects
the lack of any such report by the Reporting
Entity.
The entry for Field 45 reflects whether theReporting Entity reported that it firstreceived notice regarding the incident from acommunication in writing, including
communications in electronic form, from an
employee or representative of a Reporting
Entity. A “Y” in Field 45 reflects the Reporting
Entity’s report that this was the source of its
first notice of the incident, and a blank entry
in Field 45 reflects the lack of any such reportby the Reporting Entity.
The entry for Field 46 reflects whether theReporting Entity reported that it firstreceived notice regarding the incident from acommunication, including communications inelectronic form, regarding a subject vehicle
that is undergoing evaluation, development,
or validation testing when the incident
occurs. A “Y” in Field 44 reflects theReporting Entity’s report that this was thesource of its first notice of the incident, and ablank entry in Field 46 reflects the lack of any
such report by the Reporting Entity.
The entry for Field 47 reflects whether theReporting Entity reported that it firstreceived notice regarding the incident from a
media organization, either through specificinquiries to the Reporting Entity or through areported account of an incident. A “Y” in
Field 47 reflects the Reporting Entity’s reportthat this was the source of its first notice of
the incident, and a blank entry in Field 47
reflects the lack of any such report by theReporting Entity.
The entry for Field 47 reflects whether theReporting Entity reported that it firstreceived notice regarding the incident from asource other than those identified in Fields
42-49. A “Y” in Field 46 reflects the Reporting
Entity’s report that this was the source of its
first notice of the incident, and a blank entry

Field #Name

Type/Size

Descriptionin Field 46 reflects the lack of any such reportby the Reporting Entity.

49

Source - Other Text

TEXT(128)50

Incident Date

TEXT(20)

51

Incident Date - Unknown

TEXT(1)52

Notice Received Date

TEXT(20)53

Incident Time (24:00)

TEXT(10)54

Incident Time – Unknown

TEXT(1)

55

Same Incident ID

TEXT(64)

The entry for Field 49 reflects the Reporting
Entity’s identification of an “other” source, in
those cases where the Reporting Entity firstreceived notice of the incident from an“other” source, as disclosed in Field 49. A
blank entry in Field 49 typically reflects that
the Reporting Entity did not report that it
first received notice of an incident from an“other” source.
The Reporting Entity’s report of the monthand year the incident occurred [MMM-YY].
The entry for Field 51 reflects whether theReporting Entity reported that the
information requested in Field 50 (IncidentDate) was unknown. A “Y” in Field 51 reflects
the Reporting Entity’s report that thisinformation was unknown, and a blank entry
in Field 40 reflects the lack of any such reportby the Reporting Entity.
The Reporting Entity’s report of the monthand year in which the Reporting Entity firstreceived notice of the reportable incident[MMM-YY].
The Reporting Entity’s report of the local
time at which the incident occurred [24-hourformat].
The entry for Field 54 reflects whether theReporting Entity reported that the
information requested in Field 53 (IncidentTime) was unknown. A “Y” in Field 54 reflects
the Reporting Entity’s report that thisinformation was unknown, and a blank entry
in Field 54 reflects the lack of any such reportby the Reporting Entity.
A unique identifier, generated by NHTSA
based on information in the report, for theincident that is the subject of the report. This
unique identifier permits data users todetermine whether other reports regarding
the same incident were filed by another
Reporting Entity.

13

Field #56

Name
Latitude57

Latitude – Unknown

58

Longitude

59

Longitude – Unknown

60

Address

Type/Size
Description
DECIMAL(15) The Reporting Entity’s report of the latitudeof the incident location in decimal degrees(ex: 38.889747). If the entry states “[MAYCONTAIN PERSONALLY IDENTIFIABLE
INFORMATION],” the information reportedby the Reporting Entity has been redacted by
NHTSA because NHTSA has concluded that it
may constitute (or lead to the disclosure of)
personally identifiable information (PII) thatis protected from disclosure.
TEXT(1)The entry for Field 57 reflects whether theReporting Entity reported that the
information requested in Field 56 (Latitude)
was unknown. A “Y” in Field 57 reflects theReporting Entity’s report that thisinformation was unknown, and a blank entry
in Field 56 reflects the lack of any such reportby the Reporting Entity.
DECIMAL(15) The Reporting Entity’s report of thelongitude of the incident location in decimaldegrees (ex: 38.889747). If the entry states“[MAY CONTAIN PERSONALLY IDENTIFIABLE
INFORMATION],” the information reportedby the Reporting Entity has been redacted by
NHTSA because NHTSA has concluded that it
may constitute (or lead to the disclosure of)
personally identifiable information (PII) thatis protected from disclosure.
TEXT(1)The entry for Field 59 reflects whether theReporting Entity reported that the
information requested in Field 58(Longitude) was unknown. A “Y” in Field 59
reflects the Reporting Entity’s report that
this information was unknown, and a blankentry in Field 59 reflects the lack of any suchreport by the Reporting Entity.
TEXT(128)
The street address or the roadway location
where the incident occurred, as reported by
the Reporting Entity. If the entry states“[MAY CONTAIN PERSONALLY IDENTIFIABLE
INFORMATION],” the information reportedby the Reporting Entity has been redacted by
NHTSA because NHTSA has concluded that it
may constitute (or lead to the disclosure of)
personally identifiable information (PII) thatis protected from disclosure.
14

Field #61

Name
Address - Unknown

Type/Size
TEXT(1)62

City

TEXT(30)

63

City - Unknown

TEXT(1)64

State

TEXT(3)65

Zip Code

TEXT(10)66

Zip Code – Unknown

TEXT(1)

15

Description
The entry for Field 61 reflects whether theReporting Entity reported that the
information requested in Field 60 (Address)
was unknown. A “Y” in Field 61 reflects theReporting Entity’s report that thisinformation was unknown, and a blank entry
in Field 61 reflects the lack of any such reportby the Reporting Entity.
The city where the incident occurred, asreported by the Reporting Entity
The entry for Field 63 reflects whether theReporting Entity reported that the
information requested in Field 62 (City) was
unknown. A “Y” in Field 63 reflects theReporting Entity’s report that thisinformation was unknown, and a blank entry
in Field 63 reflects the lack of any such reportby the Reporting Entity.
The state or territory where the incident
occurred, as reported by the Reporting
Entity.
The 5-digit ZIP code where the incident
occurred, as reported by the Reporting
Entity. If the entry states “[MAY CONTAINPERSONALLY IDENTIFIABLE INFORMATION],”
the information reported by the Reporting
Entity has been redacted by NHTSA because
NHTSA has concluded that it may constitute(or lead to the disclosure of) personallyidentifiable information (PII) that is
protected from disclosure.
The entry for Field 66 reflects whether theReporting Entity reported that the
information requested in Field 65 (Zip Code)was unknown. A “Y” in Field 65 reflects theReporting Entity’s report that thisinformation was unknown, and a blank entry
in Field 66 reflects the lack of any such reportby the Reporting Entity.

Field #67

Name
Roadway Type

Type/Size
TEXT(80)

68

Roadway Surface

TEXT(80)

16

Description
The type of road on which the subject vehicle
was operating at the time of the incident, asreported by the Reporting Entity. Possible
values Highway / Freeway: A divided arterial
highway with full control of access.
Street: Local city or residential road not at anintersection; does not include unpaved orrural roads.
Intersection: An area where two or more
roadways join or cross.
Parking Lot: Dedicated area intended forparking vehicles, including a publicly
accessible road within a dedicated parking
area and on-street parking.
Traffic Circle: A circular intersection, rotary,roundabout, or similar junction in which roadtraffic is permitted to flow in one direction.
Rural Road: Local road outside densely
populated areas; does not include unpaved
roads or a highway/freeway.
Unpaved Road: A roadway where the surface
is not concrete or asphalt.
Unknown.
The roadway surface environmental
conditions at the time of the incident, asreported by the Reporting Entity. Possible
values Dry: No adverse conditions.
Snow / Slush / Ice: The roadway surface was,at a minimum, partially covered with snow,
slush, and/or ice.
Wet: The roadway surface was wet without
any frozen water.
Other, see Narrative
Unknown

Field #69

Name
Roadway Description

Type/Size
TEXT(80)70

Posted Speed Limit (MPH)

NUMBER(5)71

Posted Speed Limit – Unknown

TEXT(1)

72

Lighting

TEXT(80)

17

Description
The roadway conditions, excluding weather
and surface conditions, at the time of theincident, as reported by the Reporting Entity.
Possible values No Unusual Conditions: The roadway did notcontain any unusual anomalies orimperfections.
Traffic Incident: A prior traffic event thatadversely affected normal traffic operations
separate from the reported incident.
Examples include, but are not limited to,traffic crashes, disabled vehicles, and spilled
cargo.
Work Zone: An area of a roadway whereconstruction, maintenance, or utility work
activities are identified by warning signs,
signals, or other indicators.
Missing / Degraded Markings: The roadway
lane markings were missing, degraded, orotherwise altered, not in conjunction with awork zone.
Other, see Narrative
Unknown
The posted speed limit on the roadway
where the incident occurred in miles perhour, as reported by the Reporting Entity.
The entry for Field 71 reflects whether theReporting Entity reported that the
information requested in Field 70 (Posted
Speed Limit (MPH)) was unknown. A “Y” in
Field 71 reflects the Reporting Entity’s reportthat this information was unknown, and ablank entry in Field 71 reflects the lack of any
such report by the Reporting Entity.
The lighting conditions at the time andlocation of the incident, as reported by theReporting Entity. Possible values Daylight: The incident occurred when there
was daylight.
Dawn / Dusk: The incident occurred during
dusk or dawn.
Dark - Lighted: The incident occurred when it
was dark, but street lights were on.
Dark - Not Lighted: The incident occurred
when it was dark, but there were no street
lights.

Field #Name

Type/Size

73 - 81

Weather73

Weather – Clear

TEXT(1)

74

Weather - Snow

TEXT(1)75

Weather - Cloudy

TEXT(1)

76

Weather - Fog/Smoke

TEXT(1)

Description
Dark - Unknown Lighting: The incident
occurred when it was dark, but the presenceof street lights is unknown.
Other, see Narrative
Unknown

The weather or environmental conditions at
the time and location of the incident. A
value of “Y” in any of Fields 73-81 reflects theReporting Entity’s report that the weather
condition was present at the time andlocation of the incident. Multiple weather
conditions may be reported for a single
incident.
The entry for Field 73 reflects whether theReporting Entity reported that there were no
adverse weather conditions at the time andplace of the incident. A “Y” entry in Field 73
reflects the Reporting Entity’s report thatthese conditions were present, and a blankentry in Field 73 reflects the lack of any suchreport.
The entry for Field 74 reflects whether theReporting Entity reported that it wassnowing at the time and place of theincident. A “Y” entry in Field 74 reflects theReporting Entity’s report that these
conditions were present, and a blank entry in
Field 74 reflects the lack of any such report.
The entry for Field 75 reflects whether theReporting Entity reported that the sun was
obscured by clouds at the time and place of
the incident. A “Y” entry in Field 62 reflects
the Reporting Entity’s report that these
conditions were present, and a blank entry in
Field 75 reflects the lack of any such report.
The entry for Field 74 reflects whether theReporting Entity reported that there were
low visibility conditions, including fog orsmoke, at the time and place of the incident.
A “Y” entry in Field 74 reflects the Reporting
Entity’s report that these conditions were
present, and a blank entry in Field 74 reflects
the lack of any such report.
18

Field #77

Name
Weather – Rain

Type/Size
TEXT(1)

78

Weather - Severe WindTEXT(1)

79

Weather – Unknown

TEXT(1)80

Weather – OtherTEXT(1)

81

Weather – Other Text

TEXT(128)

82

Crash WithTEXT(80)

19

Description
The entry for Field 77 reflects whether theReporting Entity reported that it was raining
at the time and place of the incident. A “Y”
entry in Field 77 reflects the Reporting
Entity’s report that these conditions were
present, and a blank entry in Field 77 reflects
the lack of any such report.
The entry for Field 78 reflects whether theReporting Entity reported that there weresevere winds at the time and place of theincident. A “Y” entry in Field 78 reflects theReporting Entity’s report that these
conditions were present, and a blank entry in
Field 78 reflects the lack of any such report.
The entry for Field 79 reflects whether theReporting Entity reported that the weather
conditions at the time and place of theincident were unknown. A “Y” entry in Field
79 reflects the Reporting Entity’s report thatthe weather conditions were unknown, and ablank entry in Field 79 reflects the lack of any
such report.
The entry for Field 80 reflects whether theReporting Entity reported that weather
conditions “other” than those identified in
Fields 73-79 were present at the time andplace of the incident. A “Y” entry in Field 80
reflects the Reporting Entity’s report that“other” weather conditions were present,
and a blank entry in Field 80 reflects the lackof any such report.
The entry for Field 81 reflects the Reporting
Entity’s description of “other” weather
conditions in those reports where theReporting Entity reported, in Field 80, that“other” weather conditions were present at
the time and place of the incident. Field 81 isblank if the Reporting Entity did not indicate
in Field 80 that “other” weather conditions
were present.
The Reporting Entity’s categorical descriptionof any vehicle, non-motorist, animal, orobject with which the subject vehicle cameinto contact during the incident. Possible
values: Passenger Car, SUV, Van, Pickup
Truck, Motorcycle, Bus, Heavy Truck, First

Field #Name

Type/Size

83

Highest Injury Severity Alleged

TEXT(80)

84

Property Damage?

TEXT(80)20

Description
Responder Vehicle, Non-Motorist:
Pedestrian, Non-Motorist: Cyclist, NonMotorist: Other, Pole / Tree, Other Fixed
Object, Animal, “Other, see Narrative,”
Unknown.
The Reporting Entity’s report of the highest
confirmed or alleged crash injury severity
level resulting from the incident. Possible
values Fatality: Confirmed or alleged incident where
an involved party was fatally injured.
Serious: Confirmed or alleged incident where
an involved party sustained serious injuries
that required hospitalization or emergency
treatment.
Moderate: Confirmed or alleged incident
where an involved party sustained injuries
and sought medical treatment (excludes
hospitalization and emergency treatment).
Minor: Confirmed or alleged incident where
an involved party sustained possible injuries
that did not require medical treatment.
No Injuries Reported: No injuries werereported or alleged from the incident.
Unknown
The Reporting Entity’s report of whether theincident resulted in any property damage.
Possible values: Yes, No or Unknown.

Field #85

Name
CP Pre-Crash Movement

Type/Size
TEXT(80)21

Description
The Reporting Entity’s report of the precrash movement of any crash partner / othervehicle, or non-motorist (NM) prior to theincident. Field 83 will be blank if theReporting Entity does not report any crashpartner, other vehicle, or non-motorist.
Possible values Stopped: Vehicle was stopped and not
moving.
Proceeding Straight: Vehicle was moving
uniformly in one direction only.
Lane / Road Departure: Vehicle left theoriginal lane of travel.
Making Right Turn: Vehicle was turning right.
Making Left Turn: Vehicle was turning left.
Making U-Turn: Vehicle was making a UTurn.
Backing: Vehicle was backing in reverse.
Passing: Vehicle was passing another vehicle.
Changing Lanes: Vehicle was in the processof changing lanes within the same directionof travel.
Parking Maneuver: Vehicle was parking intoa space including forward, reverse, orparallel.
Entering Traffic: Vehicle was entering onto aroadway from a non-roadway – e.g., parking
lot, driveway.
Crossing into Opposing Lane: Vehicle
traveled into the opposing lane intentionallyto maneuver around a vehicle, object, orother obstruction.
Parked: Vehicle was parked at the time of
the incident.
Merging: Vehicle was merging onto aroadway from another roadway.
Traveling Wrong Way: Vehicle was travelingon the roadway in the wrong direction of theintended traffic flow.
NM Crossing Roadway: Non-motorist moving
across the roadway.
NM Waiting to Cross Roadway: Non-motorist
waiting to attempt to cross the roadway.
NM Moving Alongside Roadway: Nonmotorist walking or cycling along the side ofa roadway (not on a sidewalk) with or against
the flow of traffic.

Field #Name

Type/Size

Description
NM Moving on Sidewalk: Non-motorist
walking or cycling on a sidewalk alongside aroadway with or against the flow of traffic.
NM in Roadway - Other: Non-motorist
moving in the roadway with or against theflow of traffic.
Other, see Narrative
Unknown86

CP Any Air Bags Deployed?

TEXT(80)

87

CP Was Vehicle Towed?

TEXT(80)

The Reporting Entity’s report of whether any
air bag in the Crash Partner / Other vehicle
deployed during the incident. Possible
values: Yes, No, Not Applicable, Unknown.
Field 84 will be blank if the Reporting Entity
does not report any crash partner, othervehicle, or non-motorist.
The Reporting Entity’s report of whether the
Crash Partner / Other vehicle was towed
from the scene of the incident. Possible
values: Yes, No, Not Applicable, Unknown.
Field 87 will be blank if the Reporting Entity
does not report any crash partner, othervehicle, or non-motorist.

22

Field #88 - 98

Name
CP Contact Area

Type/Size

88

CP Contact Area - Rear Left

TEXT(1)89

CP Contact Area - Left

TEXT(1)90

CP Contact Area – Front Left

TEXT(1)

23

Description
The entries for Fields 88-98 reflect theReporting Entity’s report of the location of
any crash contact or damage resulting fromthe crash on the crash partner or othervehicle. A value of “Y” in any of these fields
reflects the Reporting Entity’s report of crashcontact or damage at the specified location.
Fields 88-98 will be blank if the Reporting
Entity does not report any crash partner,other vehicle, or non-motorist. One of moreof Fields 88-98 will be blank if the Reporting
Entity does not report any contact ordamage at the location described for thatfield.
The entry for Field 88 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 88 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashat the identified location. Field 86 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.
The entry for Field 89 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 89 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashat the identified location. Field 89 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.
The entry for Field 90 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 90 reflectsthat the Reporting Entity reported crashField #Name

Type/Size

91

CP Contact Area – Rear

TEXT(1)92

CP Contact Area – TopTEXT(1)93

CP Contact Area – Front

TEXT(1)24

Description
contact or damage resulting from the crashat the identified location. Field 88 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location t.
The entry for Field 91 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 91 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashat the identified location. Field 91 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.
The entry for Field 92 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 92 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashat the identified location. Field 92 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.
The entry for Field 93 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 93 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashat the identified location. Field 93 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.

Field #94

Name
CP Contact Area – Rear Right

Type/Size
TEXT(1)95

CP Contact Area – Right

TEXT(1)96

CP Contact Area – Front Right

TEXT(1)97

CP Contact Area – Bottom

TEXT(1)25

Description
The entry for Field 94 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 94 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashat the identified location. Field 94 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.
The entry for Field 95 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 95 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashat the identified location. Field 95 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.
The entry for Field 96 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 96 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashat the identified location. Field 96 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.
The entry for Field 97 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the crash partner orother vehicle. A “Y” entry in Field 97 reflectsthat the Reporting Entity reported crashcontact or damage resulting from the crashField #Name

Type/Size98

CP Contact Area – Unknown

TEXT(1)99

SV Pre-Crash Movement

TEXT(80)

26

Description
at the identified location. Field 97 will beblank if the Reporting Entity does not reportany crash partner, other vehicle, or nonmotorist or if the Reporting Entity does notreport any contact or damage at thedescribed location.
The entry for Field 98 indicates whether theReporting Entity reported that the location of
any crash contact or damage resulting fromthe crash on the crash partner or othervehicle was unknown. A “Y” entry in Field 98
reflects that the Reporting Entity reported
that the location of any crash contact ordamage resulting from the crash on the crashpartner or other vehicle was unknown. Field
98 will be blank if the Reporting Entity does
not report any crash partner, other vehicle,
or non-motorist or if the Reporting Entity
does not report that the location of any suchcontact or damage is unknown.
The Reporting Entity’s report of the precrash movement of the subject vehicle prior
to the incident. Possible values Stopped: Vehicle was stopped and not
moving.
Proceeding Straight: Vehicle was moving
uniformly in one direction only.
Lane / Road Departure: Vehicle left theoriginal lane of travel.
Making Right Turn: Vehicle was turning right.
Making Left Turn: Vehicle was turning left.
Making U-Turn: Vehicle was making a UTurn.
Backing: Vehicle was backing in reverse.
Passing: Vehicle was passing another vehicle.
Changing Lanes: Vehicle was in the processof changing lanes within the same directionof travel.
Parking Maneuver: Vehicle was parking intoa space including forward, reverse, orparallel.
Entering Traffic: Vehicle was entering onto aroadway from a non-roadway – e.g., parking
lot, driveway.
Crossing into Opposing Lane: Vehicle
traveled into the opposing lane intentionallyField #Name

Type/Size

Description
to maneuver around a vehicle, object, orother obstruction.
Parked: Vehicle was parked at the time of
the incident.
Merging: Vehicle was merging onto aroadway from another roadway.
Traveling Wrong Way: Vehicle was travelingon the roadway in the wrong direction of theintended traffic flow.
Other, see Narrative
Unknown

100

SV Any Air Bags Deployed?

TEXT(80)

101

SV Was Vehicle Towed?

TEXT(80)

102

SV Were All Passengers Belted?

TEXT(80)

103

SV Precrash Speed (MPH)

NUMBER(5)104

SV Pre-crash Speed – Unknown

TEXT(1)The Reporting Entity’s report of whether any
air bag in the subject vehicle deployed.
Possible values: Yes, No, Not Applicable,
Unknown.
The Reporting Entity’s report of whether the
subject vehicle was towed from the scene.
Possible values: Yes, No, Unknown.
The Reporting Entity’s report of whether all
passengers in the subject vehicle were
wearing seat belts at the time of theincident. Possible values: Yes, “No, see
Narrative,” No Passengers in Vehicle,
Unknown.
The Reporting Entity’s report of the speed of
the subject vehicle at the time of the incident
in miles per hour.
The entry for Field 104 reflects whether theReporting Entity reported that the pre-crash
speed of the subject vehicle was unknown. A“Y” entry in Field 104 reflects the Reporting
Entity’s report that this information was
unknown. A blank entry in Field 91 reflects
the lack of any report by the Reporting Entitythat the pre-crash speed of the subject
vehicle was unknown.

27

Field #Name
105 - 115 SV Contact Area

Type/Size105

SV Contact Area – Rear Left

TEXT(1)

106

SV Contact Area - Left

TEXT(1)

107

SV Contact Area – Front Left

TEXT(1)28

Description
The entries for Fields 105-115 reflect theReporting Entity’s report of the location of
any crash contact or damage resulting fromthe crash on the subject vehicle. A value of“Y” in any of these fields reflects theReporting Entity’s report of crash contact ordamage at the specified location. One ofmore of Fields 105-115 will be blank if theReporting Entity does not report any contact
or damage on the subject vehicle at thelocation described for that field.
The entry for Field 105 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 105 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 105 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.
The entry for Field 106 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 106 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 106 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.
The entry for Field 107 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 107 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 107 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.

Field #108

Name
SV Contact Area – Rear

Type/Size
TEXT(1)

109

SV Contact Area – TopTEXT(1)

110

SV Contact Area – Front

TEXT(1)

111

SV Contact Area – Rear Right

TEXT(1)29

Description
The entry for Field 108 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 108 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 108 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.
The entry for Field 109 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 109 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 109 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.
The entry for Field 110 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 110 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 110 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.
The entry for Field 111 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 111 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 111 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.

Field #112

Name
SV Contact Area – Right

Type/Size
TEXT(1)

113

SV Contact Area – Front Right

TEXT(1)

114

SV Contact Area - Bottom

TEXT(1)

115

SV Contact Area - Unknown

TEXT(1)30

Description
The entry for Field 112 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 112 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 112 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.
The entry for Field 113 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 113 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 113 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.
The entry for Field 114 indicates whether theReporting Entity reported any crash contact
or damage resulting from the crash at theidentified location on the subject vehicle. A“Y” entry in Field 114 reflects that theReporting Entity reported crash contact ordamage resulting from the crash at theidentified location. Field 114 will be blank if
the Reporting Entity does not report any
contact or damage on the subject vehicle atthe described location.
The entry for Field 115 indicates whether theReporting Entity reported that the location of
any crash contact or damage resulting fromthe crash on the subject vehicle was
unknown. A “Y” entry in Field 115 reflectsthat the Reporting Entity reported that thelocation of crash contact or damage resulting
from the crash was unknown. Field 115 willbe blank if the Reporting Entity does notreport that the location of any contact ordamage on the subject vehicle is unknown.

Field #Name
116 - 123 Data Availability

Type/Size

116

Data Availability - EDR

TEXT(1)

117

Data Availability - Police Rpt

TEXT(1)

118

Data Availability - Telematics

TEXT(1)

119

Data Availability – Complaints

TEXT(1)31

Description
The entries for Fields 116-123 reflect theReporting Entity’s report regarding thesources of available data or otherinformation regarding the incident. A “Y”
entry in any of Fields 103-110 reflects theReporting Entity’s report that the data
described in that field is available for the
subject vehicle. A blank entry in any of Fields
116-123 reflects that the Reporting Entity
has not reported that the data described inthat field is available.
The entry for Field 116 reflects the Reporting
Entity’s report regarding the availability of
EDR data from the subject vehicle. A “Y”
entry for Field 116 reflects the Reporting
Entity’s report that this data is available, anda blank entry for Field 116 reflects the lack ofany such report from the Reporting Entity.
The entry for Field 117 reflects the Reporting
Entity’s report regarding the availability of apolice report or other governmental reportor investigative record regarding theincident. A “Y” entry for Field 117 reflects
the Reporting Entity’s report that thisinformation is available, and a blank entry for
Field 117 reflects the lack of any such reportfrom the Reporting Entity.
The entry for Field 118 reflects the Reporting
Entity’s report regarding the availability ofdata or other information regarding theincident transmitted via telematics from thesubject vehicle. A “Y” entry for Field 118
reflects the Reporting Entity’s report that
this data is available, and a blank entry for
Field 118 reflects the lack of any such reportfrom the Reporting Entity.
The entry for Field 119 reflects the Reporting
Entity’s report regarding the availability of
consumer complaints regarding the incident.
A “Y” entry for Field 119 reflects theReporting Entity’s report that this data isavailable, and a blank entry for Field 119
reflects the lack of any such report from theReporting Entity.

Field #120

Name
Data Availability - Video

Type/Size
TEXT(1)

121

Data Availability – OtherTEXT(1)

122

Data Availability - No Data

TEXT(1)

123

Data Availability - Unknown

TEXT(1)124

Law Enforcement Investigating?

TEXT(80)

125

Investigating Agency

TEXT(128)

32

Description
The entry for Field 120 reflects the Reporting
Entity’s report regarding the availability ofvideo information (from the subject vehicle
or otherwise) relating to the incident. A “Y”
entry for Field 120 reflects the Reporting
Entity’s report that this data is available, anda blank entry for Field 120 reflects the lack ofany such report from the Reporting Entity.
The entry for Field 121 reflects the Reporting
Entity’s report regarding the availability of
information relating to the incident otherthan that specified in Fields 114-118. A “Y”
entry for Field 121 reflects the Reporting
Entity’s report that “other” data is available,
and the nature of this information should be
described in Field 134 (Narrative). A blankentry for Field 121 reflects the lack of any
such report from the Reporting Entity.
The entry for Field 122 reflects the Reporting
Entity’s report regarding the lack of any
available additional data regarding theincident. A “Y” entry for Field 122 reflects
the Reporting Entity’s report that there is nosuch available data, and a blank entry for
Field 122 reflects the lack of any such reportfrom the Reporting Entity.
The entry for Field 123 reflects the Reporting
Entity’s report regarding the availability ofadditional data or information regarding theincident. A “Y” in Field 123 reflects theReporting Entity’s report that the availabilityof any such additional data or information
was unknown, and a blank entry in Field 123
reflects the lack of any such report by theReporting Entity.
The Reporting Entity’s report on whether alaw enforcement agency is investigating theincident. Possible values: Yes, No, Unknown.
The Reporting Entity’s report on the name ofany law enforcement agency investigating
the incident. The entry for Field 125 will beblank if the Reporting Entity has entered a“No” or “Unknown” response to Field 124(Law Enforcement Investigating?). If theentry states “[MAY CONTAIN PERSONALLY
IDENTIFIABLE INFORMATION],” theField #Name

Type/Size

126

Investigating Agency - Unknown

TEXT(1)127

Rep Ent Or Mfr Investigating?

TEXT(80)

128

Investigating Officer NameTEXT(60)

129

Inv. Officer Name - Unknown

TEXT(1)130

Investigating Officer Phone

TEXT(20)

33

Description
information reported by the Reporting Entity
has been redacted by NHTSA because NHTSA
has concluded that it may constitute (or leadto the disclosure of) personally identifiable
information (PII) that is protected fromdisclosure.
The Reporting Entity’s report on whether thename of the law enforcement agency
investigating the incident is unknown. A “Y”
entry in Field 126 reflects the Reporting
Entity’s report that this information was
unknown, and a blank entry in Field 126
reflects the lack of any such report by theReporting Entity.
The Reporting Entity’s report on whether theReporting Entity or the manufacturer of thesubject vehicle is conducting an investigationof the incident. Possible values: Yes, No,
Unknown.
The Reporting Entity’s report of the name ofthe primary point of contact for any law
enforcement investigation. If the entry states“[MAY CONTAIN PERSONALLY IDENTIFIABLE
INFORMATION],” the information reportedby the Reporting Entity has been redacted by
NHTSA because NHTSA has concluded that it
may constitute (or lead to the disclosure of)
personally identifiable information (PII) thatis protected from disclosure.
The Reporting Entity’s report on whether thename of the primary point of contact for any
law enforcement investigation is unknown.
A “Y” in Field 129 reflects the Reporting
Entity’s report that this information was
unknown, and a blank entry in Field 129
reflects the lack of any such report by theReporting Entity.
The Reporting Entity’s report of thetelephone number for the primary point ofcontact for any law enforcement
investigation. If the entry states “[MAYCONTAIN PERSONALLY IDENTIFIABLE
INFORMATION],” the information reportedby the Reporting Entity has been redacted by
NHTSA because NHTSA has concluded that it
may constitute (or lead to the disclosure of)Field #Name

Type/Size

Description
personally identifiable information (PII) thatis protected from disclosure.

131

Inv. Officer Phone – Unknown

TEXT(1)

132

Investigating Officer EmailTEXT(50)

133

Inv. Officer Email – Unknown

TEXT(1)

134

Within ODD?

TEXT(80)

The Reporting Entity’s report on whether the
telephone number of the primary point ofcontact for any law enforcement
investigation is unknown. A “Y” in Field 131
reflects the Reporting Entity’s report that
this information was unknown, and a blankentry in Field 131 reflects the lack of any
such report by the Reporting Entity.
The Reporting Entity’s report of the email
address of the primary point of contact for
any law enforcement investigation. If theentry states “[MAY CONTAIN PERSONALLY
IDENTIFIABLE INFORMATION],” theinformation reported by the Reporting Entity
has been redacted by NHTSA because NHTSA
has concluded that it may constitute (or leadto the disclosure of) personally identifiable
information (PII) that is protected fromdisclosure.
The Reporting Entity’s report on whether theemail address of the primary point of contact
for any law enforcement investigation is
unknown. A “Y” in Field 133 reflects theReporting Entity’s report that thisinformation was unknown, and a blank entry
in Field 133 reflects the lack of any suchreport by the Reporting Entity.
The Reporting Entity’s report on whether the
subject vehicle was acting within its ODD
during the period 30 seconds prior to thecrash through the conclusion of the crash.
Possible values: Yes, “No, see Narrative”,“Unknown, see Narrative”. If the entry states“[REDACTED, MAY CONTAIN CONFIDENTIAL
BUSINESS INFORMATION],” this indicatesthat the Reporting Entity has made andsubmitted a claim that this information is
confidential business information that is
protected from public disclosure.

34

Field #135

NameWithin ODD? – CBI

Type/Size
TEXT(1)

136

Narrative

TEXT(4000)

137

Narrative - CBI?

TEXT(1)35

Description
The entry for Field 135 reflects whether theReporting Entity made a claim that the
information it submitted in response to Field
134 (Within ODD?) constitutes confidential
business information that is protected fromdisclosure. A “Y” in Field 135 indicates that
the Reporting Entity claimed that the
information it submitted in response to Field
134 constitutes confidential businessinformation. A blank entry in Field 135
indicates that the Reporting Entity made nosuch claim.
The Reporting Entity’s written narrative of
the pre-crash, crash, and post-crash details,
and other information. If the entry states“[REDACTED, MAY CONTAIN CONFIDENTIAL
BUSINESS INFORMATION],” this indicatesthat the Reporting Entity has made andsubmitted a claim that some or all of thisinformation is confidential businessinformation that is protected from public
disclosure. If the Reporting Entity has madesuch a claim, only those portions of thenarrative for which a claim has been madeare redacted. Markings of “[XXX]” indicatessome of the information reported by theReporting Entity has been redacted by
NHTSA because NHTSA has concluded that it
may constitute (or lead to the disclosure of)
personally identifiable information (PII) thatis protected from disclosure, pursuant to theFreedom of Information Act (FOIA), 5 U.S.C.
552(B)(6).
The entry for Field 137 reflects whether theReporting Entity made a claim that some or
all of the information it submitted in
response to Field 136 (Narrative) constitutes
confidential business information that is
protected from disclosure. A “Y” in Field 137
indicates that the Reporting Entity claimed
that some or all of the information it
submitted in response to Field 136
constitutes confidential businessinformation. A blank entry in Field 137
indicates that the Reporting Entity made nosuch claim.

36