Crash Rated Does Not Automatically Mean Protected

It’s easy to treat an impact test certificate like a guaranteed stamp of safety. The bollard or gate survived a high speed crash test in a controlled facility, earned its rating, and gets ticked off the risk register.

But the test certificate only answers part of the site-security question.

A crash rating tells us how a particular barrier configuration performed during a defined, controlled full-scale impact test. Actual protection comes down to how that equipment interacts with real world topography, shallow ground conditions, vehicle approach paths, and site interfaces. When you ignore the gap, you end up paying top dollar for equipment that offers little more than a false sense of security.

What Impact Ratings Actually Measure

Standards like BS ISO 22343-1 give us clear data points: vehicle mass, speed, impact angle, penetration distance, and major debris spread. What they don't give you is context.

Applying one blanket HVM requirement across an entire site can miss how vehicle threats actually vary around the perimeter. A Vehicle Dynamics Assessment helps establish what vehicles can credibly approach, from where, and at what speed. Without that step, one part of a site can be unnecessarily over-specified while a more exposed approach remains under-protected.

A rating is only useful if the tested vehicle, mass, impact speed and angle are relevant to the vehicle-borne threat that can realistically reach that location. Kinetic energy is useful context, but it isn't a substitute for matching the actual threat and impact conditions.

Without analysing real approach geometry, you end up over-specifying quiet, unapproachable perimeter lines while leaving high-speed vehicle corridors dangerously exposed.

The Simulation Gap: Computer Models vs. Physical Reality

Finite Element Analysis (FEA) and other numerical modelling can be extremely useful when developing vehicle security barriers, exploring alternative configurations or understanding how a system may behave under impact.

But modelling and physical impact testing are not the same thing. An ISO 22343-1 classification comes from the defined full-scale impact test, not from a computer simulation.

The quality of any model also depends on the assumptions and validation behind it: material properties, connections, weld behaviour, soil interaction, strain rate and failure modes all matter. A model calibrated against physical evidence carries much more weight than one relying on theoretical assumptions alone.

Simulations have value, but only if they’re calibrated against a physical test.

Real life isn't a software model. Uncalibrated simulations fail to predict the dynamic stresses of a real collision, like sudden shear points, weld pops, or structural twisting under load. If a barrier’s rating exists solely in a digital model, it should not be presented as equivalent to a full-scale impact classification.

The Installation Gap: Paper Compliance vs. Site Reality

That gap widens when field conditions require configurations that were not covered in the test. permanent HVM products rely entirely on engineered foundation details, but on a live build, buried utilities, shallow slabs, or drainage runs frequently get in the way. I’ve been asked multiple times if the engineer can make the pit shallower, shorten the footprint, or adjust the layout, but modifying the foundation means you can no longer simply assume that the published impact-test performance applies to the altered configuration. If a tested foundation is shortened, narrowed or otherwise materially changed, the installation is no longer the configuration that produced the published test result. That doesn't automatically prove it will fail, but neither can the original impact rating simply be assumed to apply.

I've even had a colleague attend a site where the product had been installed but roughly a third of the specified foundation depth had simply been omitted because the ground was difficult to excavate. Any proposed alternative foundation needs proper engineering justification, ideally involving the manufacturer and an appropriately qualified HVM structural engineer. For some NPSA-recognised systems, alternative foundation design is specifically required tobe approved by a Principal Member Grade HVM engineer on the RSES.

Ultimately, a classification records how a barrier performed in one defined ISO 22343-1 impact test; a specific vehicle weight, speed, angle, penetration distance, and debris spread. It tells you what happened in that test. The designer still has to establish whether that test is relevant to this site. If approach geometry permits higher vehicle speeds, or if an altered foundation compromises restraint, the certificate can no longer be relied upon, on its own, as evidence that the installed arrangement will deliver the tested performance.

ISO 22343 itself recognises this distinction. Part 1 deals with impact performance and testing; Part 2 deals with application, including threat, site assessment, selection, installation and use.

Coverage Gaps: Leaving Unrated Pathways

A perimeter protection system is only as capable as its weakest interface. Securing a primary vehicle entrance with an impact-rated gate achieves little if a credible vehicle route allows the same attacker to bypass it through an adjacent unprotected section of boundary. Equally, that doesn't mean every metre of fence needs to be crash-rated. It means every credible vehicle approach needs to be understood.

A hostile driver can exploit the path of least resistance, not necessarily the location where the project has concentrated its HVM spend. Specifying isolated crash-rated products without looking closely at the full boundary layout leaves gaps that allow a vehicle to simply bypass the rated element altogether.

What to Check Before Approving a Design

To ensure your perimeter delivers true physical protection rather than compliance on paper, evaluate these critical areas before finalizing the design package:

• Request the Full Impact Classification: Look beyond a generic "HVM rated" label. Request the exact performance code detailing vehicle mass, test speed, angle, penetration distance, and debris spread.

• Verify Penetration Clearance: Compare the certified penetration distance against your site layout. If the protected asset sits within the measured vehicle penetration or relevant debris zone, simply stopping the vehicle may not achieve the required outcome.

• Review Test Footage and Documentation Carefully: Review the actual classification and available test report, not just marketing photographs or crash-test video. Understand the penetration measurement, major debris result, barrier configuration and what happened to the system during the test.

• Match Foundations to Site Realities: Check whether ground conditions, utility surveys, and sub-slab constraints accommodate the exact tested foundation detail before procurement.

• Check the approach conditions: Has a credible vehicle threat and approach speed actually been established, ideally through an appropriate VDA?

• Check the tested configuration against the proposed installation: Spacing, foundation, barrier length, gate opening, interface details and installation conditions should be checked against the evidence supporting the product's rating.

A crash rating doesn't prove resistance to every vehicle attack

There is another limitation worth understanding. ISO 22343-1 assesses a defined single high-speed impact. It does not demonstrate resistance to every way a vehicle might attack a barrier, including repeated low-speed ramming. Different threats require different evidence. Again, the important point is not simply whether a product carries a rating, but whether the rating actually corresponds to the attack method the design is intended to mitigate.

Real Protection is an Integrated Outcome

A crash rating measures a product in isolation. Real perimeter security is an integrated outcome where design, foundation engineering, approach geometry, and site interfaces align.

When project information contains technical contradictions, ignores site constraints, or treats certified products as silver bullets, sites are left carrying risk.

Protection isn't bought in a box. A crash rating is product evidence. Protection is a site outcome.

It comes from aligning the threat, approach geometry, standard, product, foundation, layout and installation so that the finished site still delivers the security outcome originally intended.

When those things stop aligning, the product may still have a perfectly valid certificate while the site carries a very different level of protection. That's another form of the Security Intent Gap.

About me

Adam Savage is the founder of Relkron, bringing over 26 years of dedicated, hands-on expertise in the physical perimeter security industry. Throughout his career, Adam has specialised in high-security fencing and gates, hostile vehicle mitigation (HVM), product manufacturing, specification, and navigating complex LPS 1175 standards across international markets.

Having delivered intricate perimeter security systems in over 40 countries, Adam has worked closely alongside clients, consultants, contractors, and manufacturers worldwide.