Platform
Modules
By sector
By sector
By standard
Blog
News
Events
ANEP-83
Naval engineering authorities, shipyards and harpoon designers in NATO nations that build or fit a shipborne helicopter or UAV harpoon-grid securing system, under the agreement recorded in STANAG 1276
ANEP-83 sets NATO's mandatory harpoon and grid interface dimensions, tolerances and mechanical characteristics for securing a helicopter or a VTOL UAV to a ship's flight deck, and it binds nations through the agreement recorded in STANAG 1276.
ANEP-83, printed on its own cover as ANEP/MNEP-83, is a NATO Allied/Multinational Naval Engineering Publication: the technical document that fixes the mandatory mechanical characteristics of the harpoon-grid rapid securing system used to hold a helicopter or a VTOL UAV to a ship's flight deck immediately after touchdown and until take-off. Its aim is to enhance the safety of these interoperations between aircraft and ships, and to prevent nations developing new systems that would not interoperate with the harpoon-grid systems already in service (clause 1).
It is narrower than a full grid specification. The document provides guidance for honeycomb design, but its primarily intention is not to specify a grid for ship construction (clause 2): each nation still describes and publishes its own grid's overall shape and construction data separately, within a companion publication it calls MPP-02. What ANEP-83 fixes as mandatory is the shared interface, the geometry that lets any compliant harpoon engage any compliant grid regardless of which nation built either one.
A harpoon-grid rapid securing system secures a helicopter or a UAV to the flight deck by extending a harpoon telescopically under the fuselage, engaging its jaw into one of the grid's holes, then locking and retracting to hold the aircraft down under tension; disengagement unlocks and retracts the harpoon again (clause 3). The grid itself is a stainless steel plate machined into a honeycomb of calibrated holes, normally flush with the deck, with an omnidirectional network of isthmus that the harpoon's claws secure onto (clause 3.3).
The harpoon must engage and disengage on an isthmus with an 80 mm clearance height under the grid; have mechanical and metallurgic characteristics compatible with the grid's own material properties; carry a built-in mechanical fuse that breaks once it reaches a specified tension, so an overload shears the fuse rather than damaging the deck or the aircraft; and engage regardless of the helicopter's heading.
Working from the grid-detail drawing at figure 6.3, clause 4.2 fixes the honeycomb's own geometry:
This is the interoperability layer: get any one of these wrong and a harpoon built to one nation's tolerances will not reliably engage a grid built to another's.
Clause 5 is optional rather than mandatory: the grid should be at least capable of withstanding constraints in accordance with the heaviest helicopter likely to operate on the deck, and the document gives worked examples, not one universal figure, across a UAV-VTOL, a light helicopter and a medium helicopter:
A nation picks the class, and the figures that go with it, that match the heaviest aircraft its own deck expects to operate. The remaining clause, 6, is drawings rather than requirements: an illustration of a harpoon locked into a grid, a general grid display, the grid-detail dimensions drawing clause 4.2 refers to, and an enlargement of the grid.
ANEP-83 does not address individual aircrew or shipboard operators directly. Its own terms point to the nations that approved it through the Military Committee Maritime Standardization Board, and to whichever national authority, shipyard or harpoon designer specifies the equipment. Nations agree to use the publication through the agreement recorded in STANAG 1276; it binds a nation's own naval engineering authority once that nation has taken the agreement on, and it reaches a shipyard or a designer because that authority specifies it, not because NATO printed the document. Edition A, Version 1 was promulgated 25 June 2014 and is effective upon receipt; the document does not say what, if anything, it superseded.
ANEP-83 describes no certification, audit or inspection scheme, and names no accredited body, notified body or government surveillance role. What exists is a set of mandatory figures in clause 4 and example figures in clause 5; checking a specific harpoon or grid design against them is left to whichever national naval engineering authority or shipyard specifies and accepts the equipment.
NATO publishes ANEP-83 through the NATO Standardization Document Database at no charge. ComplyTrain does not sell it or host a copy; the NSDD listing for ANEP-83 is the source. It is covered by STANAG 1276, the agreement recording nations' commitment to use it.
ANEP-83 is a mechanical engineering interface standard. The work it demands, fixing a harpoon's and a grid's clearances, tolerances and material properties, and verifying a specific design against them, is naval architecture and mechanical engineering, not something a compliance platform performs.
What ComplyTrain supports is the paperwork trail around that engineering work: holding the design and verification records that show a harpoon or a grid was specified against clause 4's mandatory characteristics, the national data a nation submits for MPP-02, and the revision history and sign-offs behind them, kept current and ready to produce for a customer or a national authority.
What ComplyTrain does not do: it does not design, machine, test or accept a harpoon or a grid, and it does not decide which of clause 5's weight-class figures a nation should specify for its own ships. See where ANEP-83 sits alongside STANAG 1276 and other maritime publications in the standards explorer, and talk to us about the design and verification record trail behind it.
Tell us how you need to work with ANEP-83 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. ANEP-83 is covered by STANAG 1276, the agreement recording nations' commitment to use it. Whether it applies to a specific ship or aircraft programme depends on whether the operating nation has taken on that agreement and specifies ANEP-83 in its own naval engineering requirements.
No. Its stated intention is not to specify a grid for ship construction. It fixes the interface dimensions in clause 4, the geometry a harpoon and a grid must share, and leaves each nation to describe and publish its own grid's overall shape and construction data separately, in a publication it calls MPP-02.
Clause 4's harpoon and honeycomb dimensions apply to every compliant system. Clause 5's load and material figures are worked examples a nation uses to size a grid to its heaviest expected aircraft, scaled across a UAV-VTOL, a light helicopter and a medium helicopter, rather than a single fixed requirement.
Yes. The document defines the harpoon-grid system as securing "a VTOL aircraft (Helicopter or UAV)" to the flight deck, and clause 5's example mechanical characteristics give a separate UAV-VTOL class alongside light and medium helicopter classes.
The document does not say. It sets the mandatory and example figures but names no accredited body, notified body or government surveillance role; checking a specific design against them is a matter for whichever national naval engineering authority or shipyard specifies and accepts the equipment.
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.