Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3526
NATO nations and NATO bodies implementing common medical categories for aircrew
STANAG 3526 is NATO's agreement bringing AAMedP-1.10 into force, under which ratifying nations align their own doctrine and set up a system to track aircrew medical examinations.
STANAG 3526 is the NATO standardization agreement that brings AAMedP-1.10, Edition B into force among the nations that ratify it. It is not itself a medical specification: the categories and criteria live in AAMedP-1.10, and this agreement is the mechanism by which NATO nations commit to apply them. This page covers the agreement; a separate page covers AAMedP-1.10 itself.
Aircrew move between NATO nations, on exchange postings, in multinational units and on NATO missions. Each nation runs its own medical categorisation system for its own aircrew, so without a shared reference a category assigned by one air force means nothing to another. STANAG 3526 exists "to establish the medical procedures for the exchange and assignment of aircrews among NATO nations," and it encourages nations to exchange the medical information behind that categorisation, particularly with the aircrew member's new home base clinic.
Under the agreement, "participating nations agree to implement" AAMedP-1.10, Edition B as the standard that actually carries the medical categories. Ratification and implementation are recorded separately: national ratification positions sit in the NATO Standardization Document Database (NSDD), and a nation that has not yet advised NATO of its position is invited to do so. Implementation is a distinct, later step, and the document is specific about what it consists of. Two things have to be true: the nation has "updated the content of the national doctrine, regulation and procedures in accordance with its provisions," and "there is put in place a system to record and track medical examinations and tests for the subject personnel." Both are reported back to NATO through the electronic reporting tool. This edition carries no NATO Effective Date of its own.
This is the ninth edition of STANAG 3526, promulgated 26 March 2021. It supersedes the eighth edition, dated 8 December 2017.
There is no certification here. No accredited body, notified body or NATO inspector audits a nation's aircrew medical programme against this STANAG. What exists is self-reporting: a nation (or NATO body) records its own ratification and, separately, its own implementation through NATO's electronic reporting tool, and the NSDD holds the resulting record. The STANAG itself is reviewed in accordance with AAP-03, with the outcome again recorded in the NSDD. For a supplier or contracted organisation, this STANAG has no direct force; it binds nations and NATO bodies, and reaches anyone else only where a contract or a national instruction points at the medical categorisation system it brings into force.
STANAG 3526's own "Other related documents" list names STANAG 3114 (aeromedical training of flight personnel) and the NATO E-3A Component Flight Surgeon's Manual as related reading, not binding requirements of this agreement. STANAG 3114 covers training rather than categorisation, and the Flight Surgeon's Manual is outside our catalogue. The STANAG is reviewed against AAP-03, NATO's standardization procedures document. The standard it brings into force is AAMedP-1.10.
The work STANAG 3526 describes happens in national doctrine and in a nation's own medical record-keeping, not in software, and ComplyTrain does not perform aircrew medical examinations or replace a nation's medical record system. What an organisation working against AAMedP-1.10 under this STANAG has to show is that its doctrine and procedures were actually updated to match it, and that a working system for recording and tracking the underlying medical examinations exists and is used. That is evidence: a controlled procedure document, a record of who reviewed and approved the update, training records for the people who have to follow it, and a corrective-action log where an examination or a record falls behind. ComplyTrain holds that evidence trail - the controlled documents, the approvals, the training records, the audit findings - for whichever standard a contract or a national instruction points at.
Which standards apply to a given contract, and on what tier, is set by the contract and the customer's quality clause, not by us. If you are working out what sits alongside STANAG 3526 for a given programme, the standards explorer is the place to look, and we are glad to talk through what evidencing it in practice involves.
Tell us how you need to work with STANAG 3526 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 by itself. It binds a NATO nation once that nation has ratified and implemented it, and it reaches a supplier or contracted organisation only where a contract or tender names AAMedP-1.10 or the medical categorisation system it brings into force.
It is the Allied Medical Publication that STANAG 3526 brings into force, and it is where the actual aircrew medical categories and criteria are set out. This page covers the STANAG that puts AAMedP-1.10 into effect, not AAMedP-1.10's medical content itself.
This is Edition 9, promulgated 26 March 2021, superseding Edition 8 of 8 December 2017. The document in front of us does not itemise what changed between the two editions.
No. Implementation is reported by nations and NATO bodies through NATO's own electronic reporting tool and recorded in the NATO Standardization Document Database. No accredited body, notified body or third party certifies a nation, or a company, against this STANAG.
The agreement binds NATO nations and NATO bodies, not companies. It reaches a supplier indirectly, through a contract or national instruction that invokes AAMedP-1.10 or the aircrew medical categorisation it establishes.
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.