Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 4703
NATO nations and the national airworthiness authorities that implement AEP-83 for light unmanned aircraft systems
STANAG 4703 is NATO's agreement by which member nations commit to implement AEP-83, the Allied publication setting light unmanned aircraft systems airworthiness requirements.
STANAG 4703 is the NATO standardization agreement that gives force to AEP-83, Edition C, the Allied engineering publication setting airworthiness requirements for light unmanned aerial systems. 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 use common standards for the production of airworthiness requirements for light unmanned aerial systems." Read plainly, that means the agreement exists so that NATO nations design and assess light unmanned aircraft against common airworthiness requirements, not so that a national scheme sets its own from scratch.
This is Edition 3, promulgated 24 October 2023. It supersedes STANAG 4703, Edition 2, dated 24 November 2016.
The mechanism that matters here: a STANAG binds a nation, not a manufacturer or operator. 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 ratification and implementation", and the national response is recorded in the NATO Standardization Document Database (NSDD). The STANAG "is effective upon receipt for use by the participating nations and NATO bodies", and it "is considered to be implemented when qualification and proficiency standards described in this standard are acknowledged and implemented into national regulations and manuals." A manufacturer or operator meets AEP-83 only where a contract, a tender or a national regulation brings it in by name, not because the STANAG exists on its own.
Allies and NATO bodies "shall provide implementation details through the electronic reporting tool", and partner nations are invited to provide theirs the same way. The document's own "OTHER RELATED DOCUMENTS" field reads "None." Its NATO Effective Date field reads "Not applicable", since the agreement takes effect on receipt rather than on a single fixed date. Its own review follows AAP-03. What it does not say is just as telling: it names no certifying body, and it does not describe an aircraft or a system being assessed. Whatever national airworthiness certification exists for a programme sits in a nation's own regulations once AEP-83 is folded into them, not in this text.
No certification exists here, and the document names none. What it describes is a national ratification, implementation and reporting cycle run through NATO's own machinery: nations record their ratification in the NSDD, acknowledge AEP-83's requirements into their own regulations and manuals, and report implementation through the electronic reporting tool. There is no accredited body, no notified body and no audit described against this STANAG as such.
STANAG 4703 and AEP-83 describe an airworthiness requirement for a physical aircraft system, not a management system: the engineering, design substantiation and airworthiness work that meets AEP-83 sits in aerospace engineering and national airworthiness regulation, not in software. What that leaves to evidence is the paperwork trail around it: procedures that correctly reference AEP-83 and this STANAG, records of which national regulation and edition a programme was assessed against, and the documentation an internal or customer audit, or a national authority, asks for afterwards.
ComplyTrain holds that evidence as a modern, auditable system: version-controlled procedures, records tied to named individuals, dates and programme identifiers, and corrective actions when a gap turns up, all searchable when a customer's quality clause or a national authority asks for it. It does not design, test or certify an aircraft, does not decide whether AEP-83 applies to a given programme, and does not replace the ratification, national implementation and reporting that nations carry out themselves through the NSDD.
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 4703, the standards explorer covers the related NATO airworthiness publications, and we are glad to talk through what that means in practice.
Tell us how you need to work with STANAG 4703 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 manufacturer or operator through a contract, a tender or a national regulation that names AEP-83 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 4703 is the agreement: the letter of promulgation, the ratification record, and the reporting and review machinery. AEP-83 is the publication itself, the Allied engineering publication that sets out the actual light unmanned aircraft airworthiness requirements. The STANAG is the cover; AEP-83 is the content.
Edition 3, promulgated 24 October 2023. It supersedes STANAG 4703, Edition 2, dated 24 November 2016.
No. There is no accredited certification for STANAG 4703 or AEP-83 to hold, and ComplyTrain does not claim one. What we support is the evidence trail around procedures and records for programmes working to AEP-83, at an informational level.
No, and the document does not say that either. It describes nations ratifying the agreement and folding AEP-83's requirements into their own regulations; any airworthiness certification of a specific aircraft is a national authority's action under those regulations, not something this STANAG or ComplyTrain awards.
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.