Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 7234
National authorities implementing NATO airspace-integration procedures for military RPAS, and defence organisations working to a contract that invokes AATMP-51
STANAG 7234 is NATO's agreement committing member and partner nations to implement AATMP-51, the harmonized procedures for integrating military RPAS into shared airspace; it binds nations, not suppliers, directly.
STANAG 7234 is a NATO Standardization Agreement, currently Edition 1, dated 23 September 2019. It is not a technical specification. It is the agreement by which NATO nations commit to implement AATMP-51, Edition A, the Allied publication that sets out a harmonized set of procedures for integrating military remotely piloted aircraft systems (RPAS) into shared airspace. The actual integration procedures that a reader usually wants live inside AATMP-51 itself, not inside this six-page cover. Read on its own, STANAG 7234 requires almost nothing of a supplier or operator directly. Its obligations run to nations, and it reaches an organisation only indirectly, once a nation has implemented it and a contract or tender names AATMP-51.
STANAG 7234 is explicit that it binds nations rather than organisations. Its letter of promulgation describes the enclosed agreement as one "which has been ratified by member nations, as reflected in the NATO Standardization Document Database (NSDD), is promulgated herewith." Ratification and implementation are separate steps: the document invites nations that have not already done so to "advise the NSO of their intention regarding its ratification and implementation." So "is STANAG 7234 mandatory" has no single answer: it depends on whether a given nation has ratified and implemented it, and, for an organisation working with that nation's RPAS programme, on whether a specific contract invokes AATMP-51 as a result.
The stated aim is "to respond to the following interoperability requirements": "to establish a harmonized set of procedures among NATO nations for the safe and effective airspace integration of military RPAS, while respecting national sovereignty." The publication is further "intended to promote standardization and interoperability among NATO Member and Partner Nation RPAS operations." Under "Agreement," participating nations agree to implement AATMP-51, Edition A. None of this is written as a duty on a supplier or an operator; it is a duty on the nation.
A reader who only has STANAG 7234 in hand does not yet have a procedure to follow. The actual airspace-integration procedures are in AATMP-51. What this document does carry is a list of related publications that sit alongside it: STANAG 4586 on UA control system interfaces (covered by AEP-84), STANAG 4660 on the interoperable command and control data link for unmanned systems (covered by AEP-77), STANAG 4670 on minimum training requirements for UAS operators and pilots, STANAG 4671 on UAS airworthiness requirements (covered by AEP-4671), STANAG 4811 on sense-and-avoid guidance, STANAG 3531 on safety investigation and reporting of accidents and incidents (covered by AFSP-1.3), and the NATO UAS Human Systems Integration Guidebook. Each of these informs airspace integration; none of them is made binding by this STANAG itself.
Once implemented, "Allies and NATO bodies shall provide implementation details through the electronic reporting tool," while "Partner nations are invited to provide their implementation details" the same way - an invitation rather than a commitment for partner nations, and a distinction worth keeping straight. National ratification responses are recorded in the NSDD. The STANAG itself "is to be reviewed in accordance with AAP-03. The result of the review is to be recorded within the NSDD" - a check on whether the agreement is still current, not an audit of any organisation. It is supervised by NATO's AVC, ATM-CNS AG and ATOMI WG committee chain.
STANAG 7234 names no specific integration procedure, sense-and-avoid criterion or training standard of its own - that detail sits in AATMP-51 and the publications listed above. It also names no assessment or certification scheme: the only stated check is that the STANAG itself is reviewed periodically, not that an organisation, an aircraft or a procedure is certified.
STANAG 7234 itself gives an organisation nothing to implement in software: it is an agreement between nations, and the substance sits in AATMP-51 and the publications around it. Where ComplyTrain fits is the paperwork trail behind whatever a contract actually invokes: the procedure that documents how airspace integration is carried out for a given platform or mission, the training records that show crews were trained against it, and the corrective-action or incident record when a sense-and-avoid or safety-reporting STANAG is engaged.
ComplyTrain does not fly the aircraft, integrate it into shared airspace, or decide whether a nation has ratified this STANAG - that work and that decision sit with the operator and the government bodies concerned. What applies to a specific programme is set by the contract and the customer's quality clause, not by this page. Our standards explorer shows what else sits alongside STANAG 7234 - if you are weighing up what a tender actually requires, we're glad to talk it through.
Tell us how you need to work with STANAG 7234 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 on its own. A STANAG binds a nation once that nation has ratified and implemented it, and it reaches an organisation only when a contract or tender names AATMP-51. Whether it applies to a given programme is a question for the contract, not for this page.
STANAG 7234 is the cover agreement: it commits nations to implement AATMP-51 but contains no airspace-integration procedure itself. AATMP-51 is the Allied publication that actually sets out the harmonized procedures for integrating military RPAS into shared airspace.
No. STANAG 7234 describes no certification or accreditation scheme. Its only stated check is a periodic review of the agreement itself, in accordance with AAP-03. NATO does not certify organisations or aircraft against a STANAG.
Edition 1, dated 23 September 2019. The document states plainly that it "does not supersede any document," so this is the first edition.
Partner nations are separately "invited to provide their implementation details" through the same reporting tool, but that is an invitation rather than the ratification commitment member nations make.
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.
A 90-day plan for the smallest defence suppliers: let the tender set your scope, document what you already do, fix the security basics primes check, and keep the system small enough for two people to maintain.
Learn how to qualify, approve and monitor sub-suppliers, flow down requirements through purchase orders, and keep the records an auditor will ask to see under ISO 9001 clause 8.4 and AQAP.
Learn how to run an ISO 9001 Clause 9.3 management review that turns evidence into decisions, with the right inputs, actionable outputs, and a cadence that fits your risks.