Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 4670
Defence organisations running UAS or RPA training or operations under a NATO or national programme
STANAG 4670 is NATO's agreement committing member nations to implement ATP-3.3.8.1's minimum training requirements for UAS and RPA operators and pilots.
STANAG 4670 is the NATO standardization agreement covering minimum training requirements for unmanned aircraft system (UAS) and remotely piloted aircraft (RPA) operators and pilots. Like every STANAG, the agreement itself sets out no training content. "Participating nations agree to implement the following standard": ATP-3.3.8.1, Edition C. That publication is where the actual, testable training requirements live; this record covers the agreement, not that publication's content.
The aim, stated on the cover, is to "establish minimum training requirements for UAS operators and pilots that are or may become engaged in NATO operations", so that operator and pilot proficiency is standardised across nations working together.
A nation signs up to STANAG 4670 in two stages. First it ratifies the agreement, recorded in the NATO Standardization Documents Database (NSDD): "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." Second, once implemented, it reports the details of that implementation through NATO's electronic reporting tool. The agreement sets no NATO Effective Date of its own; it is effective upon receipt for use by the participating nations and NATO bodies, and it reaches an operator or a supplier once a national programme or a contract actually applies ATP-3.3.8.1, not at the moment NATO promulgates the agreement.
Nations are asked to "prioritize the requirements as described in ATP-3.3.8.1 Edition C Chapters 3 and 4", and, as applicable, to reference this agreement in their own national standards as a minimum requirement. Where able, it is also to be evaluated during NATO exercises that use UAS or RPAs.
This is Edition 6, dated 23 September 2025, and it supersedes STANAG 4670 Edition 5 of 8 May 2019. Review of the agreement follows the procedure set out in AAP-03, with the result recorded in the NSDD.
The agreement names no other related document, and it sets out no certification scheme: it creates a nation-to-nation reporting cycle through ratification and implementation records, not a scheme an organisation is assessed against. The training content itself, including the detail of what Chapters 3 and 4 of ATP-3.3.8.1 require, sits in that publication rather than in this agreement.
STANAG 4670 is an operational standard: the training it points to is delivered in the classroom, the simulator and the aircraft, not in software. What an organisation running UAS or RPA training can evidence is the paperwork around that delivery: instructor qualification records, syllabus version history tied to a specific edition of ATP-3.3.8.1, individual training and currency records for each operator and pilot, and the trail showing which requirements a given course was run against.
ComplyTrain holds those records under version control, tracks who has completed which training and when it falls due for renewal, and keeps the audit trail an assessor or a customer would ask to see. It does not deliver the flying, simulator or classroom training itself, and it does not decide which edition of ATP-3.3.8.1 a contract requires.
Which tier applies, and which other NATO publications come with it, is set by the contract and the customer's quality clause. The explorer shows what sits alongside STANAG 4670 and ATP-3.3.8.1 for a given programme. Talk to us if you need help working out what a specific contract is asking for.
Tell us how you need to work with STANAG 4670 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.
It binds a nation once that nation has ratified it, not an organisation directly. An organisation meets it because a national standard or a contract references ATP-3.3.8.1, the publication STANAG 4670 commits nations to implement.
STANAG 4670 is the agreement by which nations commit to implement a standard. ATP-3.3.8.1 is that standard: the Allied Tactical Publication that actually sets out the minimum training requirements for UAS and RPA operators and pilots.
No. The agreement names no certification scheme and no body that assesses an organisation against it. It sets up ratification and implementation reporting between nations and NATO; where an operator's training is checked, that happens under whichever national or contractual arrangement applies ATP-3.3.8.1.
Edition 6, dated 23 September 2025, supersedes Edition 5 of 8 May 2019. The agreement's own text does not itemise what changed between the two editions.
Nations are asked to prioritise the requirements in ATP-3.3.8.1 Edition C, Chapters 3 and 4.
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.