Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJP-3.3
NATO commanders and staffs planning and conducting air and space operations
AJP-3.3 is NATO's doctrine for how air and space capabilities are commanded, planned and employed in NATO joint operations; nations record their agreement to use it through STANAG 3700.
AJP-3.3, Allied Joint Doctrine for Air and Space Operations, is the Allied Joint Publication that explains how NATO organises, commands and employs air and space capabilities within a joint operation. The Preface names its audience directly: "AJP-3.3 is intended primarily as guidance for NATO commanders and staffs." Beyond that primary audience it offers itself more loosely: "the doctrine applies to, and provides a useful framework for, operations conducted by a coalition of mission participants", and "it also provides a reference for civilian mission participants". A framework and a reference are not obligations, so nothing here reads a requirement onto a coalition partner or a civilian actor, and the document does not address a supplier, manufacturer or any commercial role.
AJP-3.3 is doctrine, not a contract or a regulation, and it does not bind a company directly. NATO nations ratify a separate covering agreement, STANAG 3700: "The agreement of nations to use this publication is recorded in STANAG 3700." This edition, Edition C, Version 1 of February 2026, "is effective upon receipt and supersedes AJP-3.3, Edition B, Version 1". The promulgation letter directs that the superseded edition be destroyed "in accordance with the local procedure for the destruction of documents". A ratifying nation can also record a reservation against a specific provision at the time of promulgation; three did so in this edition. Where a company meets this world of doctrine in practice, it is normally through a level-3 publication that a contract or tender actually names, not through AJP-3.3 itself.
AJP-3.3 sits below two documents it draws on directly: it "reflects a clear linkage to the capstone publication AJP-01, Allied Joint Doctrine", and it "is subordinate to the keystone publication AJP-3", the Allied Joint Doctrine for the Conduct of Operations. As a level-2 publication it "sits at the top of air and space operations doctrine, with subordinate level-3 documents and tactical publications covering further details" - the AJP-3.3.x series on specific air missions, and the ATP-3.3.x series of tactical publications beneath those.
Chapter 1 sets out the fundamentals: the air domain, a working definition of air power, its three core attributes (speed, reach and height) and the further attributes they enable (ubiquity, agility, concentration), its limitations (impermanence, limited payload, vulnerability and cost), and air capabilities in outline, distinguishing manned aircraft, categorised by "generation", from unmanned aircraft, which the document classes by maximum take-off weight and states are to be operated "with appropriate levels of judgment and care" under "clear human responsibility".
Chapter 2, the most detailed in the document, sets out NATO's air command and control architecture: the principle of "centralised control and decentralised execution"; the roles of the Commander Allied Air Command, the Combined Force Air Component Commander and their responsibilities, the Combined Force Space Component Commander, and the Deputy Commander Air; the planning and tasking documents the structure produces, among them the air operations plan, the air operations directive, the airspace control plan and order, and the air tasking order; and the liaison elements that connect the air component to the rest of a joint force.
Chapter 3 introduces air power's four fundamental operational roles - control of the air, attack, air mobility, and intelligence, surveillance and reconnaissance - plus two further missions it discusses for their cross-cutting importance, electromagnetic warfare and support to personnel recovery. It defines the three recognised levels of control of the air, names the four functions air power depends on (base, sustain, connect, protect), and surveys employment options across the continuum of competition from reassurance activity through to warfighting, without prescribing tactics or targeting method.
Chapter 4 describes how a joint commander's direction becomes a published, executed and assessed air tasking order, and sets out planning considerations across supporting areas including air and missile defence, special operations forces integration, communications and information systems, electromagnetic operations, joint intelligence, surveillance and reconnaissance, unmanned aircraft systems, force protection, and the legal framework a commander operates within - the law of armed conflict, international human rights law, and rules of engagement, which "never limit an individual's right of self-defence".
Chapter 5 sets out NATO's approach to space as an operational domain: the segments of a space system, the domain's physical attributes and limitations, and the three functions - space domain awareness, operational space support, and space domain coordination - that structure NATO's space activity. It is explicit that "NATO neither owns nor directly operates any spacecraft", and that the capabilities it draws on come from national and, in places, commercial space systems, provided by Allies "on a voluntary basis".
Three annexes describe the standing NATO Command Structure air organisation, how a joint force air component headquarters is staffed and divided, and the ground-based and airborne command and control elements below headquarters level.
AJP-3.3 does not put a company, or a nation, through certification against it, and describes no scheme by which one could be. The nearest thing it describes is internal to a NATO operation: the final phase of the air tasking cycle is "the evaluation of the results of air operations", feeding lessons into the next planning cycle - an operational after-action review, not an audit of a supplier or contractor.
AJP-3.3 sets out doctrine, not testable technical requirements: it tells commanders and staffs how air and space capabilities are organised, commanded and employed, not what a supplier must deliver. It names commercial and national space systems only where NATO's own space capabilities depend on them, and says nothing about how a commercial provider is managed or evaluated. It does not itself set out the tactics, techniques and procedures for any specific mission; for those it points to the level-3 AJPs and the ATPs beneath it.
AJP-3.3 sits beneath AJP-01 and AJP-3, and draws on further Allied Joint Publications for detail on specific topics: AJP-5 for planning, AJP-2 and AJP-2.7 for intelligence and ISR, AJP-3.6 for electronic warfare, AJP-3.7 for personnel recovery, AJP-3.8 for CBRN defence, AJP-3.9 for joint targeting, AJP-3.11 for meteorological and oceanographic support, AJP-3.17 for geospatial support, AJP-3.19 for civil-military cooperation, and AJP-10 for strategic communications. Below it sit the level-3 AJPs on specific air missions - AJP-3.3.1, AJP-3.3.2 and AJP-3.3.3 - and the Allied Tactical Publications that carry the detailed procedures: ATP-3.3.2.1, ATP-3.3.3.1, ATP-3.3.4, ATP-3.3.5.1, ATP-3.3.6 and ATP-3.3.8.2, together with ALP-4.3 for air logistics.
AJP-3.3 is doctrine for NATO commanders and staffs, not a set of requirements addressed to a supplier, so there is no mapping between this document and a ComplyTrain feature to describe honestly. Where a defence contractor meets this world of doctrine in practice, it is usually through one of the level-3 or tactical publications AJP-3.3 points to, because a contract or a tender names one of those, or through the operational and space-support arrangements a NATO force runs under this doctrine. For that kind of contracted defence work, ComplyTrain gives an organisation a place to hold the documented procedures, training records and audit trail an assessor would ask for, and to keep them current as a contract's requirements change. It does not plan or command an air or space operation, staff a headquarters, or substitute for the judgement AJP-3.3 places with NATO commanders and their staffs; that work happens in a headquarters and in the field, not in software. Which standards and tiers actually apply to a given contract is set by that contract and the customer's quality clause, not by AJP-3.3 or by us. The standards explorer shows what sits alongside AJP-3.3 in the catalogue, including the publications referenced above; talk to us about how your documentation and evidence trail hold up against what a contract in this space is likely to ask for.
Tell us how you need to work with AJP-3.3 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.
AJP-3.3 itself is doctrine, not a rule a company can be bound by. NATO nations ratify their agreement to use it through STANAG 3700, so it binds a nation through that ratification, not through AJP-3.3 existing. It does not describe any mechanism by which a company is required to meet it; a company only meets this doctrine where a contract or tender cites a specific requirement from one of the subordinate publications beneath it.
STANAG 3700 is the agreement NATO nations ratify to use AJP-3.3; AJP-3.3 is the doctrinal content itself. The Letter of Promulgation states it plainly: "The agreement of nations to use this publication is recorded in STANAG 3700."
No. AJP-3.3 describes no certification scheme for organisations at all. The closest thing it names, the assessment phase of the air tasking cycle, evaluates the results of an air operation, not a supplier's compliance with anything.
Edition C, Version 1, published in February 2026 and promulgated on 11 February 2026, superseded Edition B, Version 1, which the promulgation letter directs be destroyed "in accordance with the local procedure for the destruction of documents".
AJP-3.3 is the level-2 publication for air and space operations; the AJP-3.3.x series beneath it (on counter-air operations, close air support and air interdiction, and air-maritime coordination) and the ATP-3.3.x tactical publications carry the detailed tactics, techniques and procedures that AJP-3.3 itself does not set out.
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.