Motor Vehicle Collisions - Person

f55k-p6yuPublic Safety21 columns

NOTE: This dataset is temporarily not updating while its automated update process is being fixed. This fix is expected to be completed during the month of August. The Motor Vehicle Collisions person table contains details for people involved in the crash. Each row represents a person (driver, occupant, pedestrian, bicyclist,..) involved in a crash. The data in this table goes back to April 2016 when crash reporting switched to an electronic system. The Motor Vehicle Collisions data tables contain information from all police reported motor vehicle collisions in NYC. The police report (MV104-AN) is required to be filled out for collisions where someone is injured or killed, or where there is at least $1000 worth of damage (https://www.nhtsa.gov/sites/nhtsa.dot.gov/files/documents/ny_overlay_mv-104an_rev05_2004.pdf). It should be noted that the data is preliminary and subject to change when the MV-104AN forms are amended based on revised crash details. Due to success of the CompStat program, NYPD began to ask how to apply the CompStat principles to other problems. Other than homicides, the fatal incidents with which police have the most contact with the public are fatal traffic collisions. Therefore in April 1998, the Department implemented TrafficStat, which uses the CompStat model to work towards improving traffic safety. Police officers complete form MV-104AN for all vehicle collisions. The MV-104AN is a New York State form that has all of the details of a traffic collision. Before implementing Trafficstat, there was no uniform traffic safety data collection procedure for all of the NYPD precincts. Therefore, the Police Department implemented the Traffic Accident Management System (TAMS) in July 1999 in order to collect traffic data in a uniform method across the City. TAMS required the precincts manually enter a few selected MV-104AN fields to collect very basic intersection traffic crash statistics which included the number of accidents, injuries and fatalities. As the years progressed, there grew a need for additional traffic data so that more detailed analyses could be conducted. The Citywide traffic safety initiative, Vision Zero started in the year 2014. Vision Zero further emphasized the need for the collection of more traffic data in order to work towards the Vision Zero goal, which is to eliminate traffic fatalities. Therefore, the Department in March 2016 replaced the TAMS with the new Finest Online Records Management System (FORMS). FORMS enables the police officers to electronically, using a Department cellphone or computer, enter all of the MV-104AN data fields and stores all of the MV-104AN data fields in the Department’s crime data warehouse. Since all of the MV-104AN data fields are now stored for each traffic collision, detailed traffic safety analyses can be conducted as applicable.

View on NYC Open Data

Quality

B86.0 / 100

From a 500-row sample across 21 columns.

completeness66/ 25% weight

consistency88/ 20% weight

accuracy95/ 20% weight

timeliness94/ 15% weight

usability95/ 20% weight

Related datasets

Motor Vehicle Collisions - Vehicles0.74

Sample rows

unique_id	collision_id	crash_date	crash_time	person_id	person_type	person_injury	vehicle_id	ped_role	person_sex	person_age	ejection
10249006	4229554	2019-10-26T00:00:00.000	9:43	31aa2bc0-f545-444f-8cdb-f1cb5cf00b89	Occupant	Unspecified	19141108	Registrant	U	—	—
10255054

Columns

21 queryable · 21 profiled

The machine field names SoQL needs, with the publisher's own description of each.

Field	Type	Description	Null	Values
`unique_id`	integer	Unique record code generated by system. Primary Key for Person table.	0%	`111843931027560611761946`
`collision_id`	integer	Crash identification code. Foreign Key, matches unique_id from the Crash table.	0%	`396377546911583591272`
`crash_date`	datetime	Occurrence date of collision	0%	`2018-11-15T00:00:00.0002017-05-19T00:00:00.0002017-12-15T00:00:00.000`
`crash_time`	text	Occurrence time of collision	0%	`0:00`

Query this from your own app

GET /api/datasets/f55k-p6yu
GET /api/datasets/f55k-p6yu/quality
GET /api/datasets/f55k-p6yu/related
GET /api/columns?dataset=f55k-p6yu