The Best Practice Guide to Understanding Near-Miss Conflict Analytics

Road fatalities and severe accidents continue to inflict a high cost on vulnerable road users and communities.

With more vehicles sharing roadways with bicycles, pedestrians, e-scooters, and other alternative modes of transportation, an aging population, and the advent of connected and autonomous vehicles, the risk of vehicle-to-vehicle and vehicle-to-vulnerable road user crashes continues to be a challenge for transportation planning, engineering, and operations professionals.


Many agencies still depend exclusively on historical crash and injury data to identify safety risks at intersections and other higher-risk sites on their roadways. There is a growing body of research and real-world implementations of new technologies to suggest that crash data alone is insufficient to make safety decisions and safety countermeasure investments.


The lagging crash data, errors and incomplete data in crash reports, as well as small samples of reported vulnerable road user accidents, all combine to offer an incomplete picture of the path forward for near-miss conflict analytics.


This whitepaper, authored by industry-recognized leaders in road safety engineering, is designed to provide transportation professionals with a better understanding and recommended set of best practices for evaluating and selecting near-miss conflict analytics, including identifying those measurements, methodologies, and capabilities that are critical to accurately predicting and mitigating severe crashes through actionable insights and countermeasures.

What are ‘Near-Misses’ and Conflicts?

Well-known limitations with the quality and timeliness of crash data and crash-based safety analysis methods are giving rise to the use of alternative measures of safety referred to as conflicts, or ‘near-misses’. Conflicts describe events involving road users that demonstrate a high correlation with vehicle-vehicle and vehicle-vulnerable road user crashes.

Presently, ‘near-miss’ events are being measured using a wide range of definitions. For example, depending on the provider, ‘near-miss’ is a term applied to measurements of a hard deceleration or acceleration, sudden lateral movement, or, simply the presence of a pedestrian and vehicle in the crosswalk area at the same time.

However, the only useful definition of a conflict is one that has a statistically proven relationship with observed crashes. Without such a proven relationship, these definitions of ‘near-miss’ may be merely correlated with levels of traffic, and are of no use in assessing road safety.

It is also important to recognize that conflicts include both remarkable and unremarkable events. A distinguishing feature of remarkable conflicts: evasive actions.


Examples of Evasive Actions:

  1. A pedestrian abruptly stopping or changing direction to avoid a crash
  2. A vehicle braking heavily or swerving to avoid a crash.

While not an essential characteristic of a conflict, the presence of an evasive action is much more remarkable and reminiscent of crashes than conflicts that do not involve evasive actions.


Note: The relationship between conflicts and crashes does not depend on the presence of evasive actions.

Why Do Conflict Analytics and Near-Misses Matter?

Conflict analytics and data are critical to transportation planning, operations, and engineering because they offer a number of important advantages over historical crash data for road safety programs:


  1. Conflicts occur much more frequently than crashes, and therefore, generate more robust datasets and insights that are critical for reliability.
  2. Conflict data avoids the ethical dilemma of the need to first observe crashes in order to prevent them.
  3. Conflict data provides instantaneous insights that can be used for real-time safety evaluation, countermeasure implementation, and traffic operation optimization, as opposed to lagging crash data.
  4. Crash data does not provide insights into road user behavior, but conflict data can pool multiple data points to identify correlating factors for crash prediction.
  5. Accident reports often include incorrect data, such as misidentifying hazardous road segments and blindspots while conflict data is using the same ground truth data.

AMAG aims to become the world’s leading provider of predictive transport analytics, addressing current and future planning, management, and operations challenges faced by Departments of Transport (DOTs) and Governments around the world. 

A transportation analytics company with pioneering artificial intelligence technology that improves transport safety and network operations by providing data-driven insights that saves lives, prevents crashes, reduces congestion and supports vital planning and transport network operations by providing data-driven insights that are not available from competing products.

Five Conflict Indicators In Near-miss Analysis

Research has shown that understanding crash risk through conflict data analysis requires the measurement of at least five unique indicators that have a proven ability to predict future crashes and crash severity. These include:

  1. Time-To-Collision
  2. Modified Time-To-Collision
  3. Post Encroachment Time
  4. Deceleration Rate to Avoid a Crash
  5. Delta-V, a measure of severity

These measures have a proven ability to predict future crashes. As an example of this evidence, an evaluation of implementing Leading Pedestrian Intervals at signalized intersections in Bellevue, WA showed consistent results in the observed reduction in conflicts between pedestrians and vehicles as do reductions in vehicle-pedestrian crashes from crash-based studies.

Further evidence of the link between conflicts and crashes can be found in several published  :

      1. 2020: A bivariate Bayesian hierarchical extreme value model for traffic conflict-based crash estimation. L Zheng, T Sayed. Analytic Methods in Accident Research 25, 100111.
      2. 2019: Bayesian hierarchical modeling of traffic conflict extremes for crash estimation: A non-stationary peak over threshold approach. L Zheng, T Sayed. Analytic Methods in Accident Research 24, 100-106.
      3. 2019: Bayesian hierarchical modeling of the non-stationary traffic conflict extremes for crash estimation. L Zheng, T Sayed, M Essa. Analytic methods in accident research 23, 100100.
      4. 2016: Conflict-Based Safety Performance Functions for Predicting Traffic Collisions by Type. E. Sachhi, T. Sayed. Transportation Research Record 2583.

Ensuring Accuracy of ‘Near-Miss’ Data

The foundation of using conflicts to predict crash risk is built on the accuracy of the process to extract conflicts from sensor data. Research has shown that only extreme conflicts are the best predictors of crash risk and the identification of true extremes is highly sensitive to the quality of the conflict extraction process.


The accuracy of conflict extraction and their use to assess crash risk is highly sensitive to several factors usually not considered. Ignoring these factors can completely bias the analysis.

Factors Affecting Near-Miss Conflict Data Collection

  1. Road users are assumed to be represented by points (e.g. centroid, center of front bumper) and the road user size (e.g. vehicle size) is ignored. This can lead to significant errors in conflict indicator values.
  2. When using video data, to accurately recover the positions of various road users, geometric elements need to be mapped back from camera image space to the world space. This mapping process is called “camera calibration” and is ignored in many systems that rely instead on tracking in the image pixels. Road user tracking in real-world coordinates significantly improves the accuracy of the tracking performance by correcting for perspective effects and other distortions due to projection on the image plane. Ignoring this step leads to significant errors in measuring quantities such as distances, speeds, deceleration and conflict indicators. Even if camera calibration is undertaken, a poor camera calibration can cause errors up to 1 sec in conflict indicators, which is a critical rate of error.
  3. The relationship between conflicts and crashes varies by crash type and across jurisdictions. It is vital that a proven relationship exists between the crash type of interest and the conflict measure being used. Many systems available use only one conflict measure for all types of crashes.


Even with accurate, objectively defined conflict measures, it must be recognized that sensors do not provide perfect data.


In conflict detection, false positives and false negatives are inevitable. They can, however, be minimized in order to accurately predict crash risk. Extensive testing and validation is needed to refine the conflict extraction process to reduce false positives and negatives, and include only those conflicts that are highly predictive of future crashes.

Best Practice for Conflict Measurement

In addition to precise definitions of the five conflict measures required, numerous in-depth conditions should be applied to ensure accuracy. These conditions include:


  1. Eliminating road user trajectories that are too short in length to provide reliable data.
  2. Consideration of the speeds and angles between road users and eliminating data points that don’t fall within acceptable and reasonable ranges. These ranges vary by specific encounter types (e.g. rear-end, sideswipe, right-angle).
  3. Calculating conflict measures at a frame of video only if both road users are moving above a minimum speed, which can differ by site type.
  4. Filtering data based on threshold values, which can vary by conflict measure, after conflict measures are calculated.
  5. Keeping only the conflicts that meet the threshold criteria for a minimum number of video frames, based on the number of frames per second recorded.

Does Your Conflict Analytics Data Prove there is a High Probability of Crash Risk?

Not all systems for extracting conflicts, or ‘near-misses’, are the same and the reliability of the results needs to be established before relying on them to evaluate safety.


Using conflict analysis measures that haven’t been extensively validated against crash data is not useful for determining crash risk. It is important to recognize that not only are several conflict indicators required, but different crash types are related to different conflict types and with different threshold values. These relationships may change between jurisdictions with different traffic environments. The conflict extraction process must also take into account vehicle size and calibration of the camera when using video data collection. The application of additional criteria is required to minimize the number of false positives and false negatives. Not doing so may result in seemingly small errors that render the results meaningless.

About the Author

Craig Lyon

has 25 years of experience as a road safety engineer focused on applied research projects. In 2020, Craig joined AMAG as General Manager for North America and Senior Road Safety Engineer. Craig has made significant contributions to the state-of-the-art knowledge in road safety found in the AASHTO Highway Safety Manual, including the development of statistical models for predicting crashes, road safety management analysis methods, and the development of crash modification factors (CMFs). Craig is recognized as an expert in the statistical analysis of safety data and was a long-time member of the Transportation Research Board Committee on Safety Performance Analysis.

Share this post