Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 1487
Naval aviation and shipboard planning staff in NATO and partner nations that ratify or adopt STANAG 1487 for armed-helicopter cross-deck operations
STANAG 1487 is NATO's agreement for nations to adopt MPP-02.3.7 as their shared planning reference for armed-helicopter cross-deck operations; it binds nations, not suppliers directly.
STANAG 1487 is a NATO Standardization Agreement covering common planning and operating considerations for cross-deck operations with armed rotary wing aircraft. It exists to respond to an interoperability requirement stated "in the naval operational domain, to enable multinational armed rotary wing cross-deck operations by establishing common planning and operation considerations."
Like every STANAG, this one is an agreement between nations, not a technical manual in itself. The actual planning considerations live in a separate Allied Publication, MPP-02.3.7 Edition A, and participating nations agree to implement that publication rather than a set of clauses printed here. A STANAG binds the nation that ratifies it; it reaches a supplier, operator or contractor only when a contract, tender or operating order invokes STANAG 1487 or the MPP-02.3.7 publication it covers.
For a nation that has ratified it, the agreement is effective on receipt and ready to be used by implementing nations and NATO bodies. Partner nations are invited to adopt it rather than ratify it, which is a genuinely different, non-binding step. The agreement is considered implemented once a nation adopts MPP-02.3.7 as an aide memoire for planning HOSTAC operations with armed helicopters from another nation, and nations report that adoption to the NATO Standardization Office using the forms in Annex H (nations) and Annex G (partner nations) to AAP-03(J). Ratification and implementation decisions are recorded in the NATO Standardization Document Database.
This is Edition 1, dated 21 March 2018, and it does not supersede any prior document. It is reviewed at least once every three years, and any nation or NATO body can propose a change through the tasking authority at any time. What it does not contain is a clause-by-clause planning procedure: that content sits in MPP-02.3.7, a separate publication. Anyone looking for the actual cross-deck planning steps needs that publication, not this agreement.
The planning work this STANAG points to belongs to the in-service, operational phase of a cross-deck evolution, once a ship and an embarked or visiting helicopter are already in service. It has nothing to do with the design, production or acceptance of either the aircraft or the ship.
implement; it is the whole substance behind this cover agreement.
from ships other than aircraft carriers) that this STANAG's cross-deck planning considerations sit inside.
use to report their ratification and adoption.
Nothing in STANAG 1487 sets out an accreditation or certification scheme. Nations report their own ratification and implementation status to the NATO Standardization Office, and that status is recorded in NATO's own database, not assessed by an accredited body or a third-party auditor. The work this agreement points to happens on the flight deck and in the planning room, briefing the common planning considerations before a cross-deck evolution, not in software.
That is where ComplyTrain fits: holding the procedure that reflects a unit's or supplier's adopted planning considerations, keeping the aircrew and flight-deck team training and briefing records that show people were current on it, and keeping the evidence of which considerations were followed for a given exercise or deployment, ready for a command or customer to review afterward.
ComplyTrain does not plan or fly a cross-deck evolution, and it is not a substitute for MPP-02.3.7 as the aide memoire aircrew use in the moment. The applicable tier, and which STANAGs a contract actually requires, is set by the contract and the customer's quality clause. Our standards explorer shows what sits alongside STANAG 1487, and we are glad to talk through how a unit or supplier evidences the planning work it already does.
Tell us how you need to work with STANAG 1487 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.
Only for the nations that ratify it, and only in the sense that a ratified STANAG commits a nation to implement it domestically. For a supplier or operator, STANAG 1487 has force only when a contract, tender or operating order names it or the MPP-02.3.7 publication it covers.
STANAG 1487 is the agreement by which nations commit to adopt MPP-02.3.7 as their common reference for cross-deck planning. MPP-02.3.7 is the Allied Publication that actually carries the planning considerations; the STANAG itself does not.
No. The document describes a national reporting loop to the NATO Standardization Office, recorded in NATO's own database. It sets out no accreditation, notified-body or certification scheme, and NATO does not certify suppliers or organisations against a STANAG.
HOSTAC (Helicopter Operations from Ships Other Than Aircraft Carriers) is the broader framework named in STANAG 1194, which STANAG 1487's cross-deck planning considerations sit inside. STANAG 1487 covers the specific case of armed rotary wing aircraft.
The agreement is reviewed at least once every three years, and any nation or NATO body can propose a change to the tasking authority at any time, for processing at the next review.
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.