Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 1476
NATO nations and NATO bodies implementing technical and medical standards for submarine survival and escape
STANAG 1476 is NATO's agreement committing member nations to implement ANEP-86, the Allied publication covering technical and medical standards for submarine survival and escape.
STANAG 1476 is the NATO standardization agreement that gives force to ANEP/MNEP-86, Edition A, the Allied publication setting out technical and medical standards and requirements for submarine survival and escape. A STANAG is not itself a technical specification: it is the agreement by which NATO nations commit to implement one, and the actual requirements sit in the Allied Publication it covers. This STANAG responds to an interoperability requirement stated plainly in the document: "to set up the common basic aspects of technical and medical standards to ensure the minimum conditions for survival in a DISSUB while waiting for rescue or for escape if needed." Read plainly, that means the agreement exists so that a submariner's chances of survival and escape do not depend on which NATO nation built or crews the submarine, not so that a particular piece of equipment is bought to a single national standard.
This is Edition 1, promulgated 28 July 2014. It supersedes four earlier documents: STANAG 1301 (Edition 5), STANAG 1321 (Edition 3), STANAG 1469 (Edition 1), and part of STANAG 1320 (Edition 4).
The mechanism that matters here: a STANAG binds a nation, not a supplier. Nations "are invited to examine their ratification of the STANAG and, if they have not already done so, advise the NSO of their intention regarding its implementation," and the national decision is recorded in the NATO Standardization Document Database (NSDD). Once ratified, the agreement "is effective upon receipt and ready to be used by the implementing nations and NATO bodies." Partner nations "are invited to adopt this STANAG" on the same terms, without the ratification step that binds a participating nation. A shipyard, an equipment maker or a medical supplier meets ANEP-86 (or this STANAG) only where a contract or a tender brings it in by name, not because the agreement exists on its own.
Nations "are invited to report on its effective implementation of the STANAG using the form in Annex H to AAP-03(J)"; partner nations report their adoption of the STANAG the same way, using the form in Annex G to the same publication. The STANAG "is to be reviewed at least once every three years," with the result recorded in the NSDD, and nations or NATO bodies may propose changes at any time through a standardization proposal to the tasking authority.
The document in front of us is the agreement, not the standard. It names no depth limit, pressure limit, time limit or medical threshold for survival or escape: those figures, if the publication sets any, belong to ANEP-86 itself. Participating nations "agree to implement the following standard," named as "ANEP/MNEP-86, Edition A," and that is where the substantive technical and medical requirements live.
No certification exists here, and the document names none. What it describes is a national ratification, implementation and review cycle run through NATO's own machinery, not an audit against this STANAG as such. Whatever assessment a shipyard, a piece of escape equipment or a medical procedure actually faces would run against ANEP-86's own provisions and a national programme's or customer's quality clause, not against this document.
STANAG 1476 and ANEP-86 describe an operational and medical readiness requirement, not a management system: the work of preparing a submarine crew and its equipment for survival and escape sits in naval engineering, medical planning and crew training, not in software. What that leaves to evidence is the paperwork around it: procedures that correctly reference ANEP-86 and this STANAG, training records that show crews have been trained against the current edition, and the trail an internal or customer audit asks for afterwards.
ComplyTrain holds that evidence as a modern, auditable system: version-controlled procedures, training records tied to named individuals and dates, and corrective actions when a gap turns up, all searchable when a higher headquarters or a customer's quality clause asks for it. It does not design or test submarine escape or survival equipment, does not set or apply the medical or technical figures ANEP-86 contains, and does not replace the ratification and reporting nations carry out themselves through the NSDD and the AAP-03(J) forms.
The applicable tier here, and whatever else it comes with, is set by the contract and the customer's quality clause. If you are working out what sits alongside STANAG 1476, the standards explorer covers the related NATO maritime publications, and we are glad to talk through what that means in practice.
Tell us how you need to work with STANAG 1476 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 in general. It binds a nation once that nation ratifies it, and it reaches a supplier or a shipyard through a contract or a tender that names ANEP-86 or this STANAG, not by existing on its own. Whether it applies to a given programme is set by the tasking or contract in front of you.
STANAG 1476 is the agreement: the letter of promulgation, the ratification record, and the reporting and review machinery. ANEP/MNEP-86, Edition A is the publication itself, where the actual technical and medical survival and escape requirements live. The STANAG is the cover; ANEP-86 is the content.
Edition 1, promulgated 28 July 2014. It supersedes STANAG 1301 (Edition 5), STANAG 1321 (Edition 3), STANAG 1469 (Edition 1), and part of STANAG 1320 (Edition 4).
No. There is no accredited certification for STANAG 1476 or ANEP-86 to hold, and ComplyTrain does not claim one. What we support is the evidence trail around training and procedures for submarine survival and escape readiness, at an informational level.
At least once every three years, with the result recorded in the NATO Standardization Document Database. Nations and NATO bodies can also propose changes at any time through a standardization proposal to the tasking authority.
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.