3. Safety program requirements mapping

Frontal crash configuration selection is not a single decision — it is a mapping problem. Each safety program defines its own barrier, impact speed, overlap, dummy family, and injury criteria, and a vehicle that satisfies one program may still fail another. Before any CAE model is built or any sled pulse is chosen, the engineer must translate the applicable regulatory and consumer-rating requirements into a concrete set of load cases. This section builds that mapping systematically, starting from the regulatory baseline and moving through consumer protocols to the less common frontal variants.

FMVSS 208: The Regulatory Baseline

FMVSS 208 (49 CFR 571.208) is the U.S. federal occupant crash protection standard and the anchor for most North American frontal work. It is not one test but a family of them, and the configuration depends on the vehicle type and the compliance option the manufacturer selects. For passenger cars and light trucks, the principal frontal configurations are:

• Rigid barrier, 0° (full frontal), 56 km/h (35 mph) — both belted and unbelted dummies, driver and right-front passenger. The barrier is a fixed, flat, rigid concrete wall; the vehicle strikes it perpendicular to its longitudinal axis.
• Rigid barrier, ±30° angled, 56 km/h — the vehicle is towed at an angle into the same rigid wall, loading the structure asymmetrically and exercising the seat-belt geometry under lateral occupant excursion.
• Offset deformable barrier (ODB), 40% overlap, 56 km/h — a deformable honeycomb-faced barrier, used in the belted compliance path, with the vehicle offset so 40% of its width engages the barrier.

The dummy set is the Hybrid III 50th-percentile male in the driver and passenger positions, with the 5th-percentile female used in specific configurations. Injury assessment reference values (IARVs) are checked on head (HIC15 ≤ 700), neck (Nij ≤ 1.0), chest (deflection and 3 ms clip), and femur (axial force), with the exact limits depending on belt status and seating position. A critical practical point: FMVSS 208 permits unbelted occupants, so the restraint system must protect an unbelted 50th-percentile male at 56 km/h — a far more demanding structural and restraint requirement than any belted-only consumer test.

US NCAP: Same Barrier, Higher Speed

The U.S. New Car Assessment Program (US NCAP) frontal test uses the same rigid full-width barrier as FMVSS 208 but raises the impact speed to 56 km/h is the regulatory figure; NCAP runs at 56 km/h for the frontal test as well in the current program, with the distinguishing feature being the 5th-percentile female dummy in the driver seat and a star rating derived from combined injury risk. In practice, the US NCAP frontal configuration is a 56 km/h rigid barrier test with the Hybrid III 5th-percentile female driver and 50th-percentile male passenger, scored through a risk curve rather than a pass/fail threshold. The engineering consequence is that the same hardware must satisfy a binary regulatory limit and a continuous star-rating score, so the design target is usually set well inside the IARV to leave margin for rating.

Euro NCAP: Offset, Mobile Barrier, and the MPDB

Euro NCAP's frontal assessment has evolved substantially and now centers on the Mobile Progressive Deformable Barrier (MPDB) test at 50 km/h with 50% overlap. Unlike the fixed ODB, the MPDB is a moving trolley carrying a deformable honeycomb face; both the vehicle and the barrier are in motion, which better represents car-to-car compatibility. The dummy set is the THOR 50th-percentile male in the driver seat and a Hybrid III 5th-percentile female in the passenger seat, with additional rear-seat assessment. Euro NCAP also retains a full-width rigid barrier test at 50 km/h to evaluate restraint performance for a broader occupant range, and scores "compatibility" — how aggressively the vehicle deforms the barrier, which penalizes overly stiff front ends that endanger other cars.

The MPDB introduces a metric that has no FMVSS 208 equivalent: the barrier deformation and the resulting compatibility score. A vehicle tuned only for self-protection against a rigid wall will often score poorly here because its front structure is too stiff. This is the single most common reason a North American-compliant vehicle needs structural retuning for Europe.

Other Frontal Protocols Worth Mapping

Beyond the big three, several protocols appear in global programs and should be captured in the requirements matrix:

Two mapping traps deserve emphasis. First, speed is not the only variable: the 56 km/h rigid wall and the 50 km/h MPDB differ by 6 km/h but by a far larger margin in structural demand, because the MPDB's moving mass and deformable face change the energy partition. Second, dummy family changes the restraint target: THOR's improved chest and abdomen instrumentation captures loading that the Hybrid III under-reports, so a restraint that passes on HIII may show elevated THOR injury metrics. The requirements matrix must therefore record dummy type alongside barrier and speed, not treat them as interchangeable.

Building the Requirements Matrix in Practice

The mapping output should be a single controlled document — a requirements matrix — that every downstream load case references. A workable structure records, per row: program, test name, barrier type and mass, impact speed, overlap percentage, impact angle, dummy family and percentile, seating position, belt status, and the governing pass/fail or scoring metric. The matrix above is a condensed example; the working version adds barrier mass (the MPDB trolley is 1,400 kg, the fixed ODB is effectively infinite), the pulse corridor or sled pulse file, and the injury criteria set with numeric limits.

Once the matrix exists, configuration selection becomes a filtering exercise. For a vehicle targeting North America only, the load-case set is FMVSS 208 full, angled, and ODB plus US NCAP frontal. For a global vehicle, add Euro NCAP MPDB and full-width, and expect the MPDB to drive front-end stiffness tuning while the FMVSS 208 unbelted case drives restraint energy management. The two requirements pull in opposite directions — a softer front end helps MPDB compatibility but can increase intrusion in the unbelted 56 km/h rigid test — and that tension is precisely what the configuration selection must resolve.

The practical takeaway is that "frontal crash configuration" is shorthand for a matrix of barrier, speed, overlap, and dummy combinations, each with its own governing metric. Selecting a configuration means selecting the subset of that matrix the vehicle must satisfy, then resolving the conflicts between them — most notably the stiffness conflict between self-protection against a rigid wall and compatibility against a moving deformable barrier. The next step in the workflow is to convert each selected row into a concrete CAE load case and sled pulse, which is where the matrix becomes an executable test plan.