Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3533
National flight safety aviation programme authorities implementing AFSP-05, and defence organisations operating under a national flight safety manual or contract that invokes it
STANAG 3533 is NATO's agreement committing member nations to implement AFSP-05, Edition B, the flight safety publication for flying and static displays, superseding the STANAG's 2013 edition.
STANAG 3533 is the NATO Standardization Agreement covering flying and static displays. This is Edition 10, promulgated 26 May 2025, and it states that it supersedes STANAG 3533, Edition 9, dated 28 October 2013.
A STANAG is the agreement by which NATO nations commit to implement a standard, not the technical specification itself. STANAG 3533's own text is short and administrative: an aim, an interoperability requirement, and the ratification, implementation and reporting machinery. The flight safety principles for flying and static displays themselves are specified in a separate publication, AFSP-05, which the STANAG names as the standard participating nations "agree to implement": "AFSP-05, Edition B." Anyone running or overseeing a flying or static display programme needs AFSP-05's own text, not this cover agreement.
The stated aim is interoperability: "To standardize within NATO nations the basic aviation flight safety principles that apply to the operation of all air weapons and platforms in use by NATO nations, irrelevant of the environment." The document ties this to mishap prevention rather than to display safety alone, so the STANAG sits inside NATO's wider aviation flight safety framework, with flying and static displays as its named subject. This edition carries one stated change over the last: "a paragraph has been added to cover the operation of unmanned aircraft systems (UAS)," which the previous edition did not carry.
STANAG 3533 binds nations, not suppliers or display organisers. It is effective "upon receipt for use by the participating nations and NATO bodies," and becomes binding on a given nation through ratification, which NATO records in the NATO Standardization Documents Database (NSDD). The STANAG sets out exactly when it counts as implemented: it is considered implemented "when all national authorities responsible for aviation/flight safety program have updated their flight safety manual to ensure that their procedures reflect the principles and general guidance set out in AFSP-05." To get there, a national flight safety aviation programme authority adopts AFSP-05 into its national flight safety manual (or uses it to complement or amplify an existing manual), updates its national programme to include AFSP-05's key principles, makes sure flight safety specialists and aviation personnel receive the update and can "act accordingly to the provisions of the standard," and makes the standard available to everyone involved in the aviation safety programme. Nations, and separately partner nations, then report implementation the way they report ratification: through the electronic reporting tool. An organisation meets STANAG 3533, or the AFSP-05 principles it covers, only where a national flight safety manual, a tender or a contract says so; the document itself sets no obligation reaching a supplier or a display organiser directly.
STANAG 3533 describes no certification scheme and no audit. What it describes is nations reporting their ratification and implementation status for the record, both "through the electronic reporting tool (e-Reporting)," with the review's result "recorded within the NSDD." Nobody, company or nation, is described as certified against STANAG 3533; whatever checking exists against the flight safety principles it covers happens inside a nation's own flight safety programme, under AFSP-05, not against this STANAG.
STANAG 3533 covers AFSP-05, the Allied publication that carries the actual flight safety principles for flying and static displays and the standard participating nations agree to implement. Its own review runs under AAP-03: "This STANAG is to be reviewed in accordance with AAP-03." The "Other Related Documents" clause it carries names none: it simply reads "None."
STANAG 3533 and the AFSP-05 principles it brings into force are followed inside a nation's flight safety programme and in the running of flying and static displays, not inside a compliance platform: a flight safety authority updates its manual and programme, trains its flight safety specialists and aviation personnel, and keeps the standard available to everyone involved. Where an organisation supports that programme, or holds a contract that references AFSP-05 or a national flight safety manual built on it, ComplyTrain helps hold the paperwork trail an assessor would ask for: the procedure that shows how the manual and programme were updated, the training records for flight safety specialists and aviation personnel, and the version history of the manual as it moves from one AFSP-05 edition to the next.
ComplyTrain does not run a flight safety programme, does not conduct or approve a flying or static display, and does not decide what AFSP-05 requires. That work happens in aviation flight safety administration and on the display itself, against the publication's own text and whatever a contract's quality clause demands.
Which STANAGs and Allied Publications actually apply to a given display or flight safety programme is set by the contract and the customer's quality clause, not by us. Browse the explorer to see what sits alongside STANAG 3533 and AFSP-05, 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 3533 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 or display organiser only where a national flight safety manual, a tender or a contract invokes it. STANAG 3533 binds the nations that ratify it, not suppliers or organisers directly.
STANAG 3533 is the NATO ratification agreement; AFSP-05, Edition B is the publication that actually carries the flight safety principles for flying and static displays. Ratifying STANAG 3533 is how a nation commits to implement AFSP-05.
No. STANAG 3533 describes nations ratifying the agreement and reporting implementation to NATO, recorded in the NATO Standardization Documents Database. It describes no certification or audit scheme for a supplier, an organiser or a product.
This edition supersedes STANAG 3533, Edition 9, dated 28 October 2013, and adds a paragraph covering the operation of unmanned aircraft systems that the previous edition did not carry. The document does not describe what that paragraph itself requires; that sits in AFSP-05.
No. STANAG 3533 is the ratification agreement; the flight safety principles for flying and static displays are set out in AFSP-05, Edition B, which is the document to consult for that content.
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.