IVHS Countermeasures for Rear-End Collisions, Task 2 -- Functional Goals

Wilson, Terry · 1996 · ROSA P / United States. Department of Transportation. National Highway Traffic Safety Administration

archive: archived pipeline: cataloged verified

Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)

Summary

This interim report, produced by Frontier Engineering Inc. for the National Highway Traffic Safety Administration (NHTSA), addresses the development of functional goals for Intelligent Vehicle-Highway System (IVHS) countermeasures designed to prevent rear-end collisions. The primary objective of the broader program is to establish practical performance specifications for autonomous, in-vehicle-based collision avoidance systems for light vehicles. This specific document, Task 2, focuses on defining the functional requirements necessary to guide the design and evaluation of such systems, emphasizing non-cooperative technologies that do not rely on infrastructure modifications or vehicle-to-vehicle communication. The methodology involved a structured analysis of the rear-end crash problem to identify opportunities for intervention. The authors developed a taxonomy of collision subsets and crash-related events, categorized into six primary modifiers: dynamic situations, environmental conditions, roadway characteristics, vehicle characteristics, driver characteristics, and system characteristics. Central to this framework is the definition of "dynamic situations," which describe the relative motion of the lead and following vehicles prior to driver recognition of a hazard. The report analyzes 15 distinct dynamic scenarios, ranging from a stopped lead vehicle with an accelerating following vehicle to various combinations of constant velocity and deceleration. Data from the 1992 National Accident Sampling System (NASS) Crashworthiness Data System was utilized to quantify the prevalence of these situations, revealing that the most common scenario involves a decelerating or stopped lead vehicle and a following vehicle at constant velocity. The report establishes functional goals for three main categories of rear-end collision avoidance systems: Headway Maintenance Systems (including manual, Autonomous Intelligent Cruise Control, and Cooperative Intelligent Cruise Control), Driver Warning Systems, and Automatic Control Systems. Functional goals are defined as qualitative descriptions of data processing algorithms intended to eliminate or mitigate collision severity. For instance, the functional goal for a Driver Warning System requires the system to operate on stopped vehicles, detect the presence of a vehicle ahead, process sensor measurements, warn the driver of dangerous situations, and potentially suggest avoidance maneuvers. The report also standardizes terminology, distinguishing between false alarms (system noise) and nuisance alarms (misinterpretation of non-threat objects), and clarifies that "rear-end" refers specifically to forward-looking collisions where the front of one vehicle impacts the rear of another. The significance of this work lies in its role as a foundational step for developing performance specifications. By subdividing the complex rear-end crash problem into manageable dynamic situations and establishing clear functional goals for each system type, the report provides a structured basis for evaluating existing technologies and designing new countermeasures. The findings support the focus on autonomous in-vehicle systems as the most cost-efficient approach, while acknowledging that infrastructure and vehicle modifications remain valid but less immediate priorities. This framework enables subsequent phases of the program to refine performance guidelines and design test bed systems for empirical validation.

Key finding

The most prevalent dynamic situation in rear-end collisions involves a decelerating lead vehicle and a following vehicle that is stopped or decelerating, accounting for over 50 percent of analyzed cases.

Methodology

dataset

Sample size: 135

Provenance

The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).

Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.

Topics

Ranked by relevance to this paper. Hover a topic for its definition.

• following distance
• crash typology
• time to collision looming
• driver post crash behavior
• secondary collisions
• naturalistic crash near crash