Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 4599
Defence suppliers whose contracts invoke NATO design safety and evaluation requirements for weapon launched grenade systems
STANAG 4599 is NATO's ratified agreement setting design safety requirements and a safety and suitability for service test programme for weapon launched grenade systems, carried in the STANAG's own annexes.
STANAG 4599 is a NATO Standardization Agreement, currently Edition 1, promulgated on 13 March 2007. It sets design safety requirements for weapon launched grenade systems and defines the standard tests that support evaluating their safety and suitability for service. Most STANAGs only ratify a separate Allied Publication and leave the technical content there; this one is different. It carries the design safety requirements and the assessment and test procedures directly in its own annexes, Annex A for design safety requirements, Annex B for assessments and Annex C for tests, so participating nations are agreeing to comply with what is in this document itself rather than in a publication it points to elsewhere.
In its own agreement clause, participating nations agree to comply with the design safety requirements and the safety and suitability for service evaluation procedures the STANAG sets out. A nation carrying out an evaluation of a grenade or launcher system also agrees to make its test parameters, safety analyses and trial reports available to other NATO nations that are considering buying or taking over that system, on receipt of a valid request, and to share the results of the design assessment and the safety and suitability for service evaluation in the same way. The subject is a weapon launched grenade: a fuzed munition with its own integral cartridge, fired from a launching device other than a service rifle, whether a hand-held low velocity launcher or an automatic grenade launcher.
The document draws its own line here, and it is worth stating precisely because the distinction is not simply which launcher is used. A grenade projected using the energy of a service rifle's own cartridge is a rifle launched grenade, and it is addressed by a different STANAG, 4520. A grenade with its own integral cartridge is a weapon launched grenade under this STANAG, and that includes one fired from a launching device attached to a rifle, such as an under-barrel launcher, not only one fired from a stand-alone launcher.
A STANAG binds a nation, not a company, once that nation ratifies it. This document is explicit about what counts as implementation: a nation has implemented STANAG 4599 once it has issued instructions to its services that all new weapon launched grenades procured for Service use will be designed, assessed and tested in accordance with the requirements and procedures it details. None of that reaches a supplier directly. It reaches a supplier once a national procurement authority puts design and qualification against this STANAG into a tender or a contract, which is the point where an agreement between nations becomes something a programme has to design to.
The grenade is assessed against the whole-system design safety requirements in Annex A, amplified by the developing nation where needed, using a hazard analysis conducted under AOP-15. Annex A sets those requirements at the level of categories rather than numeric values: the strength of the design under launch stresses, safe operation across the specified environments, compatibility between the materials used and the explosive content, protection against a single point of failure, in-flight stability, the launcher attachment, noise and blast, the feed and unloading mechanisms, and the firing mechanism, including the safety of any electro-explosive device and the fuze. The safety and suitability for service test programme is built from that design safety assessment, the hazard analysis and the environmental profile the grenade is expected to see across its life, packaged and unpackaged. Annex C groups its tests into environmental functioning and durability tests and safety tests and analyses, and names them individually: transportation and handling tests such as logistic and tactical vibration and shock; climatic tests such as temperature cycling, rain, salt fog, dust and sand, sealing and fluid contamination; free fall drop, underwater shock, parachute delivery and safety drop; reaction tests such as liquid fuel fire, slow heating, bullet and fragment attack and sympathetic reaction; fuze safety tests; electrical, electromagnetic, lightning and nuclear hardening tests; and range and functioning tests covering noise and blast overpressure, accuracy and initial functioning. Annex B adds a critical examination of components after environmental stressing and firing, and a range safety assessment. Severities are not to fall below what Annex C sets, though a nation may test more severely, and the hazard analysis behind the programme has to be broad enough to also support an Insensitive Munitions assessment under STANAG 4439 and AOP-39. The document separately distinguishes development testing, which may use a non-representative build of the grenade, from the safety and suitability for service tests, where the article under test has to be fully representative of the production build standard.
There is no certification an organisation can hold under this STANAG. Each participating nation's own national or service safety evaluation organisation is responsible for evaluating the design safety and the safety and suitability for service of the weapon launched grenades used by its own Services, working from a data package the developing nation compiles documenting the test methods, the rationale for the programme and the detailed results. The only accreditation the document names attaches to the test houses, ranges and authorities that produce that evidence, not to a supplier company or to the grenade as a certified product, and results are shared between NATO nations on a valid request rather than published against a fixed audit cycle.
The design safety assessment and test programme lean on a set of other NATO documents: AOP-15 for the hazard analysis and environmental life cycle method; STANAG 4170 for qualifying the explosives used; STANAG 4147 for material compatibility; STANAG 4439 and AOP-39 for insensitive munitions assessment; STANAG 4187 for the fuze's own design safety requirements; and STANAG 4157 with AOP-20 for fuze safety testing. Individual Annex C tests are tied to their own procedure standards: STANAG 4396 for sympathetic reaction, STANAG 4241 for bullet and fragment attack (alongside STANAG 4496, cited in this edition as not yet available), STANAG 4382 for slow heating and STANAG 4240 for liquid fuel fire, plus STANAG 4560 for electro-explosive device characterization and STANAG 4315 for whole life assessment, both cited in this edition as still being drafted. The wider environmental test methods come from AECTP-100, AECTP-300 and AECTP-400, with AECTP-500 named as related reading rather than invoked directly. AEP-22 and STANAG 4145 are named together only to define the effects considered in the nuclear hardening test. A further set of NATO environmental and munitions test-method standards appears in the document's own front matter as related reading, outside what is linked here.
STANAG 4599 governs an engineering and test discipline, not a document a company holds a certificate against. Designing to Annex A's requirements, running the hazard analysis, and carrying out the safety and suitability for service test programme is work done by the people designing, testing and evaluating the grenade system, not by software.
For that kind of work, ComplyTrain gives a programme one place to hold the design safety assessment and hazard analysis records, the test plans and reports it accumulates against this STANAG and the standards it relies on, the data package assembled for a national evaluation, and the corrective actions raised when a result comes back unsatisfactory. It does not perform the design safety assessment, run the hazard analysis, or carry out the safety and suitability for service tests, and it does not decide which related standards apply to a particular grenade programme. In defence, the applicable tier and the standards that come with it are set by the contract and the customer's quality clause. Use the standards explorer to see what sits alongside STANAG 4599, or talk to us about the programme you are building evidence for.
Tell us how you need to work with STANAG 4599 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 through ratification and, for a supplier, a contract. STANAG 4599 binds a nation once it ratifies the agreement and issues instructions to its services that new weapon launched grenades will be designed, assessed and tested against it; it reaches a supplier because a tender or contract requires that, not because the STANAG exists.
STANAG 4599 covers a weapon launched grenade, which carries its own integral cartridge and is fired from a launching device, including one attached to a rifle. STANAG 4520 covers a rifle launched grenade, which is projected using the energy of the rifle's own cartridge rather than a cartridge built into the grenade.
No. It describes a national evaluation, run by each participating nation's own safety evaluation organisation against the design safety requirements and test programme in the STANAG's own annexes, not a certificate a company can hold. The only accreditation named in the document belongs to the test houses and ranges that produce the test evidence.
Unlike many STANAGs, it is not in a separate Allied Publication. The design safety requirements sit in Annex A, the supporting assessments in Annex B, and the test procedures in Annex C, all part of this same document.
From NATO's Standardization Document Database, which lists the catalogue and serves the document free of charge. We do not sell it or host a copy.
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.