Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 1162
Naval shipyards, ship operators and defence suppliers working to a contract or building specification that invokes MPP-02.3.3
STANAG 1162 is NATO's agreement committing member nations to implement MPP-02.3.3, the marking, clearance and lighting requirements for a ship's vertical replenishment operating area.
STANAG 1162 is a NATO Standardization Agreement, currently Edition 6, promulgated 11 March 2016. Like most STANAGs, it is not itself a technical specification. It is the agreement by which NATO nations commit to implement MPP-02.3.3, Edition A, the publication that sets the minimum requirements for marking, clearing and lighting a ship's Vertical Replenishment Operating Area (VOA), the deck area used to transfer cargo from a helicopter during vertical replenishment (VERTREP). The technical detail a reader usually wants sits inside MPP-02.3.3, not inside this short cover document. Read on its own, STANAG 1162 requires almost nothing of a shipyard or operator directly: its obligations run to nations, and it reaches a contractor only indirectly, once a nation has implemented it and a contract or building specification brings MPP-02.3.3 into play.
STANAG 1162 is explicit that it binds nations, not suppliers. 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), is promulgated herewith." Ratification and implementation are separate steps, and once ratified, the agreement "is effective upon receipt and ready to be used by the implementing nations and NATO bodies." So "is STANAG 1162 mandatory" has no single answer: it depends on whether a given nation has ratified and implemented it, and, for a shipyard or supplier, on whether a specific contract or building specification then invokes MPP-02.3.3.
The stated aim is "to respond to the following interoperability requirement," and the requirement itself is direct: "in the naval operational domain, to establish the minimum requirements for the marking and lighting of shipboard Vertical Replenishment Operating Areas (VOAs)." Under "Agreement," participating nations "agree to implement the following standard," named under "Standard" as "MPP-02.3.3, Edition A." STANAG 1162 goes no further than naming that publication; it sets out no dimension, colour or light characteristic of its own.
The STANAG lists four "other related documents" for context: STANAG 1194, covering helicopter operations from ships other than aircraft carriers (HOSTAC, MPP-02); STANAG 1236, on glide slope indicators for helicopter operations from ships (MPP-02.3.1); STANAG 1065, on replenishment at sea (ATP/MTP-16); and STANAG 3117, on aircraft marshalling signals (AFSP-2). None of these is stated as a prerequisite that must be in place first; they describe the wider naval replenishment and flight-deck picture that vertical replenishment operating area marking sits inside.
Nations examine their own ratification of the STANAG and, where they have not already done so, advise the NATO Standardization Office (NSO) of their implementation intentions; they later provide their actual implementation details to the NSO as well. Once promulgated, "STANAG 1162, Edition 6, is effective upon receipt and should be implemented by nations and NATO bodies as soon as possible after receipt." Nations are invited to report their effective implementation using the form at Annex H to AAP-03(J); partner nations, invited to adopt the STANAG without the ratification obligation that binds a member nation, report their adoption using the form at Annex G to AAP-03(J).
This edition, Edition 6, supersedes the previous Edition 5 of STANAG 1162. "This STANAG is to be reviewed at least once every three years. The result of the review is recorded within the NSDD," and any nation or NATO body may propose a change at any time through a standardization proposal to the tasking authority, processed at the next review. It is supervised under NATO's Military Committee Maritime Standardization Board (MCMSB).
STANAG 1162 names no certification or accreditation scheme, no assessment body and no audit of a shipyard, operator or product. The only accountability it describes is procedural: nations reporting their own ratification and implementation decisions to the NSO, and the periodic review of the agreement's own currency described above.
STANAG 1162 itself gives a shipyard or operator nothing to implement in software: it is an agreement between nations, and the marking, clearance and lighting detail sits in MPP-02.3.3. Where ComplyTrain fits is the paperwork trail behind whatever a specific contract or building specification actually calls up: documented procedures for how a vertical replenishment operating area is marked, cleared and lit, records of the inspections that confirm those markings meet the specification a contract invokes, and training records showing deck crew have been briefed on the layout and lighting they are working to.
ComplyTrain does not mark or light a vessel's deck, inspect a physical operating area, or decide which edition of MPP-02.3.3 a given contract requires - that work is done in the day-to-day handling by the shipyard, the operator and the nation concerned, working to whatever a specific contract requires. What applies to a specific programme is set by the contract and the customer's quality clause, not by this page. Our standards explorer shows what else sits alongside STANAG 1162 - if you are weighing up what a build or refit specification actually requires, we're glad to talk it through.
Tell us how you need to work with STANAG 1162 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 a shipyard or supplier only once a contract or building specification invokes MPP-02.3.3. Whether it applies to a given programme is a question for the contract, not for this page.
STANAG 1162 is the cover agreement: it commits nations to implement MPP-02.3.3 but contains no marking, clearance or lighting detail itself. MPP-02.3.3 is the publication that actually sets those minimum requirements for a ship's vertical replenishment operating area.
No. STANAG 1162 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.
Edition 6, promulgated 11 March 2016, is current. It supersedes the previous Edition 5 of STANAG 1162.
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.