Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2902
NATO member and partner nations implementing AEP-2902 under this agreement, and the suppliers who meet its combat helmet test criteria through a contract
STANAG 2902 is NATO's agreement committing member nations to implement AEP-2902, the non-ballistic test methods and evaluation criteria for combat helmets; it binds nations and NATO bodies, not suppliers, directly.
STANAG 2902 is a NATO Standardization Agreement, currently Edition 3, promulgated 6 February 2019. It is not a technical specification. It is the agreement by which NATO nations commit to implement AEP-2902, Edition A, the Allied Publication that sets out non-ballistic test methods and evaluation criteria for combat helmets. The document's own aim is to respond to an interoperability requirement: "to establish a standard classification to designate the non-ballistic performance of combat helmets when exchanging tactical information in NATO." Its own reasoning for that requirement: "This to ensure interoperability in multinational missions by the use of equipment with matching protection levels against a given threat." Read on its own, STANAG 2902 requires nothing of a helmet manufacturer or supplier. Its obligations run to nations and to NATO bodies, and the test methods themselves sit in AEP-2902, not in this cover.
STANAG 2902 is explicit that it binds nations rather than organisations. Its letter of promulgation describes the enclosed agreement as one "which has been ratified by member nations, as reflected in the NATO Standardization Document Database (NSDD), is promulgated herewith." Under "Agreement," participating nations agree to implement AEP-2902, Edition A - a national commitment, made by ratification, not a duty a supplier signs up to by reading this document. Ratification and implementation stay separate steps: nations that have not already done so are invited to "advise the NSO of their intention regarding its implementation." So "is STANAG 2902 mandatory" has no single answer: it depends on whether a given nation has ratified and implemented it, and this cover names no manufacturer, supplier or test house at all.
The STANAG states it "is effective upon receipt and ready to be used by the implementing nations and NATO bodies" - a NATO-wide mechanism, with partner nations separately "invited to adopt this STANAG." Implementation is tracked by ratification response: "participating nations agree to implement STANAG 2902 (Edition 3) in accordance with their ratification responses." Nations are invited to report their effective implementation, and partner nations their adoption, both "in accordance with AAP-03."
A reader who only has STANAG 2902 in hand does not yet have the test methods it points to. The non-ballistic test criteria, sample sizes and pass thresholds a helmet is actually judged against sit in AEP-2902, Edition A, the publication named under "Standard." STANAG 2902 names one other related document, STANAG 2920, which covers AEP-2920 on the classification of personal armour - the ballistic counterpart to AEP-2902's non-ballistic criteria, and a separate assessment entirely. Edition 3, 6 February 2019, supersedes STANAG 2902, Edition 2 (the source text names the prior edition but prints no date for it).
National responses on ratification and implementation are recorded in the NATO Standardization Document Database. The STANAG itself "is to be reviewed at least once every five years," with the result recorded in the NSDD, and "nations and NATO bodies may propose changes, at any time, through a standardization proposal to the tasking authority (TA)." The agreement is supervised under the authority of the NATO Army Armaments Group (NAAG), Land Capability Group on Dismounted Systems (LCGDSS), with the United Kingdom's Defence Science and Technology Laboratory (Dstl) named as custodian.
STANAG 2902 names no ballistic performance criterion of its own - that sits under STANAG 2920 and AEP-2920. It also names no test method, sample size or pass/fail threshold: those sit entirely in AEP-2902, which this agreement covers but does not reproduce. It also names no assessment or certification scheme: the only stated check is that the STANAG itself is reviewed periodically, not that a nation, an organisation or a helmet is certified.
STANAG 2902 itself gives a helmet manufacturer or supplier nothing to implement in software: it is an agreement between nations, and the test methods sit in AEP-2902. Where this reaches an organisation is through a tender or contract that invokes AEP-2902's testing regime for a specific helmet programme - and that work is physical, done on the bench and at a test facility, not in a compliance tool. ComplyTrain's usual footprint applies around it: holding the procedure describing how a helmet submission is prepared and which criteria a programme is being tested against, as a controlled document; the training record showing the people preparing it know the criteria they are working to; the design and test records held with their revision history; and the corrective-action trail if a result comes back short.
ComplyTrain does not test a helmet, does not decide which criteria or sample sizes apply to a programme, and does not certify a helmet, a manufacturer or a nation against this STANAG - NATO itself recognises no such certification. Our standards explorer shows what else sits alongside STANAG 2902, including AEP-2902 and the ballistic classification under STANAG 2920 - if you're weighing up what a tender or quality clause is actually asking of you, we're glad to talk it through.
Tell us how you need to work with STANAG 2902 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
Not on its own. A STANAG binds a nation once that nation has ratified and implemented it, and this cover names no manufacturer, supplier or test house at all. Whether it touches a given organisation is a question for the tender or contract in front of you, not for this page.
STANAG 2902 is the cover agreement: it commits nations to implement AEP-2902 but contains no test methods itself. AEP-2902, Edition A is the Allied Publication that sets out the actual non-ballistic test methods and evaluation criteria for combat helmets.
No. STANAG 2902 covers non-ballistic performance only. Ballistic performance is classified separately under STANAG 2920 and its Allied Publication, AEP-2920.
No. STANAG 2902 describes no certification or accreditation scheme. Its only stated check is a periodic review of the agreement's own currency, at least every five years, recorded in the NSDD. NATO does not certify a nation, an organisation or a product against a STANAG.
Edition 3, promulgated 6 February 2019, which supersedes STANAG 2902, Edition 2 (no date for that edition is printed in the source text).
One system for the whole compliance programme. Start with the module you need most.
Collect information the same way every time, and decide in advance what happens next.
Know whether your controls are operating, not just whether a policy says they exist.
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.