Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 1474
National authorities implementing NATO's embarked aviation cross deck clearance criteria, and naval aviation and shipboard organisations working to a tasking or contract that invokes APP-29
STANAG 1474 is NATO's agreement committing member nations to implement APP-29's clearance criteria for calculating Landing Position, so an embarked helicopter can safely operate from another nation's ship.
STANAG 1474 is a NATO Standardization Agreement, currently Edition 1, promulgated 18 January 2018. Like most STANAGs, it is not a technical specification in its own right. It is the agreement by which NATO nations commit to implement APP-29, Edition A, the Allied Publication that actually sets out the clearance criteria and the method for calculating a Landing Position when an embarked helicopter from one nation operates from another nation's ship. Read on its own, STANAG 1474 requires almost nothing of a supplier or operator directly: its obligations run to nations, and it reaches an aviation unit, a ship's company or a maintenance organisation only once a nation has implemented it and a national tasking or contract brings APP-29's requirements into play.
The stated aim is "to respond to the following interoperability requirements", and the document sets that requirement out as a plan: "To provide a methodology based on NATO-defined clearance criteria for the calculation of Landing Position", so that one nation's helicopter can operate safely from another nation's ship flight deck. Allied nations routinely embark and cross deck helicopters between each other's ships, which is why a common clearance methodology is an interoperability requirement rather than a purely internal safety matter for one navy. The document is careful to say this "does not replace nationally-defined safety or flight deck design criteria" - the two apply alongside each other, not one in place of the other.
STANAG 1474 is explicit that it binds nations, not suppliers or operators. 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)". Once ratified, the agreement "is effective upon receipt and ready to be used by the implementing nations and NATO bodies". Partner nations are separately invited to adopt it. So "is STANAG 1474 mandatory" has no single answer: it depends on whether a given nation has ratified and implemented it, and, for an aviation unit or ship's company, on whether a specific national tasking or contract then invokes APP-29.
STANAG 1474 is a short letter of promulgation, not a clause-numbered specification, so its content sits in named sections rather than numbered clauses.
Under "Agreement", participating nations agree to implement the standard named: APP-29, Edition A. No calculation formula, measurement apparatus or specific clearance threshold appears in the STANAG text itself; all of that, if it exists, is in APP-29, which this page does not hold the text of.
The one testable obligation this document states directly sits under "Implementation of the Agreement": the STANAG "may be considered implemented when nations have applied the criteria and procedures within APP-29 to their national HOSTAC information, and have provided any required changes to the Custodian (USA) of MPP-02.1.1." That names two things a nation actually does: apply APP-29's criteria to its own HOSTAC (Helicopter Operations from Ships Other Than Aircraft Carriers) information, and keep the US-held Ship/Aircraft Interoperability Matrix, MPP-02.1.1, current with any resulting changes.
The STANAG also lists related documents: STANAG 1162, on Vertical Replenishment (VERTREP) operating area marking, clearances and lighting; STANAG 1194, on Helicopter Operations from Ships Other Than Aircraft Carriers (HOSTAC); STANAG 1278, on the required level and measurement of coefficient of friction on flight decks; and SRD MPP-02.1.1, the Ship/Aircraft Interoperability Matrix and Advance National Information itself. The last of these sits outside NATO's own standards catalogue under its own reference code, named here with no link invented for it.
Nations are "invited to report on their effective implementation of the STANAG using the form in Annex H to AAP-03(J)." Partner nations, who adopt without the ratification obligation that binds a member nation, report separately, "using the form in Annex G to AAP-03(J)." The agreement itself "is to be reviewed at least once every three years", with the result recorded in the NSDD, and any nation or NATO body may propose a change at any time through a standardization proposal to the tasking authority.
Nobody can be certified against STANAG 1474 through this document: it names no accredited body, notified body or government-surveillance scheme. The only accountability it describes is national self-reporting - "The national decisions regarding the ratification and implementation of this STANAG are provided to the NSO" - plus the periodic review of the agreement itself. A nation applies APP-29's criteria to its own HOSTAC information and tells NATO it has done so; nobody audits that application from outside the chain of national command.
STANAG 1474 is a cover agreement, not a technical standard, and it obliges nations rather than suppliers or operators, so there is nothing in this document itself for an organisation to implement in software. The work is operational: applying APP-29's clearance criteria to calculate a Landing Position and confirm cross deck interoperability before an embarked helicopter operates from another nation's ship, done in flight planning and deck procedures, not in a compliance tool.
Where ComplyTrain fits is the paperwork trail behind whichever requirements a national tasking or contract actually invokes: documented procedures for cross deck clearance assessment, records of the national HOSTAC information reported against APP-29's criteria, training records for the aircrew and deck crew involved, and the evidence trail a national authority asks for when interoperability is questioned.
ComplyTrain does not calculate a Landing Position, assess a flight deck's clearance, or decide which criteria a specific tasking or contract carries. That work is done by the aircrew, the ship's company and the national authority concerned, working to whatever APP-29 and the tasking require. The applicable tier and which requirements a tasking or contract carries are set by the contract and the customer's quality clause, not by this page. Our standards explorer shows what else sits alongside STANAG 1474 and APP-29 - if you are weighing up what a defence programme actually requires, we're glad to talk it through.
Tell us how you need to work with STANAG 1474 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 aviation unit, a ship's company or a supplier only once a national tasking or contract invokes APP-29. Whether it applies to a given programme is a question for the tasking or contract, not for this page.
STANAG 1474 is the cover agreement: it commits nations to implement APP-29 but contains no clearance calculation detail itself. APP-29 is the Allied Publication that actually sets out the clearance criteria and the method for calculating a Landing Position.
The document states that implementation means nations have "applied the criteria and procedures within APP-29 to their national HOSTAC information, and have provided any required changes to the Custodian (USA) of MPP-02.1.1." The clearance calculation method itself is in APP-29, not in this cover agreement.
No. STANAG 1474 describes no certification or accreditation scheme. Nations report their own ratification and implementation decisions to the NSO, and the only other stated check is a periodic review of the agreement's own currency, at least once every three years. NATO does not certify organisations or products against a STANAG.
Partner nations are separately invited to adopt the STANAG and report their adoption using a different form, but adoption for a partner nation is voluntary rather than the ratification obligation that binds a member nation.
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.