Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AAMedP-1.17
National authorities and aircrew equipment programmes that specify or select immersion protection assemblies for aircrew
AAMedP-1.17 sets NATO's minimum requirements for immersion protection assemblies for aircrew, and a method for working out how much protection one needs; it binds participating nations, not suppliers directly, and names no certification scheme.
AAMedP-1.17 is a short NATO Allied Aeromedical Publication: two chapters that state why immersion protection assemblies for aircrew exist and set the minimum requirements they must meet. Its aim, in its own words, is "to establish the minimum requirements for immersion protection assemblies for aircrew." Edition A, Version 1 was promulgated in November 2018; the record does not show it superseding an earlier edition.
This is a technical requirements document written in physiological terms, not a design specification for a reader to copy figures from. This page describes what it covers at that level; it does not reproduce the specific figures the document works through, because a supplier acting on a number pulled out of context, without the document, its graph and the operating assumptions behind them, would be acting on the wrong basis.
The document explains the risk plainly: aircrew who end up in water face hypothermia, and an immersion protection assembly is meant to reduce that risk by cutting heat loss and reducing the chance of cold shock and swimming failure. It sets a deliberately cautious baseline assumption - that a survivor may have no life-raft available and may need to stay immersed until rescued, rather than assuming rescue aids will always be to hand.
It also names a trade-off rather than hiding it: more protection against cold immersion adds thermal load the wearer carries before ever entering the water, and an assembly has to work alongside other worn equipment, life-preservers named specifically. The document groups that compatibility requirement with "other subsidiary requirements" it says are "not considered here."
Rather than fixing one figure for every situation, AAMedP-1.17 sets out a method. An organisation estimates how long rescue is realistically likely to take, for the location, season and search-and-rescue capability in question, and uses that estimate to determine the level of protection an assembly needs to provide, then selects an assembly whose measured performance meets or exceeds it.
The document is careful about which estimate to use: the likely rescue time for the great majority of cases, not the longest theoretically possible one, because designing for the extreme case would demand a level of protection that is difficult to achieve and rarely needed. It also recognises that in adverse circumstances, particularly in wartime, rescue may take longer than any assembly alone can cover; in that case the direction is to wear the maximum protection that stays compatible with reasonable thermal comfort in the aircraft, and treat the achievable rescue time as the resulting constraint. Water leaking into an assembly is treated as a serious defect in its own right, because it produces a marked loss of the protection the assembly was selected to provide.
None of the document's own figures behind that estimate are reproduced on this page. What matters to a reader is the method: an estimate of the operating context comes first, and the assembly selected has to match what that estimate requires.
One nation recorded a reservation against this edition: Slovenia noted that it does not use assemblies specified in the document. A recorded reservation is normal for a NATO agreement - it changes what that nation itself uses, not the document.
AAMedP-1.17's own agreement clause states that "Participating nations agree that immersion protection assemblies for aircrew shall meet the minimum requirements detailed in this NATO standard." The publication is covered by STANAG 3981, the NATO instrument through which nations record commitment to publications of this kind; the STANAG carries the commitment, the AAMedP carries the technical detail. Neither obliges a supplier directly - the trigger for a supplier is a national requirement or a contract for aircrew survival equipment that names this standard, not the document existing on its own.
AAMedP-1.17 describes no certification, government-surveillance or notified-body scheme, and no organisation can be "AAMedP-1.17 certified." What it describes is a selection method: whoever specifies equipment for a nation works out the required level of protection for a given aircrew role and operating area, then selects an assembly whose measured performance meets it. The document does not say who verifies that a specific assembly's measured performance matches what its manufacturer claims; that sits with each nation's own procurement and test arrangements, not with anything AAMedP-1.17 establishes.
AAMedP-1.17 is covered by STANAG 3981, the NATO agreement recording participating nations' commitment to publications of this kind - the cover that gives it force. The text we read names no other standard directly.
AAMedP-1.17 is a technical requirements document about physical survival equipment, not a management system, so ComplyTrain does not implement it the way it would ISO 9001 or AQAP-2110. Working out the required level of protection for a given aircrew role and operating area, and the physical performance testing behind it, is done by the people and test facilities doing that work, not by software.
What ComplyTrain supports is the record-keeping around that decision: the procedure an organisation follows for specifying or selecting an immersion protection assembly, the record of which assembly was chosen for a given role or contract and the reasoning behind it, and the training record for whoever makes that call. It does not calculate a required level of protection, measure an assembly's performance, or select the equipment itself, and it does not replace a nation's own procurement or test arrangements.
What applies to a specific contract or aircrew role is set by the customer's requirement and the quality clause in the contract, not by this page. The standards explorer shows the STANAGs and Allied Publications AAMedP-1.17 sits alongside, and we are glad to talk through what a specific contract actually asks you to evidence.
Tell us how you need to work with AAMedP-1.17 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.
It binds through the agreement participating nations record in clause 1.2, and is covered by STANAG 3981. That is an agreement between NATO nations, not a requirement placed directly on a supplier; a nation can record a reservation against it, as Slovenia has for this edition, and a supplier meets it only when a national requirement or contract names it.
No. The document names no certification scheme. It sets minimum requirements for an assembly's performance and a method for working out what that performance needs to be for a given role and area; verifying a specific assembly's measured performance is left to each nation's own procurement and test arrangements.
STANAG 3981 is the NATO agreement recording participating nations' commitment to publications of this kind; it is the cover that gives AAMedP-1.17 its force. AAMedP-1.17 is the publication itself, the document that sets the minimum requirements and the method for working out an assembly's required level of protection.
No, not on this page. The document works through an estimation method using operating-context factors that only make sense read together with its own graph and assumptions; reproducing a figure out of that context risks it being read as a specification or survival guidance, which it is not intended to be here.
No. Nations can record reservations, and Slovenia has done so for this edition, noting it does not use the assemblies the document specifies. The requirement is set through agreement among participating nations, not enforced identically in every case.
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.