2. Regulatory and consumer-test landscape

A crash load case is never invented in isolation. Every acceleration pulse, barrier geometry, impact angle, and dummy configuration used in a CAE model qualification traces back to a governing document: a federal regulation, a regional directive, a consumer rating protocol, or an industry standard. Before a finite element model can be called "qualified," the analyst must know which document defines the load case, what its acceptance thresholds are, and how strictly the boundary conditions must be reproduced. This chapter maps that landscape so that later modelling decisions — pulse selection, barrier stiffness, occupant positioning — rest on a defensible regulatory basis.

Two Families of Requirements: Homologation versus Consumer Rating

It helps to separate the landscape into two families that differ in legal force and in how they are used for model qualification.

Homologation standards — FMVSS in the United States, ECE Regulations under the 1958 Agreement in Europe and many other markets, and national equivalents such as GB in China — are legally binding. A vehicle cannot be sold without passing them. Their test procedures are prescriptive: barrier mass and face geometry, impact speed with a defined tolerance, dummy type and seating procedure, and pass/fail injury criteria are all fixed. For modelling, this prescriptiveness is a gift: the load case is fully specified, so a qualified model must reproduce the regulation's exact pulse and boundary conditions.

Consumer-test protocols — Euro NCAP, IIHS, NHTSA's NCAP, C-NCAP, ANCAP, Latin NCAP, and JNCAP — are voluntary but commercially decisive. They evolve faster than regulation, add more severe or more diverse load cases, and score rather than simply pass or fail. Because they change on a roughly three-year cycle, a model qualified against one protocol release may need re-validation when the protocol is updated. Tracking the protocol version is therefore part of qualification traceability, not an afterthought.

The Core Load Cases and Their Governing Documents

The table below summarizes the load cases most commonly used to qualify full-vehicle and occupant-restraint models, together with the document that defines each one. Speeds and criteria are indicative of current practice and should always be confirmed against the latest released version of the document.

How the Documents Differ in What They Fix

The practical difficulty in model qualification is that the same nominal load case can be specified differently across documents. Three dimensions matter most.

Barrier definition. FMVSS 214 uses a rigid moving deformable barrier with a specific honeycomb face; Euro NCAP uses a different MDB mass and face stiffness. A model qualified against one barrier will not automatically reproduce the other's intrusion profile. The barrier's force–deflection characteristic must be modelled explicitly, not approximated as a rigid wall.

Pulse and boundary conditions. ECE R94 prescribes an offset deformable barrier with a defined honeycomb block; the resulting vehicle deceleration pulse is a consequence of the barrier, not an input. In contrast, sled-based occupant tests (for example, ECE R16 belt anchorage and some FMVSS 208 unbelted sled configurations) prescribe the pulse directly. The analyst must know whether the pulse is an input or an output of the simulation.

Injury criteria and dummy type. FMVSS 208 uses Hybrid III 50th percentile; Euro NCAP increasingly uses THOR and WorldSID. Criteria such as HIC, chest deflection, and BrIC have different thresholds and different dummy-specific measurement locations. A model qualified with Hybrid III cannot be assumed valid for THOR without re-correlation of the dummy model itself.

Reading the Landscape as a Qualification Matrix

The figure below organizes the main documents by load-case family and shows how each family feeds the model qualification activity. It is a map, not a procedure: the analyst uses it to confirm that every load case in the qualification plan has a named governing document and a defined severity.

From Document to Qualification Entry

The map becomes actionable when each load case is converted into a qualification entry with four mandatory fields. Consider a worked example for a Euro NCAP frontal MPDB case:

Load case ID : LC-FR-03
Document     : Euro NCAP 2023, Frontal MPDB, 50% overlap
Severity     : 50 km/h, MPDB 1400 kg, honeycomb face per protocol
Dummy        : THOR 50th percentile, driver; Hybrid III 5th, rear
Pulse source : output of barrier + vehicle interaction (not prescribed)
Criteria     : HIC15, chest deflection, BrIC, femur loads per protocol
Model target : barrier force-deflection, vehicle pulse, occupant kinematics
Tolerance    : pulse peak within ±5%, intrusion within ±10 mm (example)

The "pulse source" field is the one most often mishandled. For MPDB and ODB cases the deceleration pulse is an emergent result; imposing a measured pulse as a boundary condition would bypass the very structural behaviour the model is meant to predict. For sled cases the pulse is prescribed and must be applied as an input. Confusing the two produces a model that matches a curve but not the physics.

Version Control and Regional Overlap

Two practical hazards deserve explicit treatment. First, consumer protocols are revised on a fixed cadence, and a model qualified against the previous release may not satisfy the current one — the barrier mass, impact speed, or dummy may have changed. The qualification record must therefore cite the protocol release year, and the model should be re-checked whenever the governing document is updated. Second, the same physical test appears in multiple documents with different tolerances. A vehicle developed for ECE R94 and Euro NCAP simultaneously must satisfy both, and the model must be qualified against the stricter boundary where they diverge. Building a cross-reference matrix that lists, for each load case, every document that governs it and the most severe specification among them is the most reliable way to avoid a late-stage surprise.

With the landscape mapped, the next step is to translate these documents into a concrete qualification plan: which load cases to include, in what order, and what evidence each must produce. That translation is the subject of the following chapter.