Platform
Modules
By sector
By sector
By standard
Blog
News
Events
ATP-3.3.4.2
NATO and national commanders and staffs, and the tanker and receiver aircrews who plan and conduct air-to-air refuelling
ATP-3.3.4.2 is NATO's tactical publication on air-to-air refuelling procedures for fixed-wing, helicopter and tilt-rotor aircraft, cleared nation to nation through Technical Compatibility Assessments rather than any organisational certificate.
ATP-3.3.4.2 is the NATO Allied Tactical Publication that gives NATO and national commanders and their staffs a common reference for planning and conducting air-to-air refuelling (AAR): the transfer of fuel from a tanker aircraft to a receiver aircraft in flight. It works through three aircraft categories in turn, each with its own chapter: fixed-wing AAR, helicopter AAR (HAAR), and tilt-rotor AAR (TAAR). Within each chapter the structure repeats: rendezvous and join-up, formation control, the refuelling procedures themselves, safety, and communications. The document is explicit about what it is for: it exists to promote interoperability, a shared understanding of national capabilities, and mutual AAR support and tactics development among the nations that use it, not to specify how tanker or receiver equipment is designed or built. Given how procedural the subject matter is, this page stays at the level of what the document governs, who it addresses, and how a nation and an aircraft type are cleared to work together, rather than the rendezvous geometry, timing, callsigns, radio calls or light signals it actually sets out.
ATP-3.3.4.2 addresses NATO and national commanders and staffs, who use it as a planning reference, and the tanker and receiver aircrews and formation commanders who carry out the procedures it describes. It reaches an aircrew through national implementation and mission tasking rather than by binding on its own: receiver units, or their command and tasking authority, identify the missions that require AAR and raise the request; tanker units respond; and AAR tasking is normally issued through an Air Tasking Order. Where a receiver's or a tanker's own national limitations are more restrictive than the baseline procedures the document sets out, the national limitation governs, and each side is responsible for bringing its restrictions to the other's attention before or during the mission.
Equipment compatibility works the same way, nation to nation rather than through a single central authority. Where a tanker nation and a receiver nation intend to refuel from each other, the nations involved run a Technical Compatibility Assessment as part of a clearance process, and probe and drogue couplings are built to dimensions established by STANAG 3447 so that equipment from different nations fits together. That clearance covers an aircraft type pairing and its equipment. It is not a certificate an organisation holds.
Chapter 1, General Procedures, sets the scope described above, states the applicability-of- limitations rule, and distinguishes peacetime employment, which calls for extensive pre-planning and coordination with air traffic authorities, from combat operations, which the document says plainly it is "not appropriate" to detail, beyond saying the peacetime principles should be applied whenever possible. It also names the refuelling equipment types in general terms, probe and drogue, boom, and boom-drogue adapter, without going into their settings or fuel flow figures.
Chapters 2 to 4 cover fixed-wing, helicopter and tilt-rotor AAR respectively, and mirror each other's structure closely. Formation control sits with the tanker commander, or the lead tanker in a multi-tanker formation, who is responsible for the control and safe navigation of the formation; wingmen and receivers are responsible for keeping the leader in contact, holding their briefed position, and advising the leader of unsafe conditions. Positive separation is a shared responsibility of every formation member, and the concept of MARSA (Military Assumes Responsibility for Separation of Aircraft) governs how a tanker/receiver formation is briefed when it transits a nation's airspace. Safety content covers rendezvous and joining safety, damaged-equipment and lost-contact handling, abort procedures, and a stated preference against routine AAR, including hose trail, over populated areas, to avoid exposing civilians and their property to hazard. A receiver aircraft commander is responsible for ensuring the aircraft's radar is not radiating and its weapons are safe ahead of a rendezvous. A helicopter is only to refuel from a drogue certified for helicopter-compatible airspeeds, and a tanker is directed not to extend an incompatible drogue during HAAR, which is a certification requirement on the equipment, not on an organisation. Communications content covers the classification and security of radio traffic, multi-tanker formation communications responsibility, and emission-control and radio-silent procedures; a jettisoned hose is logged and reported through a national Air Incident Report. None of the rendezvous timing, separation distances, altitudes, speeds or radio scripts these chapters set out are reproduced here.
Chapter 5, Additional Information, explains the Standards Related Document (SRD) mechanism. ATP-3.3.4.2 itself currently has four formal SRDs, and nations and organizations that conduct AAR are encouraged, though not required, to publish their own SRD recording procedures and caveats particular to them. National and organizational SRDs used to be kept as annexes to the ATP; they have since been moved out to let them be updated more often, and they no longer require ratification through the NATO Standardization Office.
ATP-3.3.4.2 describes no certification, inspection or audit scheme for an organisation. What functions instead is a clearance between nations: a Technical Compatibility Assessment, run as part of the clearance process by the tanker and receiver nations themselves, and equipment built to STANAG 3447's dimensions. That is a clearance for an aircraft type pairing and its equipment, not a certificate a company holds. Conformity day to day is shown by following the ATP's own procedures and each nation's SRD, and the one recorded outcome that reads like a compliance record is administrative: the position and time of a jettisoned hose is logged and reported through a national Air Incident Report. No accredited certification body, notified body or company-level audit scheme appears anywhere in the document.
ATP-3.3.4.2 is an operational and technical standard, not a management-system one: the work it governs, rendezvous, formation flying and the refuelling itself, happens in the cockpit and on the flight line, not in software. What benefits from a documented, auditable process are the records around that work: the Technical Compatibility Assessment and the clearance it produced for a given tanker/receiver pairing, the crew briefing and currency records that show an aircrew covered the mission's AAR briefing items before flight, a nation's or organization's own SRD held as a controlled document alongside the ATP, and the log of an incident, such as a jettisoned hose, reported through a national Air Incident Report.
ComplyTrain does not fly the aircraft, run a Technical Compatibility Assessment, or decide whether a piece of refuelling equipment is compatible with a given aircraft type. Which SRDs, clearances and procedures a given unit actually has to hold is set by national instructions and the tasking authority, not by this page. The standards explorer shows what else sits alongside ATP-3.3.4.2, and we are glad to talk through what a specific tasking is asking for.
Tell us how you need to work with ATP-3.3.4.2 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 is a reference document that reaches a nation and an aircrew through national implementation and mission tasking rather than by binding automatically on its own. Where a nation's own limitations are more restrictive than the document's baseline procedures, that nation's limitation governs its own aircraft.
Fixed-wing, helicopter and tilt-rotor tanker and receiver aircraft, each with its own dedicated chapter of rendezvous, formation, safety and communications procedures.
No. The document describes no certification scheme for an organisation. A tanker nation and a receiver nation intending to refuel from each other instead run a Technical Compatibility Assessment as part of a clearance process, and it is equipment, not an organisation, that the document ever describes as certified, such as a drogue certified for helicopter-compatible airspeeds.
A nation- or organization-specific supplementary document that records procedures and caveats beyond ATP-3.3.4.2's own baseline. Nations and organizations that conduct AAR are encouraged, not required, to publish one, and SRDs no longer require ratification through the NATO Standardization Office.
The document says directly that it is not appropriate to detail AAR operations under combat conditions. It states only that the peacetime procedures and principles should be applied whenever possible, with tankers kept clear of, or protected within, the combat zone.
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.