2. Regulatory and consumer rating frameworks

Crash safety targets are never invented in a vacuum. Every requirement a vehicle program must satisfy originates from one of two families of documents: government regulations, which are mandatory and enforced through type approval or self-certification, and consumer rating programs, which are voluntary but commercially decisive. A target-setting engineer must be able to read both, extract the load cases and injury criteria that apply to a given market, and translate them into a single internally consistent requirement set. This chapter maps the five frameworks that dominate global passenger-car development — FMVSS, ECE, C-NCAP, Euro NCAP, and IIHS — across the four principal impact directions: frontal, side, rear, and pedestrian.

Two Regulatory Philosophies: FMVSS vs. ECE

The United States operates a self-certification system. The manufacturer declares that a vehicle complies with the applicable Federal Motor Vehicle Safety Standards (FMVSS) and is subject to random audit by NHTSA. The European Union, and the UNECE framework it anchors to, operates a type-approval system: an accredited technical service witnesses the tests and the approval authority grants the certificate. This difference matters practically because it changes who runs the test, when the test occurs in the program, and how much documentation must be retained.

For frontal protection, FMVSS 208 is the anchor. It requires a 56 km/h (35 mph) full-frontal rigid-barrier test with belted 50th-percentile male Hybrid III dummies in both front seats, plus an unbelted test condition that many other markets do not impose. Injury criteria are expressed through the HIC15 (Head Injury Criterion over a 15 ms window), chest deflection, and femur axial force. ECE R94, by contrast, uses a 56 km/h 40% offset deformable barrier (ODB) test, which concentrates energy into one side of the front structure and is generally more demanding on the longitudinal rails and the occupant compartment than a full-overlap test.

Side impact shows the same split. FMVSS 214 uses a 1,368 kg moving deformable barrier (MDB) at 54 km/h striking at 27°, with an ES-2re dummy. ECE R95 uses a 950 kg MDB at 50 km/h at 90°, with the ES-2 dummy. The heavier, angled US barrier loads the side structure very differently from the perpendicular European configuration, which is why a door beam and B-pillar design optimized for one market rarely transfers without modification.

Consumer Programs: Where the Real Competition Happens

Regulations set a pass/fail floor. Consumer programs set the score that appears on a showroom sticker, and they evolve faster. The four programs below are the ones that most often drive design change.

Two entries deserve emphasis. First, IIHS small overlap frontal (25% overlap, 40 km/h) was introduced because vehicles that performed well in moderate overlap were still failing when the barrier engaged only the outer edge of the structure, bypassing the main longitudinal rail. It forced the addition of upper-rail extensions, bumper-to-rail load paths, and in some cases a redesigned subframe. Second, Euro NCAP's mobile progressive deformable barrier (MPDB) replaced the older ODB because it evaluates both the striking vehicle's occupant protection and the damage it inflicts on the opposing vehicle — a compatibility metric, not just a self-protection metric.

Pedestrian Protection: A Different Load Path Entirely

Pedestrian requirements are unique because the "structure" being tested is the vehicle's exterior surface, and the "occupant" is a free-standing human body. The test uses three impactors: a legform (upper and lower leg), a pelvis impactor, and a headform (adult and child, launched at different angles). The headform is fired at the bonnet and windscreen area at 40 km/h, and the measured criterion is HIC, typically limited to 1000 in the adult headform test and 1000 in the child headform test under Euro NCAP, with lower thresholds for full marks.

The engineering consequence is that the bonnet must deform progressively without contacting rigid under-hood components — engine block, strut towers, battery pack in an EV — within the available deformation space. This is why pedestrian protection frequently drives bonnet height, hood inner-panel rib design, and the placement of under-hood packaging. A target-setting engineer must therefore treat pedestrian head-impact clearance as a hard constraint on the front-end package, not an afterthought.

Rear Impact and Whiplash

Rear impact is dominated by whiplash rather than structural crush. FMVSS 202a and the corresponding ECE R17 requirements define a head-restraint geometry zone and a dynamic sled test. Euro NCAP and C-NCAP both run a low-speed rear sled with a BioRID dummy and score neck injury criteria (NIC, Nkm, and upper-neck forces). The design levers are head-restraint height and backset, seat-back stiffness, and the energy-absorption characteristics of the recliner and seat frame. Because the injury mechanism is soft-tissue, the target is usually expressed as a score threshold rather than a pass/fail force limit.

Reading the Frameworks Together: A Target-Setting Workflow

In practice, a program does not treat these five documents as five separate projects. The engineer builds a requirement matrix that lists every load case, the market that imposes it, the dummy, the impact speed, the barrier, and the injury criterion with its limit. Overlapping cases are consolidated; conflicting cases are flagged. The figure below shows how the four impact directions map onto the five frameworks and where the load cases overlap.

From Framework to Target: A Worked Example

Suppose a vehicle is being developed for simultaneous sale in China, Europe, and North America. The target-setting engineer would extract the following minimum set of frontal load cases: FMVSS 208 full frontal at 56 km/h (belted and unbelted), ECE R94 ODB at 56 km/h, C-NCAP ODB at 50 km/h, Euro NCAP MPDB at 50 km/h, and IIHS moderate overlap at 64 km/h plus small overlap at 40 km/h. That is six distinct frontal configurations. Rather than designing six separate structures, the engineer identifies the worst-case combination for each structural element: the small overlap test drives the upper rail and A-pillar load path; the ODB drives the longitudinal rail and firewall intrusion; the full frontal drives the occupant restraint and airbag tuning.

A practical requirement matrix entry might look like this:

Load case:      IIHS small overlap frontal
Impact speed:   40 km/h (25 mph)
Overlap:        25% of vehicle width, driver side
Barrier:        rigid, 1,524 mm radius corner
Dummy:          SID-IIs (driver), Hybrid III 50th (passenger)
Key criteria:   HIC15 <= 700, chest deflection <= 50 mm,
                femur force <= 4.0 kN, lower leg <= 4.0 kN,
                occupant compartment intrusion <= 150 mm
Design levers:  upper rail extension, bumper-to-rail
                load path, door hinge and latch strength,
                A-pillar reinforcement, seat belt pretensioner
                and load limiter calibration

Note that the criteria above are representative target values used for planning, not measured results. The engineer would confirm the exact limits against the current protocol document, because consumer programs revise thresholds on a roughly two-to-three-year cycle.

Key Takeaways

• FMVSS is self-certified and includes unbelted frontal and angled side impact cases that ECE does not require.
• ECE is type-approved and uses offset frontal and perpendicular side impact, with different barrier masses and angles.
• C-NCAP and Euro NCAP are consumer programs that score performance and evolve faster than regulation; Euro NCAP's MPDB adds a compatibility metric.
• IIHS drives structural load-path design through its small overlap test and has updated its side protocol to a higher speed and heavier barrier.
• Pedestrian protection constrains front-end packaging and bonnet deformation space, with headform HIC as the primary criterion.
• Rear impact is a whiplash problem solved through head-restraint geometry and seat-back energy management, not structural crush.

The next step in target setting is to convert this requirement matrix into measurable vehicle-level and subsystem-level targets — a process that begins with benchmarking and ends with a signed-off target cascade.