Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 4526
NATO nations implementing STANAG 4526, and defence munitions suppliers whose contract calls up the AOP-4526 test procedure it brings into force
STANAG 4526 is NATO's Edition 3 agreement committing member nations to AOP-4526, the Allied Ordnance Publication covering the shaped charge jet munition test procedure; it reaches a supplier only once a contract calls for it.
STANAG 4526 is the NATO Standardization Agreement covering the Shaped Charge Jet Munition Test Procedure. This is Edition 3, promulgated 20 November 2018, superseding the previous edition of the same STANAG; the document's own record of that earlier edition prints no date.
A STANAG is the agreement by which NATO nations commit to implement a standard, not the technical specification itself. STANAG 4526's own text is short and administrative: a single aim, one interoperability requirement, and the ratification, implementation, review and reporting machinery around it. The actual test procedure sits in a separate publication, AOP-4526, Edition A, which the STANAG names as the standard "participating nations agree to implement." Anyone actually running or evaluating that test procedure needs AOP-4526's own text - this page does not describe it.
The stated aim is "to respond to the following interoperability requirements," reduced in this STANAG to one: "to accept the Allied ordnance publication (AOP)-4526 which gives guidelines on the way an shaped charge, munition test shall be performed." Nothing beyond that single requirement is developed in the STANAG's own text.
STANAG 4526 binds nations, not suppliers. The document states it "has been ratified by member nations, as reflected in the NATO Standardization Document Database (NSDD), is promulgated herewith," and that it is "effective upon receipt and ready to be used by the implementing nations and NATO bodies." Partner nations are separately invited to adopt it. Implementation is a further, distinct step: a nation is considered to have implemented the agreement "when a nation has issued the necessary orders and instructions, putting the contents of this agreement into effect," and nations report both their ratification intentions and their implementation details back to the NATO Standardization Office, recorded in the NSDD. A supplier meets STANAG 4526, or the AOP-4526 test procedure it covers, only where a contract or tender says so - the document sets no obligation reaching a supplier directly.
The STANAG "is to be reviewed at least once every five years," with the result recorded in the NSDD. Any nation or NATO body may propose a change "at any time, through a standardization proposal to the tasking authority." That authority is the Conference of National Armaments Directors' Ammunition Safety Group (AC/326), Sub-Group B on Ammunition Systems Design and Assessment; the custodian nation is the United States.
STANAG 4526 names no certification or audit scheme, for a nation or for a supplier. What it describes is nations reporting to NATO: a ratification response, then a separate implementation report once the necessary national orders and instructions are in place, both recorded in the NSDD. The document does not describe a company as certified against STANAG 4526, and it never uses that language. Where a contract calls up AOP-4526's test procedure, whatever evidence a supplier has to produce follows from that contract's own quality clause, not from anything this STANAG specifies.
STANAG 4526 covers AOP-4526, the Allied Ordnance Publication that carries the actual test procedure. The document separately lists STANAG 4123 (classification of military ammunition and explosives) and STANAG 4439 with the AOP-39 insensitive-munitions policy it covers as related reading, and reviews of the STANAG itself run in accordance with AAP-03. It also names AASTP-3 and a United Nations manual on transport testing of dangerous goods among its related documents; neither is in our catalogue.
STANAG 4526 is two pages of ratification machinery; the work a defence contractor actually does sits in AOP-4526's test procedure, carried out in a test facility, not in software. What ComplyTrain does for that kind of work generally is give a supplier one auditable place to hold the controlled procedure for how a shaped charge jet munition test is planned, witnessed and recorded, the training records for the staff who run or oversee it, and the evidence trail - non-conformances, corrective actions, document control - that a customer's quality representative or a government surveillance visit will ask to see.
ComplyTrain does not perform a shaped charge jet munition test, determine whether a nation has ratified or implemented STANAG 4526, or decide whether AOP-4526's test procedure applies to a given programme. Those are questions for the tasking authority, the customer's contract, and whoever actually runs the test.
Which STANAGs and Allied Publications apply to a given programme is set by the contract and the customer's quality clause, not by us. Browse the explorer to see what sits alongside STANAG 4526 and AOP-4526, and talk to us about the evidence trail once you know which ones are in your contract.
Tell us how you need to work with STANAG 4526 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.
Only where a nation has ratified and implemented it, and it reaches a supplier only where a contract or tender invokes it. The document sets no NATO-wide date that starts an obligation on its own.
STANAG 4526 is the NATO ratification agreement; AOP-4526, Edition A is the publication that actually carries the shaped charge jet munition test procedure. Ratifying STANAG 4526 is how a nation commits to implement AOP-4526.
No. STANAG 4526 describes nations ratifying and reporting implementation to NATO, recorded in the NATO Standardization Document Database. It names no certification or audit scheme for a supplier, a product, or a test result.
Edition 3, promulgated 20 November 2018, which supersedes the previous edition of the same STANAG.
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.