Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3527
Defence organisations operating aircrew, UAS crews or air traffic control personnel under a NATO nation that has ratified STANAG 3527 or invokes AAMedP-1.11 in a contract
STANAG 3527 is NATO's ratification agreement committing member nations to implement AAMedP-1.11 Edition B, the Allied Medical Publication on fatigue management in air operations.
STANAG 3527 is the NATO Standardization Agreement on fatigue management in air operations. This is Edition 5, promulgated 20 May 2021, superseding "STANAG 3527, Edition 4, dated 27 February 2020".
A STANAG is the agreement by which NATO nations commit to implement a standard, not the technical specification itself. STANAG 3527's own text is short and administrative: an aim, one interoperability requirement, and the ratification, implementation and review machinery. The fatigue-management content itself lives in a separate publication, AAMedP-1.11 Edition B, which the STANAG names as the standard participating nations "agree to implement". Anyone working out what that content actually requires needs AAMedP-1.11's own text, not this cover agreement.
The stated aim is "to respond to" an interoperability requirement: "to standardize the maximum allowable flying hours and measures to provide for compulsory rest periods for aircrew taking into consideration aspects to perform special operations missions." The STANAG sets no figure of its own here; it names the topic and points to AAMedP-1.11 for the substance. Participating nations "agree to implement following standard", and the standard named is "AAMedP-1.11, Edition B". This edition also carries two changes noted in its promulgation letter: AAMedP-1.11 Edition B, Version 1 adjusted the responsibilities for sleep and alertness management, and a paragraph in the implementation section was changed by removing a reference to an EU norm and a US equivalent regulation.
STANAG 3527 binds nations, not suppliers. It is effective "upon receipt for use by the participating nations and NATO bodies", and it becomes binding on a given nation through ratification, which NATO records in the NATO Standardization Document Database (NSDD). Implementation is a separate, further step, and it is demonstrated operationally rather than on paper: AAMedP-1.11 "is considered implemented when the entity is able to track the number of flying or operating hours for aircrew" and equivalent personnel, monitor their performance, and take appropriate measures. Concretely, an entity needs a system to track flight or operating hours for the aircrew, UAS-operator and ATC-personnel populations the standard covers, a system to monitor those personnel's performance, and a way of carrying the standard's own flying-hour figure into the appropriate national regulation. Allied nations and NATO bodies are then obliged to report implementation details through NATO's electronic reporting tool; partner nations are only invited to do the same. A supplier meets STANAG 3527, or the AAMedP-1.11 content it covers, only where a contract or tender says so - the document itself sets no obligation reaching a supplier directly, and it names no NATO-wide effective date (its own "NATO Effective Date (NED)" field reads "Not applicable").
STANAG 3527 describes no certification scheme and no audit. What it describes is nations reporting their ratification and implementation status to NATO for the record; nobody is "STANAG 3527 certified", and the document never uses that language. Where an organisation's tracking and monitoring systems do get checked against AAMedP-1.11's requirements in practice, the assessor and the evidence required are set by the contract's own quality clause or a nation's own oversight arrangements, not by this STANAG.
STANAG 3527 covers AAMedP-1.11, the Allied Medical Publication that carries the actual fatigue-management content that participating nations agree to implement. Reviews of STANAG 3527 itself run under AAP-03. No other related documents are named.
STANAG 3527 and the AAMedP-1.11 content it covers are followed in day-to-day air operations, not in a compliance platform: a unit tracks flight and operating hours, monitors personnel performance, and carries the standard's provisions into national regulation and unit procedure.
What ComplyTrain does for that kind of work generally is give an organisation one auditable place to hold the procedures that describe how tracking and monitoring is carried out, the training records for the people running them, and the evidence trail - reviews, corrective actions, document control - that a command inspection or a customer's quality representative would ask to see.
ComplyTrain does not track flight or operating hours, monitor aircrew performance, or determine whether a unit meets AAMedP-1.11's requirements. That is operational air-safety and medical work, carried out under national regulation and the publication itself, not something a piece of software can do on an organisation's behalf.
Which STANAGs and Allied Publications actually apply to a given air operations programme is set by the contract and the customer's quality clause, not by us. Browse the explorer to see what sits alongside STANAG 3527 and AAMedP-1.11, 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 3527 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 STANAG's own "NATO Effective Date (NED)" field reads "Not applicable", so there is no blanket start date to point to.
STANAG 3527 is the NATO ratification agreement; AAMedP-1.11 Edition B is the publication that actually specifies the fatigue-management content. Ratifying STANAG 3527 is how a nation commits to implement AAMedP-1.11.
No. STANAG 3527 describes nations ratifying and reporting implementation to NATO, recorded in the NATO Standardization Document Database. It describes no certification or audit scheme for a supplier or a product.
The document states that this edition supersedes "STANAG 3527, Edition 4, dated 27 February 2020", and its promulgation letter notes that AAMedP-1.11 Edition B, Version 1 adjusted the responsibilities for sleep and alertness management, and that a paragraph in the implementation section was changed by removing a reference to an EU norm and a US equivalent regulation.
By tracking and monitoring, not paperwork alone: the document describes AAMedP-1.11 as implemented once an entity can track flight or operating hours for the relevant personnel, monitor their performance, and act on it, with the standard's own flying-hour figure carried into national regulation.
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.