4. MPDB barrier face and honeycomb characteristics

The MPDB (Mobile Progressive Deformable Barrier) is not a rigid wall. Its crash signature — and therefore every occupant-load and structural-compatibility conclusion drawn from an MPDB test — is governed by a deformable aluminium honeycomb face bolted to a rigid backing. If the honeycomb is treated as a generic "soft front," the test loses its meaning: the barrier is a calibrated force–displacement device, and its stiffness, cell geometry, and deformation pattern are what convert an approaching vehicle's front-end aggressiveness into a measurable, repeatable load history. This chapter explains what the honeycomb face actually is, how its mechanical behaviour is specified and verified, and how to read its deformation as diagnostic evidence.

What the barrier face is made of

The MPDB face is a stack of aluminium honeycomb blocks, typically bonded into a single cartridge that is mounted on the moving barrier trolley. The honeycomb is expanded from thin aluminium foil into a hexagonal cell array; the cell walls are oriented so that the primary crush direction is along the cell axis (the direction of travel). Two material regimes are normally distinguished:

  • Cell size and foil gauge set the plateau stress. Smaller cells and thicker foil raise the crushing force; larger cells and thinner foil lower it. A typical MPDB face uses a graded or uniform cell specification chosen so the face produces a defined force level over the working stroke.
  • Cell axis orientation must be parallel to the impact direction. Off-axis loading produces shear buckling and a much lower, erratic plateau — a common cause of non-conforming barrier behaviour.
  • Backing plate and bonding transfer the crushed load into the trolley structure. Debonding at the honeycomb-to-backing interface changes the effective loaded area and must be checked after every test.

The face is a consumable: it is designed to crush, and it is replaced or re-certified at defined intervals. Its condition before the test is therefore part of the test validity, not a cosmetic detail.

Stiffness: the force–displacement signature

Under axial compression, aluminium honeycomb behaves in three stages. An initial elastic rise reaches a peak, then the cell walls fold progressively and the force settles onto a relatively flat plateau, and finally, as cells densify, the force rises steeply. For compatibility assessment, the plateau is the useful region: it is where the barrier presents a roughly constant reaction force to the vehicle front, independent of how far it has been crushed.

Two parameters matter most in practice. The plateau force level determines how much load the barrier imposes on the striking vehicle and, by reaction, how the vehicle's structure is exercised. The stroke available before densification determines how much deformation the barrier can absorb before it becomes effectively rigid. A barrier that densifies early behaves like a wall for the remainder of the impact, which distorts the load path and inflates occupant loads.

When reviewing barrier data, always pair the force level with the stroke over which it is sustained. A quoted plateau stress without a usable stroke is not a complete stiffness specification.

Geometry and the loaded area

The face geometry — overall height, width, and the position of the honeycomb relative to the trolley centreline — defines the contact patch with the vehicle. Because the honeycomb is a cellular array, the load is not applied uniformly: it concentrates where the vehicle's front structure (bumper beam, longitudinal rails, lower load path) contacts the face. The resulting deformation map is a footprint of the vehicle's front-end geometry and stiffness distribution.

This is why the barrier face is a compatibility instrument. A vehicle with a tall, stiff, narrow front structure will crush a concentrated patch and generate a high local force; a vehicle with a low, broad, compliant front will spread the crush over a larger area. The barrier does not "know" which vehicle hit it — it simply records where and how hard it was pushed. Reading that record correctly is the analyst's job.

MPDB honeycomb face: force–displacement behaviour and deformation footprint Left: force–displacement curve of aluminium honeycomb showing elastic rise, plateau, and densification. Right: plan view of the barrier face with a vehicle front contacting it, producing a localized crush footprint. Force–displacement signature displacement force elastic rise plateau densification usable stroke peak Deformation footprint (plan view) honeycomb face vehicle front localized crush lower path backing

Deformation behaviour and what it tells you

After the test, the crushed face is a permanent record. Three patterns are worth distinguishing:

  • Uniform, full-height crush across the contact area indicates a broad, well-distributed front structure — generally favourable for compatibility, because the load is shared over a large area.
  • Concentrated, deep local crush with surrounding cells barely touched indicates a narrow, stiff load path (often a single rail or a stiff bumper beam). The local force is high even if the total force is moderate, which is the classic incompatibility signature.
  • Shear or off-axis collapse, where cells fold sideways rather than axially, indicates either a geometry mismatch (contact above or below the intended load path) or a barrier installation fault. This pattern invalidates the stiffness assumption and should trigger a re-test rather than a data interpretation.

Densification is the failure mode to watch for. If the crush depth approaches the cell height, the remaining stroke is exhausted and the barrier begins to act as a rigid reaction surface. In that regime, occupant loads rise sharply and any comparison with a compliant-barrier test is no longer like-for-like.

Verifying the face before and after a test

Because the face is calibrated, its condition must be confirmed. A practical pre-test check covers cell-axis orientation, visible pre-crush or handling damage, bond integrity at the backing interface, and dimensional conformance to the specified face geometry. Post-test, record the maximum crush depth, the footprint outline, and any shear or debonding, and compare against the barrier's certification limits. A face that has densified or debonded should not be reused for a compatibility assessment.

Do not infer vehicle compatibility from total barrier force alone. Two vehicles can produce the same integrated force with very different footprints — one broad and benign, one narrow and aggressive. The footprint, not just the force, carries the compatibility information.

Reading the barrier as an instrument

The honeycomb face converts an unknown vehicle front into a known reaction: a plateau force sustained over a usable stroke, distributed over a footprint set by the vehicle's geometry. Stiffness tells you how hard the barrier pushes back; geometry tells you where; deformation tells you how the vehicle's structure engaged it. Keeping those three readings separate — and checking that the face was in certified condition — is what makes an MPDB result interpretable rather than merely numerical.

← Previous 📖 Contents Next →