﻿<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <title>accidents FARS v. 1</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>1200 New Jersey Ave. SE, Washington, DC, 20590</pubplace>
          <publish>Office of the Assistant Secretary for Research and Technology/Bureau of Transportation Statistics</publish>
        </pubinfo>
      </citeinfo>
    </citation>
    <descript>
      <abstract>Accident - (1975-current): This data file contains information about crash characteristics and environmental conditions at the time of the crash. There is one record per crash. FARS data are made available to the public in Statistical Analysis System (SAS) data files as well as Database Files (DBF). Over the years changes have been made to the type of data collected and the way the data are presented in the SAS data files. Some data elements have been dropped and new ones added, coding of individual data elements has changed, and new SAS data files have been created. Coding changes and the years for which individual data items are available are shown in the “Data Element Definitions and Codes” section of this document. The FARS Coding and Editing Manual contains a detailed description of each SAS data elements including coding instructions and attribute definitions. The Coding Manual is published for each year of data collection. Years 2001 to current are available at: http://www-nrd.nhtsa.dot.gov/Cats/listpublications.aspx?Id=J&amp;ShowBy=DocType Note: In this manual the word vehicle means in-transport motor vehicle unless otherwise noted.</abstract>
      <purpose>One of the primary objectives of the National Highway Traffic Safety Administration (NHTSA) is to reduce the staggering human toll and property damage that motor vehicle traffic crashes impose on our society.

FARS is a census of fatal motor vehicle crashes with a set of data files documenting all qualifying fatalities that occurred within the 50 States, the District of Columbia, and Puerto Rico since 1975. To qualify as a FARS case, the crash had to involve a motor vehicle traveling on a trafficway customarily open to the public, and must have resulted in the death of a motorist or a non-motorist within 30 days of the crash.</purpose>
    </descript>
    <spdom />
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Categories</themekt>
        <themekey>location</themekey>
        <themekey>transportation</themekey>
      </theme>
      <temporal>
        <tempkt>None</tempkt>
        <tempkey>2014</tempkey>
      </temporal>
    </keywords>
    <accconst>None</accconst>
    <useconst>None</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Office of the Assistant Secretary for Research and Technology/Bureau of Transportation Statistics</cntorg>
          <cntper>National Transportation Atlas Database (NTAD) 2014</cntper>
        </cntorgp>
        <cntpos>Geospatial Information Systems</cntpos>
        <cntaddr>
          <addrtype>unknown</addrtype>
          <address>1200 New Jersey Ave. SE</address>
          <city>Washington</city>
          <state>DC</state>
          <postal>20590</postal>
        </cntaddr>
        <cntvoice>202-366-DATA</cntvoice>
        <cntemail>answers@BTS.gov</cntemail>
      </cntinfo>
    </ptcontac>
    <native>Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.0.3035</native>
  </idinfo>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Entity point</sdtstype>
        <ptvctcnt>30800</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <geograph>
        <latres>8.983152841195215e-009</latres>
        <longres>8.983152841195215e-009</longres>
        <geogunit>Decimal Degrees</geogunit>
      </geograph>
      <geodetic>
        <horizdn>D WGS 1984</horizdn>
        <ellips>WGS 1984</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257223563</denflat>
      </geodetic>
    </horizsys>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>accidents FARS</enttypl>
      </enttyp>
      <attr>
        <attrlabl>FID</attrlabl>
        <attrdef>Internal feature number.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Sequential unique whole numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>shape</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>STATE</attrlabl>
        <attrdef>State FIPS code.

See FARS metada document for more information.</attrdef>
        <attrdefs>NIST</attrdefs>
      </attr>
      <attr>
        <attrlabl>ST_CASE</attrlabl>
        <attrdef>Two Characters for State Code followed by Four Characters for Case Number. 

This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together.

See FARS metada document for more information.

</attrdef>
        <attrdefs>NTSHA</attrdefs>
      </attr>
      <attr>
        <attrlabl>VE_TOTAL</attrlabl>
        <attrdef>This data element counts the number of contact motor vehicles that the officer reported on the PAR as a unit involved in the crash.

This counts all of the vehicles in the crash. This includes the vehicles in-transport which are in the Vehicle data file and the vehicles not in-transport which are in the Parkwork data file (previously Vehnit). This data element only appears in the Accident data file. Note: The Parkwork data file replaced the Vehnit data file in 2010. The Vehnit data file does not exist prior to 2005.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>VE_FORMS</attrlabl>
        <attrdef>This data element counts the number of vehicles in-transport involved in the crash. Legally parked vehicles are not included.

This data element is the count of all vehicles in the Vehicle data file and is the count where “Unit Type” = 1.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>PVH_INVL</attrlabl>
        <attrdef>This data element counts the number of parked and working vehicles involved in the crash.

This data element is the count of all vehicles in the Parkwork data file and is the count where “Unit Type” is in (2, 3 or 4).

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>PEDS</attrlabl>
        <attrdef>This data element counts the number of Person Level (Motor Vehicle Occupant) Forms that are applicable to this case (i.e., occupants).

This represents the number of forms created for persons in motor vehicles. It is the count of all persons where “Person Type” is in (1, 2, 3 or 9).

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>PERNOTMVIT</attrlabl>
        <attrdef>Number of Persons Not in Motor Vehicles in Transport (MVIT).

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>PERMVIT</attrlabl>
        <attrdef>This data element counts the number of motorists in the crash. A motorist is a driver, passenger or unknown occupant type of a motor vehicle in-transport.

This data element is derived from the Person data file and is the count of all persons where “Person Type” is in (1, 2 or 9). Note: Persons where “Person Type” = 3 (Occupant of a Motor Vehicle Not In-Transport) are not included in this data element but are counted in C5 above.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>PERSONS</attrlabl>
        <attrdef>This data element counts the number of Person Level (Motor Vehicle Occupant) Forms that are applicable to this case (i.e., occupants).

This represents the number of forms created for persons in motor vehicles. It is the count of all persons where “Person Type” is in (1, 2, 3 or 9).

See FARS metada document for more information.
</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>COUNTY</attrlabl>
        <attrdef>This data element records the location of the unstabilized event with regard to the County. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).

GSA geographical codes are somewhat stable. Occasionally one code will be divided into two codes.

See FARS metada document for more information.

</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>CITY</attrlabl>
        <attrdef>This data element records the location of the unstabilized event with regard to the City. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC).

GSA geographical codes are somewhat stable. Occasionally one code will be divided into two codes.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>DAY</attrlabl>
        <attrdef>This data element records the day of the month on which the crash occurred.

This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PDAY.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>MONTH</attrlabl>
        <attrdef>This data element records the month in which the crash occurred.

This data element also appears in the Vehicle and Person data files and in the Parkwork data file as PMONTH.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>YEAR</attrlabl>
        <attrdef>This data element records the year in which the crash occurred.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>DAY_WEEK</attrlabl>
        <attrdef>This data element records the day of the week on which the crash occurred.

This data element has been calculated based on the year, month, and day.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>HOUR</attrlabl>
        <attrdef>This data element records the hour at which the crash occurred.

All time is 24-hour military time.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>MINUTE</attrlabl>
        <attrdef>This data element records the minutes after the hour at which the crash occurred.

All time is 24-hour military time.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>NHS</attrlabl>
        <attrdef>This data element identifies whether this crash occurred on a trafficway that is part of the National Highway System.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>ROAD_FNC</attrlabl>
        <attrdef>This data element identifies the functional classification of the trafficway on which the crash occurred.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>ROUTE</attrlabl>
        <attrdef>This data element identifies the route signing of the trafficway on which the crash occurred.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>TWAY_ID</attrlabl>
        <attrdef>This data element records the trafficway on which the crash occurred.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>TWAY_ID2</attrlabl>
        <attrdef>This data element records the trafficway on which the crash occurred.

Beginning in 2004, a second trafficway identifier was added to accommodate intersection and intersection-related crashes where the officer provides the identifier for the second trafficway.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>MILEPT</attrlabl>
        <attrdef>This data element records the milepoint nearest to the location where the crash occurred.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>LATITUDE</attrlabl>
        <attrdef>Accitdent longitude as a single value, in decimal degrees.</attrdef>
      </attr>
      <attr>
        <attrlabl>DRUNK_DR</attrlabl>
        <attrdef>This data element records the number of drunk drivers involved in the fatal crash and is derived from data elements in the Vehicle and Person data files.

Data from the Vehicle and Person data files are analyzed and if there is sufficient information to conclude that a driver was drunk, i.e., if the blood alcohol concentration (BAC) is positive, or if the police reported alcohol involvement, then the driver is counted as a drunk driver. A driver being charged with an alcohol violation by itself does not have the driver counted as a drunk driver. Note that alcohol data is often missing. For that reason this data element may undercount the actual number of drunk drivers. For detailed analysis of alcohol involvement, the alcohol data files should be used.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>LATITUDE</attrlabl>
        <attrdef>Accident latitude as a single value, in decimal degrees.</attrdef>
      </attr>
      <attr>
        <attrlabl>SP_JUR</attrlabl>
        <attrdef>This data element identifies if the location on the trafficway where the crash occurred qualifies as a Special Jurisdiction even though it may be patrolled by state, county or local police (e.g., all State highways running through Indian reservations are under the jurisdiction of the Indian reservation).

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>HARM_EV</attrlabl>
        <attrdef>This data element describes the first injury or damage producing event of the crash.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>MAN_COLL</attrlabl>
        <attrdef>This data element describes the orientation of two motor vehicles in-transport when they are involved in the “First Harmful Event” of a collision crash. If the “First Harmful Event” is not a collision between two motor vehicles in-transport it is classified as such.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>RELJCT1</attrlabl>
        <attrdef>This data element identifies the crash's location with respect to presence in an interchange area. The coding of this data element is done in two sub-fields (see also C20B) and is based on the location of the “First Harmful Event” of the crash.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>RELJCT2</attrlabl>
        <attrdef>This data element identifies the crash's location with respect to presence in or proximity to components typically in junction or interchange areas. The coding of this data element is done in two sub-fields (see also C20A) and is based on the location of the “First Harmful Event” of the crash.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>TYP_INT</attrlabl>
        <attrdef>This data element identifies and allows separation of various intersection types.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>WRK_ZONE</attrlabl>
        <attrdef>This data element identifies a motor vehicle traffic crash in which the first harmful event occurs within the boundaries of a work zone or on an approach to or exit from a work zone, resulting from an activity, behavior, or control related to the movement of the traffic units through the work zone.

This data element identifies a “Work Zone Accident” as defined in ANSI D16.1, 7th Edition. If the crash qualifies as a "Work Zone Accident" then the type of work activity is identified. Use of the codes does not imply that the crash was caused by the construction, maintenance, or work activity.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>REL_ROAD</attrlabl>
        <attrdef>This data element identifies the location of the crash as it relates to its position within or outside the trafficway based on the “First Harmful Event”.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>LGT_COND</attrlabl>
        <attrdef>This data element records the type/level of light that existed at the time of the crash as indicated in the case material.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>WEATHER1</attrlabl>
        <attrdef>This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.

This data element identifies up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 are coded data elements, and Accident.WEATHER is derived from these two.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>WEATHER2</attrlabl>
        <attrdef>This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.

this data element identifies up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 are coded data elements, and Accident.WEATHER is derived from these two.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>WEATHER</attrlabl>
        <attrdef>This data element records the prevailing atmospheric conditions that existed at the time of the crash as indicated in the case material.

This data element identifies up to two values. If more than two atmospheric conditions were reported, the two conditions that most affect visibility were selected. Accident.WEATHER1 and Accident.WEATHER2 are coded data elements, and Accident.WEATHER is derived from these two.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>SCH_BUS</attrlabl>
        <attrdef>This data element identifies if a school bus, or motor vehicle functioning as a school bus, is related to the crash.

A school bus crash is (1) a motor vehicle crash in which a school bus, with or without a pupil on board, is involved directly as a contact vehicle, or (2) a motor vehicle crash or an other-road-vehicle crash in which a school bus, with or without a pupil or board, is involved indirectly as a non-contact vehicle.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>RAIL</attrlabl>
        <attrdef>This data element identifies if the crash occurred in or near a rail grade crossing.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>NOT_HOUR</attrlabl>
        <attrdef>This data element records the hour that emergency medical service was notified.

All time is 24-hour military time. SAS Name.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>NOT_MIN</attrlabl>
        <attrdef>This data element records the minutes after the hour that emergency medical service was notified.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>ARR_HOUR</attrlabl>
        <attrdef>This data element records the hour that emergency medical service arrived on the crash scene.

All time is 24-hour military time.

See FARS metada document for more information.

</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>ARR_MIN</attrlabl>
        <attrdef>This data element records the minutes after the hour that emergency medical service arrived on the crash scene.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>HOSP_HR</attrlabl>
        <attrdef>This data element records the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.

All time is 24-hour military time.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>HOSP_MN</attrlabl>
        <attrdef>This data element records the minutes after the hour that emergency medical service arrived at the treatment facility to which it was transporting victims of the crash.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>CF1</attrlabl>
        <attrdef>This data element records factors related to the crash expressed by the investigating officer.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>CF2</attrlabl>
        <attrdef>This data element records factors related to the crash expressed by the investigating officer.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>CF3</attrlabl>
        <attrdef>This data element records factors related to the crash expressed by the investigating officer.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
      <attr>
        <attrlabl>FATALS</attrlabl>
        <attrdef>This data element records the number of fatally injured persons in the crash and is derived by counting all persons with “Injury Severity” of 4 in the crash.

See FARS metada document for more information.</attrdef>
        <attrdefs>NHTSA</attrdefs>
      </attr>
    </detailed>
  </eainfo>
  <metainfo>
    <metd>20140410</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Office of the Assistant Secretary for Research and Technology/Bureau of Transportation Statistics</cntorg>
          <cntper>National Transportation Atlas Database (NTAD) 2014</cntper>
        </cntorgp>
        <cntpos>Geospatial Information Systems</cntpos>
        <cntaddr>
          <addrtype>unknown</addrtype>
          <address>1200 New Jersey Ave. SE</address>
          <city>Washington</city>
          <state>DC</state>
          <postal>20590</postal>
        </cntaddr>
        <cntvoice>202-366-DATA</cntvoice>
        <cntemail>answers@BTS.gov</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>