What PAS 170 tests prove and limitations.

PAS 170-1 defines a simple, repeatable way to test low-speed vehicle impacts for storefront and public-realm applications. This page clarifies what the standard covers, how test articles are mounted, and how penetration/overrun are judged—so you can specify devices correctly. Use it to separate incidental protection from hostile threats where an HVM bollard or crash rated bollard standard is actually required. Include one-sentence context that naturally links upward to the parent hubs (this section and the chapter hub). Add SIRA context with a link to SIRA Bollards (UAE) when relevant. Link installation pages only if helpful: What to Expect and Installation Guide.

Important: This is a general guide. For live projects we develop a tailored Method Statement & Risk Assessment (MS/RA) and align with authority approvals (e.g., SIRA) where in scope.

441.1 Purpose & scope

Defines a standardized way to assess low-speed impact performance for storefront and public-realm measures. Useful where hostile risk is low and an HVM bollard isn’t justified. Clarifies what PAS 170-1 covers vs what only a crash rated bollard standard addresses (411–416, 434).

PAS 170-1 focuses on benign traffic scenarios—slow, accidental strikes from passenger cars or light goods vehicles near glazing and pedestrian areas. It gives a consistent test method so different posts/rails/planters can be compared like-for-like. It does not simulate deliberate attacks or longer run-ups. Where credible hostile scenarios exist, escalate to certified crash standards overview (IWA/ASTM).

In practice, treat PAS 170-1 as a convenience protection benchmark to prevent storefront damage and protect people from driver error. Use the Purpose/Tier Matrix to judge if your site falls into this low-speed tier or needs an HVM path via the design selection guide.

AspectWhat mattersWhere to verify
IntentAccidental, low-speed strikesLow-Speed Impact Ratings (440)
ThreatNo hostile vehicle assumptionThreat Scenarios (212)
EscalationTriggers to move to HVMWhen to use Low-Speed vs HVM (434)

441.2 Test articles & setup

Specifies how the barrier/post is mounted, foundation notes, and measurement zones. Emphasize that installation must mirror the testbed to claim performance. If your context later escalates to hostile risk, move to HVM bollard selection (432).

PAS 170-1 tests the complete as-tested configuration—post, fixings, and foundation or base plate. A pass on one foundation type doesn’t guarantee performance on another. Document socket dimensions, anchor types, concrete grade/cure, and any sleeves. For surface-mounted kits, confirm slab thickness and reinforcement are comparable to the test bed.

Before specifying, compare your installation drawing with the certificate photo set and layout notes. Where site utilities constrain depth, consult utilities conflicts & depth classes and, if necessary, re-select a product proven on a shallow or alternative base that still matches the tested arrangement. If approvals apply (e.g., Dubai), coordinate early with SIRA Bollards (UAE).

441.3 Vehicles, speeds, masses

Outlines low-speed vehicle classes and impact bands used in PAS 170-1. Record actual storefront context (222–224) so the selected device isn’t misapplied where a crash rated bollard is required.

PAS 170-1 uses defined vehicle classes at low impact speeds representative of curbside maneuvering—typically short run-ups with limited acceleration. When scoping your site, capture realistic approach speeds using the run-up distance and speed estimation methods pages, then check if those speeds remain within the PAS 170-1 band. If longer approaches or heavier vehicles are credible, step up to an HVM standard.

441.4 Measurements & acceptance

Explains penetration/overrun style measurements and pass/fail logic at low energy. Keep evidence tables and photos aligned to your site layout and clear gaps (232, 322).

Pass/fail is determined using measured penetration/overrun limits referenced to a defined defend line. Record any residual set or damage that could compromise future performance. For arrays, check clear-gap calculations and keep in mind that array interactions can change behavior relative to a single post test.

For commissioning evidence on live projects, adapt the intrusion tests concept to verify finished positions and gaps (no crash test implied). Keep a disciplined photo/measurement set that matches the test report’s reference points.

441.5 Reporting & marking

What a valid test report includes, how products are identified, and labeling conventions. Tie report fields to your submittals (431, 444, 938) to avoid reviewer pushback.

A valid report should name the test laboratory, report number, test date, vehicle class/speed, article description, mounting/base detail, and measurement results with images. Ensure the product identity (family/variant), any sleeves/finishes, and base conditions are unambiguous. Cross-refer these fields inside your submission pack guidance and the evidence & documentation page to streamline reviews.

441.6 Typical applications

Shopfront glazing, café spill-outs, pedestrianized edges—places with benign vehicles and short run-up (214, 231). Not a substitute for an HVM bollard where credible hostile scenarios exist (212, 432).

Use PAS 170-1 devices to limit bumper-level incursions at glazing lines, protect alfresco zones from low-speed roll-aways, and define edges in shared spaces. Good candidates have constrained approach paths, traffic calming, and close supervision. Where public events increase crowd density or run-ups extend, introduce temporary layouts from event reconfiguration or escalate to HVM.

441.7 Limits & pitfalls

Low-speed energy only; foundation/config sensitivity; mis-reads of penetration photos. When in doubt, escalate to crash rated bollard mapping and equivalence checks (414, 421).

Common errors include treating PAS 170-1 as equivalent to IWA/ASTM ratings, swapping to a different base detail, or misreading still images that don’t show final rest positions. Another pitfall is ignoring array effects: mixed posts, wide spacing, or sloped pavements can alter behavior. If uncertainty remains, review standards equivalency and lock rating-critical dependencies in documents.

441.8 Mapping to HVM standards

How to explain differences vs IWA/ASTM/BS crash standards without implying equivalence. Use purpose/tier matrix (235) and anti-downgrade clauses (435) to prevent substitutions.

PAS 170-1 is not an HVM standard. It uses lower energies, shorter run-ups, and different acceptance metrics. When senior reviewers query “equivalence,” signpost them to how to read ratings and the purpose/tier matrix. Then make the anti-downgrade logic explicit in specs using the guidance under anti-downgrade / equivalence clauses.

441.9 Using PAS 170-1 in specs

Write performance clauses that lock the tested configuration, installation, and evidence. Add upgrade triggers so a future threat change cleanly moves you to an HVM or crash rated bollard (433, 446).

In your specification template, reference PAS 170-1 by title and edition; state the test article identity (family/variant), mounting/base detail, and allowable allowable variants. Require submittals to include the report number, photo set, and an installation drawing that exactly matches the tested arrangement. Add upgrade paths to HVM with clear triggers (e.g., new vehicle classes, longer approaches, event modes).

Related

External resources

441 PAS 170-1 Low-Speed Impact Tests — FAQ

Is PAS 170-1 the same as an HVM crash rating?
No. PAS 170-1 addresses low-speed, accidental impacts. HVM crash ratings (e.g., IWA/ASTM) simulate higher-energy, deliberate attacks with different vehicles, speeds, and acceptance criteria.
Can I change the foundation and keep the same PAS 170-1 performance?
Only if the new foundation is proven as part of the same tested configuration or documented as an allowable variant. Otherwise, performance claims do not transfer.
When should I escalate from PAS 170-1 to HVM?
Escalate when credible run-ups increase, heavier vehicles are possible, crowds are dense, or security threats are identified. Use the Purpose/Tier Matrix and selection pages to decide.
What must be in a compliant PAS 170-1 submittal?
Test report number/date, lab identity, vehicle class/speed, article and mounting details, measurement results with images, and an installation drawing matching the tested arrangement.