Platform
Modules
By sector
By sector
By standard
Blog
News
Events
APP-29
National authorising authorities deciding whether a visiting nation's helicopter can operate from a host nation's ship
APP-29 gives NATO national authorities a shared method and safety-margin dimensions for deciding whether a helicopter from one nation can land on or work from a ship of another.
APP-29 is a NATO Allied Procedural Publication, one of the technical documents in the AQAP/AEP/AMedP/APP family that carries the actual detail a covering agreement points to. Its subject is embarked aviation crossdeck clearance: the standardised method and safety-margin dimensions National Authorising Authorities use to decide whether a helicopter belonging to one nation can safely operate from a ship belonging to another. Nations record their agreement to use it in STANAG 1474, the covering document, and the current text is Edition A, Version 2, effective from 18 November 2024, superseding Version 1.
The document is explicit about what it is not. It "is not to be used for the design of flight decks," and says plainly that flight deck construction, aircraft maintenance and aircraft movements have not been considered, warning that using it for design purposes creates a danger to personnel and equipment. It is also written for a specific reader: the National Authorising Authorities on both sides of a crossdeck, the authority responsible for the ship and the authority responsible for the helicopter, not a designer, a shipbuilder, or a certification body.
APP-29 starts by defining the physical areas a clearance decision depends on. The Flight Deck is the area certified for take-off and landing: essentially flat, with holes restricted to approved link-plates or grids, essential obstructions capped at 0.01m (0.4in) and faired in, marked with solid white lines (yellow where snow is expected) at least 0.1m wide, lit at night, and built to a recognised classification society standard (IACS bodies such as ABS, Bureau Veritas, DNV GL or Lloyds Register) or an equivalent national ship construction standard. It must also be surfaced to the coefficient of friction that STANAG 1278 requires. The Aviation Deck carries the same obstruction and marking limits but may be swept by rotors during aviation activity around the Flight Deck.
The Approach Path and Departure Path are defined geometrically rather than by a fixed dimension: the approach path extends in rotor-diameter multiples either side of the approach line out to the hangar face, widening and rising over its outer length, with the upper boundary set by the national glide-path angle in use. Straight-in and oblique landings align the approach with the landing direction; lateral landings offset it to port or starboard.
Every calculation runs on a small set of pilot-accuracy figures. Landing Accuracy depends on the aircraft's weight and on whether the deck has a single or multiple landing spots: 2.44m (single spot) or 1.83m (multi spot) up to 5,400kg, rising to 3.05m or 2.44m above that weight. Flying Accuracy depends on main rotor diameter across four bands, from 3.05m/2.44m for rotors up to 12m, to 4.57m/3.66m for rotors over 17.01m. Heading Accuracy is a fixed 20 degrees regardless of spot type.
Those figures build four safety margins around the specific helicopter in question. The Main and Tail Rotor Swept Area (MTRSA) covers the area the rotors could traverse while positioning to land or departing after take-off, and caps obstructions at one eighth of the main rotor diameter or 1.5m, whichever is smaller, or requires half the combined widths as horizontal separation. The Fuselage and Tail Swept Area (FTSA), inside the MTRSA, caps obstructions at 0.61m. The Main and Tail Rotor Landing Area (MTRLA) takes over once the aircraft commits to its final descent, and caps obstructions at 0.11m. The Wheel/Skid Landing Area (W/SLA), where the undercarriage is expected to touch down, must sit entirely within the defined Flight Deck. Chapter 1 also sets a separate rotation datum for non-standard rotor arrangements, tandem-rotor and tilt-rotor aircraft, and is explicit that Pilot Accuracy and Flying Safety Margins for tilt-rotor aircraft have not been promulgated and are not to be used for V-22 matrix entries specifically.
Chapter 2 sets out two ways to fix the calculation's datum point. Without a Compatible Deck Securing System authorised on both aircraft and ship, the calculation runs against the full flight deck area, datum'd on the aircraft's Centre Main Rotor Head. Where both have an authorised Compatible Deck Securing System, the datum moves to that system's centre instead. The document also records a named exception: where the host nation's ship is already authorised to operate the visiting nation's aircraft type, the host nation's own national clearance criteria apply in place of the APP-29 calculation.
Running the calculation needs specific figures from both sides: ship flight deck length and width, the position and size of any deck-securing system, obstruction data, and the landing offset angle; and, for the aircraft, rotor diameters, the distance between rotor centres, and fuselage and undercarriage measurements out to the widest and furthest points. Annex A supplies blank data-collection templates for both sets of figures, and Chapter 2's later clauses (0203 to 0206) walk through the geometric construction of each safety area step by step.
Chapter 4 is where a calculation becomes a decision. National authorities first establish whether the helicopter can land (deck strength adequate, the W/SLA fitting within the flight deck when aligned with the MTRLA, and the MTRLA itself clear of obstructions when aligned with the FTSA) and whether it can approach to land (the MTRSA and FTSA fitting and clear of obstructions when aligned with each other). The outcome is then entered as a letter from a fixed legend, from full landing clearance through VERTREP-only or HIFR-only transfer, passenger transfer, or "Not Feasible," with any operating restriction noted and the entry dated. Where the assessment finds the combination unsuitable for landing, the document instructs the authority not to enter a code that permits landing, and to look instead at a VERTREP, winch-transfer or HIFR code, or "Not Feasible" if none of those apply.
NATO publishes APP-29 through the NATO Standardization Document Database at no charge. ComplyTrain does not sell it or host a copy; the NSDD listing for APP-29 is the source.
STANAG 1474 is the covering document that carries APP-29 into force. STANAG 1194, HOSTAC Publication MPP-02, holds the Ship/Aircraft Interoperability Matrix that an X-Ops Matrix entry ultimately feeds. STANAG 1162 covers VERTREP operating area marking, clearance and lighting, referenced for the VERTREP alternative when a landing code cannot be used. STANAG 1278 sets the coefficient-of-friction requirement the Flight and Aviation Deck surface must meet. MPP-02 itself, the HOSTAC interoperability matrix and briefing publication that APP-29 assumes throughout, sits outside our catalogue.
The clearance calculation itself, and the judgement of whether a particular helicopter can land on a particular ship, is a defence maritime aviation safety function carried out directly by the National Authorising Authorities the document names. It is not something a compliance platform performs, and ComplyTrain does not attempt to. Where ComplyTrain fits is around that activity: a controlled procedure for how your organisation prepares and submits ship or helicopter dimension data, training records for the people who measure or verify it, a place to log X-Ops Matrix entries and any national reservations that apply to your fleet as controlled records, and a defensible audit trail, who supplied what data, against which edition of APP-29, and when, if a customer or a national authority later asks how a clearance was reached.
ComplyTrain does not calculate a Landing Position, does not determine a Main and Tail Rotor Swept Area or any other safety margin, and does not decide whether a crossdeck is safe. Those determinations stay with the National Authorising Authorities named in the document. If your organisation needs to evidence its part in supplying data for an APP-29 assessment, talk to us about how the documentation and training side of that fits together, and see the standards explorer for what sits alongside APP-29 in a maritime aviation programme.
Tell us how you need to work with APP-29 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.
APP-29 binds through STANAG 1474, the agreement by which nations record their commitment to use it. Whether a particular organisation has to meet it depends on whether a national authority or a contract invokes the resulting procedure for a specific crossdeck, not on the document existing on its own.
STANAG 1474 is the covering agreement: it is how nations record that they will use APP-29, and it is not itself a technical specification. APP-29 is the technical document, the safety margins, dimensions and calculation method that STANAG 1474 covers.
No, not by itself. It gives National Authorising Authorities the method and the safety-margin figures to run that calculation for a specific ship and helicopter combination, and the outcome is recorded as an entry in the X-Ops Matrix under MPP-02. The determination is made by those authorities, not by the document.
No. The document states directly that flight deck construction, aircraft maintenance and aircraft movements have not been considered in it, and warns that using it for flight deck design creates a danger to personnel and equipment.
No. The document describes no accreditation scheme, no certifying body and no external assessor. The assessment it describes is run directly between the ship-operating and helicopter-operating nations' own authorities and recorded in the X-Ops Matrix.
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.