Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AOP-39
National Authorities and the nations that ratify STANAG 4439, assessing and reporting how a munition responds to insensitive munitions threats
AOP-39 is NATO's policy for assessing how a munition responds to insensitive-munitions threats and reporting that response as an IM Signature a National Authority determines.
AOP-39 is the NATO Allied Ordnance Publication that sets the policy for introducing insensitive munitions (IM) into service and for assessing how a munition responds when exposed to an IM threat. It is covered by STANAG 4439: a nation that ratifies and implements that agreement agrees to introduce into service only munitions that are "as insensitive as reasonably practicable," and the document is explicit that the judgement on what counts as "reasonably practicable" is "a matter of national policy for each nation, based on legislation, capability requirements, defense priorities, and what is technologically achievable." AOP-39 itself never speaks to a company through a contract; it speaks to nations and, within them, to a National Authority.
The current edition, Edition E, deliberately covers less ground than earlier editions. It sets out what an IM assessment consists of - identifying the relevant threats, identifying the munition's configurations, assessing its response, and generating an IM Signature - and it sets the minimum response a munition configuration has to meet against six standardised threats (covering fire, prolonged heating, small-arms and fragment impact, shaped-charge attack, and sympathetic reaction from a neighbouring munition) to be considered IM Compliant. It does not itself set out the test methods for those six threats: that detail sits in six companion Allied Publications, one per threat. AOP-39 also touches munition and fuze design, in general terms, as something to consider from the earliest stages of development, but the composition and sensitivity data behind specific design techniques lives in its own technical annex rather than in this summary.
Force runs through ratification of STANAG 4439, not through AOP-39 existing on its own. A nation that ratifies commits to the "as insensitive as reasonably practicable" standard described above, and what that means in practice is left to national policy. AOP-39's own text notes that interoperability under this policy extends "within the Alliance and with Partner Nations," and the document's front matter shows that what actually applies can vary: specific nations record reservations against it, including Finland reserving the right to procure munitions that do not meet the standard's requirements where its resources do not stretch to the prescribed tests. A company meets AOP-39 when its own national authority, or a specific procurement requirement that authority sets, calls it up, not because the document addresses companies directly.
The document's own methodology statement is unusually direct about when this work happens: it applies "either at the earliest stage of design" just as much as to munitions already "improved, replenishment purchased, or older designs still in service." A Threat Hazard Assessment works out which threats a given munition configuration is likely to face and when. Where a threat is discounted, "it shall be justified and the rationale behind it shall be documented" - not as paperwork for its own sake, but because that record becomes "key evidence for any further IM assessment necessary when there has been an application or lifecycle change."
AOP-39 is also candid about the limits of full-scale testing on its own: a single test represents one response to one threat level, sample sizes are typically too small to be statistically meaningful, and a test alone rarely explains the underlying mechanism well enough to extrapolate from. So an assessment is expected to draw on a wider evidence base - test results at several scales, assessment by analogy to similar designs, modelling, and energetic-material characterisation - rather than a single full-scale test result standing in for the whole picture. Where full-scale testing is used, it follows one of the six threat-specific Allied Publications, and AOP-39 asks that it be coordinated with hazard classification testing under STANAG 4123 so the two programmes do not duplicate effort.
An IM Signature summarises a munition's response, in one configuration, to the threats relevant to it. Because a munition can exist in several configurations across its life, more than one signature may be needed, and each has to state clearly which configuration and which threats it covers. The Nation conducting the assessment collates and reports an IM Assessment Report that, at minimum, includes an executive summary, munition system information, the assessed configurations and threat ranges, the supporting evidence, and the IM Signature(s). It is the National Authority that makes the final call on the signature, and where its judgement does not follow what the primary evidence on its own would suggest, it has to record "technical justification for any primary evidence that was not a determining factor in the decision." AOP-39 draws a firm line here: "only IM Signatures approved by a National Authority shall be used" for interoperability purposes, and it warns that signatures "from independent test facilities, project teams, etc. may not be valid for this purpose." A test result and an approved signature are not the same thing, even when the same evidence sits behind both.
Edition E, promulgated June 2026, is a scope reduction rather than a change of policy. Detailed guidance that used to sit in AOP-39's own annexes - applying the hazard assessment protocols, and interpreting fast heating, slow heating, bullet impact, fragment impact, sympathetic reaction and shaped charge jet results - has moved to a new Systems Reference Document, AOP-4864.3. An annex that was only a list of the full-scale test STANAGs was dropped because that list now sits in AOP-39's own main body. Anyone who worked from Edition D should expect to follow those cross-references rather than find the detail still here.
AOP-39 is covered by STANAG 4439, the agreement nations ratify to bind themselves to it. For the test methods behind each threat it points to six companion publications: AOP-4240, AOP-4241, AOP-4382, AOP-4396, AOP-4496 and AOP-4526. It coordinates with STANAG 4123 for hazard classification, and treats identifying life cycle threats as tied to the Safety and Suitability for Service assessment under STANAG 4297 and AOP-15. Its design-focused annex also names a further set of NATO fuze and explosives standards, which the standards explorer lists alongside it.
AOP-39 sets policy and a reporting process; it hands the substance behind that process to the companion publications above. There is nothing here for software to implement directly, and the work the document actually describes - identifying threats, running or commissioning tests, determining an IM Signature - is done by National Authorities, test facilities and munition designers.
Where ComplyTrain's kind of work fits is the evidence trail an organisation supporting a NATO munitions programme has to hold: the documented rationale behind a Threat Hazard Assessment or an exemption decision, the procedures and sign-offs that show a design or packaging choice was considered against IM threats, training records for the people involved, and a clear version history connecting an assessment report to the change that triggered it. That is the same document control, controlled records and audit trail ComplyTrain provides for any compliance programme, not a mapping to AOP-39's own clauses.
What we do not do: run explosives tests, produce an IM Signature, or stand in for a National Authority or an accredited test facility. Which tier of this policy applies to a given programme, and which of its companion standards come with it, is set by the contract and the customer's quality clause, not by AOP-39 alone. See what sits alongside it in the standards explorer, and talk to us about the document control behind it.
Tell us how you need to work with AOP-39 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. It binds a nation once that nation ratifies STANAG 4439, and the document leaves the judgement on what "as insensitive as reasonably practicable" means to each nation's own policy. A company meets it when a national requirement or a specific contract calls it up, not because the document names companies directly.
It is a summary of how a munition, in a given configuration, responds to the insensitive munitions threats relevant to it. A munition can carry more than one signature if it exists in several configurations across its life, and the final signature for interoperability purposes has to be approved by a National Authority.
No. AOP-39 has no certification scheme, accreditation body or product certificate. The closest thing to an outcome is an IM Signature, and that is a technical judgement a National Authority reaches about one munition in one configuration, not a credential an organisation holds.
AOP-39 sets the policy and the minimum requirement; the six companion publications (AOP-4240, AOP-4241, AOP-4382, AOP-4396, AOP-4496 and AOP-4526) set out the actual test method for each of the six standardised threats. Reading AOP-39 alone will not tell you how a specific test is run.
Edition E narrowed AOP-39's scope. Detailed guidance on applying the hazard assessment protocols and on interpreting test results for each threat moved out of AOP-39's own annexes and into a new Systems Reference Document, AOP-4864.3, leaving AOP-39 to cover the policy and the reporting process itself.
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.