3. Regulatory and consumer test requirements

Knee contact risk in an instrument panel is not evaluated against a single universal number. Depending on the market, the same vehicle may be judged by a federal self-certification rule, a UN type-approval regulation, and one or more consumer protocols, each with its own impactor, impact condition, measurement channel, and pass threshold. A design that satisfies FMVSS 208 may still lose Euro NCAP points, and a C-NCAP-compliant knee map does not automatically demonstrate UN R94 compliance. This chapter explains what each framework actually requires at the knee and lower-leg interface, how the test hardware and loading conditions differ, and how to translate those differences into a defensible intrusion and stiffness target for the IP structure.

Two regulatory families: FMVSS 208 and UN R94/R95

FMVSS 208 is a US federal performance requirement verified by the manufacturer (self-certification). For the upper leg and knee region, the relevant channels are femur load and knee slider displacement measured on the Hybrid III 50th percentile male dummy in frontal rigid-barrier and offset deformable-barrier tests at 56 km/h (35 mph). The femur axial compression criterion is 10 kN per leg, and the knee slider displacement limit is 15 mm per leg. These are occupant-response limits, not IP-intrusion limits: the regulation constrains what the dummy experiences, and the engineer must back-calculate how much panel intrusion and local stiffness are admissible to stay under them. FMVSS 208 also includes unbelted and out-of-position configurations, which matter because an unbelted occupant loads the knee bolster earlier and at a different height than a belted one.

UN R94 (frontal impact) and UN R95 (lateral impact) are type-approval regulations under the 1958 Agreement, tested by the approval authority rather than self-certified. R94 uses a 40% offset deformable barrier at 56 km/h with the Hybrid III 50th male; the knee-relevant acceptance criteria are again femur load (10 kN) and knee slider displacement (15 mm), plus a tibia index limit of 1.3 and a knee-joint compression limit. R95 addresses side impact and is relevant to the IP mainly through the interaction between the intruding door trim and the occupant's lower limbs, and through the requirement that interior components not produce sharp or hard contact surfaces. The practical distinction from FMVSS 208 is procedural: R94/R95 approval requires a documented test report from a designated technical service, and the vehicle is approved as a type rather than certified per unit.

Consumer protocols: Euro NCAP and C-NCAP

Consumer programmes go beyond the regulatory pass/fail by adding knee mapping and body-region scoring. Euro NCAP frontal offset testing (currently the 50 km/h full-width and 64 km/h offset deformable-barrier configurations, with the THOR 50th male in the driver position in newer protocols) evaluates knee, femur, and tibia responses and assigns a colour-coded body-region score. The knee map is generated by firing a knee impactor — a spring-loaded, instrumented striker — at a grid of points across the lower IP surface, recording peak force and displacement at each point. Points that exceed the force or displacement threshold are marked red and reduce the score. Euro NCAP also assesses intrusion through the pedal-panel and footwell displacement measurements, and penalises hard or sharp contact surfaces found during the interior inspection.

C-NCAP follows a similar philosophy with its own impactor and grid. The knee impactor is fired at a defined velocity (typically around 2.5–3 m/s, depending on protocol version) at grid points on the IP lower surface, and each point is scored against force and displacement thresholds. C-NCAP also runs a 50 km/h full-width frontal and a 64 km/h offset test with the Hybrid III 50th male, scoring knee, femur, and tibia responses, and includes a separate lower-leg assessment. The grid density and the exact threshold values are revised between protocol versions, so the engineer must always work from the current published protocol rather than a remembered number.

How the frameworks differ at the knee interface

The table below summarises the knee-relevant differences. Treat the threshold values as the current published limits and confirm them against the applicable protocol version before setting targets.

The most important engineering consequence is that the regulatory channels are occupant-response limits while the consumer knee map is a local surface limit. A panel can pass the 10 kN femur criterion in a full barrier test yet still show red knee-map points, because the impactor loads a small area at a velocity and direction that the full-dummy test does not reproduce. Conversely, a panel with good knee-map scores can still produce excessive femur load if the underlying structure bottoms out against a hard member during the barrier event. Both must be designed for.

From requirement to design target: a worked example

Suppose the task is to set a knee-bolster stiffness target for a new IP that must satisfy FMVSS 208, UN R94, Euro NCAP, and C-NCAP. The following is an illustrative engineering workflow with assumed values, not measured results.

1. Establish the intrusion budget. From the full-vehicle CAE model, run the 56 km/h offset case and extract the maximum rearward displacement of the knee bolster surface at the driver and passenger knee heights. Assume the model shows 85 mm of panel intrusion at the driver knee reference point. The femur load is driven by the relative velocity between the occupant's knee and the panel, so the intrusion budget must be reduced until the simulated femur load has margin against 10 kN — for example, target ≤ 7.5 kN to leave 25% margin for build variation and dummy repeatability.
2. Set the local stiffness from the knee map. Take the current Euro NCAP and C-NCAP knee-impact protocol thresholds (force and displacement per grid point) and convert them into a target force–deflection corridor for the bolster. A common approach is to specify an initial stiffness that keeps peak force below the protocol threshold at the impactor velocity, followed by a crush plateau that limits displacement. For an assumed impactor mass of 10 kg at 2.5 m/s, the kinetic energy is 0.5 × 10 × 2.5² = 31.25 J; the bolster must absorb this within the allowed displacement, which sets the minimum crush stroke.
3. Check the bottom-out condition. The bolster must not compress onto the cross-car beam within the allowed displacement. Measure the gap between the bolster rear face and the beam in the CAD package; if the gap is smaller than the required crush stroke, add a collapsible spacer or retune the foam density.
4. Verify against each framework separately. Run the FMVSS 208 and R94 barrier cases for femur load and knee slider; run the knee-impact grid for both Euro NCAP and C-NCAP point thresholds; check pedal-panel intrusion for Euro NCAP. A single CAE run does not cover all four — the barrier, impactor velocity, and grid differ.

Practical verification and common failure symptoms

When a knee-map point fails, the symptom is usually a local hard spot: a clip, a reinforcement rib, or a substrate edge sitting just behind the foam. The fix is local — increase foam thickness, add a crush initiator, or move the hard feature out of the grid — rather than a global stiffness change. When the femur load fails in the barrier test while the knee map is clean, the cause is usually structural bottom-out: the bolster crushes fully and then loads the cross-car beam. The fix is to increase crush stroke or add a collapsible bracket, not to soften the foam further. Distinguishing these two failure modes early prevents the common mistake of softening the entire panel to fix a single red grid point, which then degrades the barrier performance.

Finally, keep the evidence trail explicit. For each framework, record the protocol version, the test or simulation configuration, the measured or simulated channel values, and the margin to the limit. A requirement matrix that maps each knee and intrusion channel to its source framework, limit, and verification method is the deliverable that lets a design review confirm compliance without re-deriving the rules from memory.