Platform
Modules
By sector
By sector
By standard
Blog
News
Events
MPP-02.3.7
National task group command and planning staff arranging cross-deck operations between armed rotary wing aircraft and another nation's ship
MPP-02.3.7 is NATO's checklist of planning and operating considerations for armed rotary wing aircraft flying cross-deck to another nation's ship, agreed by nations under STANAG 1487.
MPP-02.3.7 is a NATO Multinational Procedural Publication (MPP) that supplements MPP-02, Volume I, Helicopter Operations From Ships Other Than Aircraft Carriers (HOSTAC), with "common planning and operating considerations for cross-deck operations with armed rotary wing aircraft of another nation". Nations agree to use its "Aide Memoire for planning operations with armed helicopters from another nation" rather than adopt a shared technical specification: the publication is a planning checklist, "designed to supplement individual nations planning processes to ensure operations with armed rotary wing aircraft are safe", not a set of engineering or flight requirements of its own. It is covered by STANAG 1487, the agreement by which NATO nations commit to use it.
Clause 0104's Aide Memoire works through sixteen planning considerations for a cross-deck operation, set out as questions rather than instructions, "designed to provide a common approach and assist the participating nations, conducting cross-deck operations, to prepare for the considerations of armed rotary wing aircraft". It prompts task group command and the two nations' planning staff to confirm, among other things: whether the operational need and its implications are understood at task group command level; how the carried explosive ordnance is classified, referencing the Hazard Classification Code in AASTP-3 and the Net Explosive Quantity in AAP-15; how the aircraft's own safety arrangements and the receiving ship's handling capability match up; the response planned for a hung weapon or an unauthorised discharge; and the fire-fighting and radiation-hazard considerations that follow from carrying ordnance and electro-explosive devices. It also asks whether deck teams, helicopter control officers and marshallers have been briefed on danger zones and their own responsibilities, whether the ship's approach and recovery geometry suit the aircraft's forward-firing arcs, whether the aircraft's weapon and ammunition standard operating procedures have been shared with the ship, and whether each nation's own approval process and a documented risk assessment cover the operation. MPP-02.3.7 does not answer these questions itself: it leaves the technical judgement on ordnance handling, arming, and flight profile to the two nations' own qualified personnel and command chain, and this page does not either.
The publication addresses "individual nations planning processes" and task group command, not a supplier or a manufacturer. It says nothing about who audits or certifies against it: "the procedures are based on a checklist format", completed and signed off within the participating nations' own process rather than assessed by any accredited or notified body. It sets no retention period for a completed checklist and no rule for what happens if a nation's answer to a consideration falls short; those are left to the nations involved.
MPP-02.3.7 is published by NATO and listed free of charge in the NATO Standardization Document Database. NATO's documents are not sold by ComplyTrain and we host no copies of them.
MPP-02.3.7 is an operational planning aid, not a management system, so there is no software mapping to claim against it. The actual work it describes, agreeing the sixteen-point checklist with a partner nation's task group, briefing deck teams and aircrew on danger zones and responsibilities, and signing off the risk assessment, happens on the flight deck, in the wardroom and at task group headquarters, not in ComplyTrain.
What ComplyTrain supports is the paperwork trail around that work: holding the completed checklist and risk assessment as a controlled, dated record; tracking which personnel have been briefed on which requirement, and when a briefing needs refreshing; and keeping the national approval-process documentation findable when a customer or a national authority asks to see it.
ComplyTrain does not classify explosive ordnance, judge an aircraft's safety arrangements, set a ship's recovery geometry, or advise on any flight or weapons-handling procedure. Those decisions stay with the participating nations' own qualified personnel and command chain, under whatever contract or tasking brought them together for the operation. See the standards explorer for what sits alongside MPP-02.3.7 and STANAG 1487, and talk to us about the evidence trail behind cross-deck planning.
Tell us how you need to work with MPP-02.3.7 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 by itself. Nations commit to using it by ratifying STANAG 1487, and a nation can ratify with reservations. Whether a particular cross-deck operation has to follow the checklist comes down to the national approval process and the contract or tasking for that deployment, not the existence of the publication.
STANAG 1487 is the agreement: the record of nations committing to use the publication. MPP-02.3.7 is the Allied Publication itself, the Aide Memoire and its sixteen-point planning checklist for cross-deck operations with armed rotary wing aircraft.
A checklist of planning considerations for flying armed rotary wing aircraft onto another nation's ship: ordnance classification, safety arrangements and handling capability, danger zones, landing and recovery geometry, and each nation's approval process and risk assessment. It does not itself specify arming procedures or flight profiles; those stay with the participating nations.
No such certification exists. MPP-02.3.7 names no certification body, notified body, or accredited scheme; it is a planning checklist that participating nations' own command and planning staff complete and sign off, not something assessed by a third party.
From the NATO Standardization Document Database, which lists it free of charge. NATO's documents are not sold by ComplyTrain and we do not host copies of them.
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.