MMUCC no longer defines how data elements should be collected (at scene/linked or derived). States are encouraged to link or derive wherever possible to minimize the impact on law enforcement.

Following State best practices, MMUCC now includes Fatal, Large Vehicles and Hazardous Materials, and Non-Motorist crash data sections; these are only completed if applicable. The Model Minimum changes based on the circumstances instead of a one-size-fits-all approach.

A new type of data element—contained in the Dynamic Data Elements section—is introduced for the first time to capture data on topics that are changing rapidly. Dynamic data elements may change more frequently than each edition (every 5 years).

Data elements are no longer defined by source (collected at the scene, derived from other data sources or linked to other databases). States are encouraged to link or derive data elements where possible to diminish the impact on law enforcement officers.

Data elements that were previously indicated as linked or derived are now shown in both the table of contents and by the data element name with the link symbol. [[{"fid":"36906","view_mode":"default","fields":{"format":"default","alignment":"","field_file_image_alt_text[und][0][value]":"Image of link"},"type":"media","field_deltas":{"1":{"format":"default","alignment":"","field_file_image_alt_text[und][0][value]":"Image of link"}},"attributes":{"alt":"Image of link","class":"media-element file-default","data-delta":"1"}}]]

The “model minimum” is no longer one-size-fits-all. Most elements reside in the main section of MMUCC and are considered minimum for all crash types. Elements that describe crashes involving fatalities, large vehicles and hazardous materials, and non-motorists are separated into three, new sections. States need only consider these sets of elements “minimum” if applicable to the crash.

This change followed the best practice of many States that already modify their data intake based upon crash type and severity. For other States, data managers should consider crash database protocols that accommodate this process.

Lastly, a new dynamic data elements section was created to house elements that may change more frequently than every five years, due to rapidly evolving technology (e.g. automated vehicle system(s)). 

The guidelines have been reformatted to eliminate multiple “subfields” to collect multiple selections from the same list of attributes. MMUCC 5th Edition denotes the number of selections by stating a single number or a range, where appropriate.

Subfields are used to capture distinct pieces of a single data element. For example, the new “Distracted By” element breaks distraction into two parts – action and source.

Attribute lists have been reordered into alphabetical order to diminish selection bias except for some elements where a specific order makes sense (e.g., keeping construction zone sections in vehicle-travel order).

Following the best practice of States and the FARS database, all defined attributes include an attribute code (or number value).

At the request of many States, “model minimum” edit checks were added to most data elements to provide guidance on the types of checks any crash data system should include minimally. For States that wish to have more extensive edit checks, consult the FARS user’s manual, found in the NHTSA CrashStats library.

Technical assistance is available to States through the NHTSA Crash Data Improvement Program (CDIP) and Traffic Records GO Teams. CDIP and GO Team technical assistance can be requested by submitting an application to your State’s NHTSA Regional Office. The Training and Technical Assistance application can be found here.

A State can request a MMUCC Mapping at any time by submitting an application to their NHTSA Regional Office. If your State is considering an update to its crash report or statewide crash database, MMUCC Mapping results provide decision-makers with State-to-MMUCC compatibility and the information they need to prioritize changes. The Training and Technical Assistance application can be found here.

The Mapping to MMUCC 5th Edition section of the MMUCC 5th Edition Guideline provides detailed information on the MMUCC Mapping rules and process.

There is a MMUCC Crash Report Form that can be found in Appendix C in the MMUCC 5th Edition Guideline or by clicking here for a full-size version. 

States are also welcome to request the editable version of the MMUCC Crash Report Form to modify and use as needed by sending an email to the Traffic Records Team.

A summary of changes can be found in Appendix B of the MMUCC 5th Edition Guideline (2017).

MMUCC is a voluntary guideline that represents a minimum, model set of variables (data elements) that describe a motor vehicle crash. Data elements were incorporated into MMUCC if they were deemed necessary (needed for decision-making purposes) and comprehensive (included all aspects of the issue or problem being described).

While the MMUCC guideline is a voluntary standard designed for States to use at their discretion, specific parts of the standard have been incorporated into several regulatory requirements. States are currently required to adopt the model distracted driving data element in order to qualify for §405(e) distracted driving incentive grants. In addition, States will also be required to adopt the “serious injury (a)” attribute of the injury severity element by April 15, 2019, per FHWA’s Safety Performance Management Measures Final Rule (23 CFR 490) and NHTSA’s Uniform Procedures for State Highway Safety Grants Program Interim Final Rule (23 CFR 1300).

MMUCC is a collaborative effort between NHTSA and GHSA, States, data collectors, data managers, data users and safety stakeholders. Prior to each publication, an expert panel convenes to review all proposed changes to determine what will be included. Every change is considered - both for its merits and how it will impact the existing elements. The panel's primary focus is to strike a balance between the data we'd like to have, what law enforcement can reasonably collect, and what data managers can link or derive. 

Proposed changes can be submitted to the Traffic Records Team and should include the following information: 1) reason for change, 2) specific change requested (draft of new or changed element/attribute), and 3) any updated or new edit checks.