Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3766
NATO nations, and the aircraft and aero-engine manufacturers and servicing organisations that fit and maintain grease nipples under their contracts
STANAG 3766 is NATO's agreement committing ratifying nations to fit ISO 413:1974 grease nipples to aircraft and aero-engines so ground crews can cross-service allied aircraft.
STANAG 3766 is the NATO standardization agreement covering grease nipples for aircraft servicing. Where many STANAGs are only a cover for a separate Allied Publication, most of what this one standardizes sits in the agreement itself: participating nations agree to conform all lubricating grease nipples fitted in aircraft, aero-engines and their components to ISO 413:1974, and to provide a minimum clearance space around each nipple so a grease gun connector can be coupled and uncoupled. Nations are also to issue instructions capping the pressure a grease gun may apply when coupled, an operating limit for the ground crew rather than a nipple dimension.
The Interoperability Requirements clause states the aim plainly: the agreement exists so as "to facilitate cross-servicing of the aircraft of member nations." Read plainly, that means the point is that one NATO nation's ground crew can service another nation's aircraft with a standard connector, not that a single national design is imposed on anyone.
This is Edition 4, promulgated 23 May 2017. It supersedes an earlier edition of STANAG 3766; the document does not give that earlier edition's number.
The mechanism that matters here: a STANAG binds a nation, not a supplier. The agreement "is effective upon receipt" and ready to be used by the implementing nations and NATO bodies once ratified, and a nation's own implementation is complete once it "has issued instructions that all future aircraft, aero-engines and the components of both will be in accordance with this agreement." A manufacturer or a servicing organisation meets ISO 413:1974 or this STANAG only where a contract, tender or specification brings it in by name, not because the STANAG exists on its own.
their components must conform to ISO 413:1974, which the STANAG names as covering aircraft lubricating nipple heads.
nipple so a grease gun connector can be coupled and uncoupled - without it, cross-servicing another nation's aircraft is not practical even where the nipple itself conforms.
grease gun may apply when coupled, an operating instruction for ground crews rather than a nipple dimension.
AAP-03(J); partner nations report their adoption of the STANAG the same way, using the form in Annex G to AAP-03(J).
recorded in the NATO Standardization Document Database (NSDD).
No certification exists here, and the document names none. What it describes is a national ratification, implementation and reporting cycle run through NATO's own machinery, not an audit against this STANAG as such. A supplier's actual conformance to ISO 413:1974, and the clearance and pressure requirements, are what a customer's own contract or quality clause checks.
STANAG 3766 sets a physical interoperability requirement for hardware fitted to aircraft, not a management system: choosing and fitting a conforming grease nipple, keeping the required clearance, and observing the pressure limit for grease guns is done in design, manufacture and on the flight line, not in software. What that leaves to evidence is the paperwork around it: a procedure that correctly calls up ISO 413:1974 and this STANAG wherever grease nipples are specified, records that ground crews have been trained on the connector and the pressure limit, and the trail an internal or customer audit asks for afterwards.
ComplyTrain holds that evidence as a modern, auditable system: version-controlled procedures, training records tied to named individuals and dates, and corrective actions when a non-conforming fitting turns up, all searchable when a customer's quality clause asks for it. It does not select or fit a grease nipple, does not inspect an aircraft's servicing points, and does not replace the ratification, implementation and reporting a nation carries out itself through the NSDD and the AAP-03(J) forms.
The applicable tier here, and whatever else it comes with, is set by the contract and the customer's quality clause. If you are working out what sits alongside STANAG 3766, the standards explorer covers the related NATO aviation publications, and we are glad to talk through what that means in practice.
Tell us how you need to work with STANAG 3766 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 in general. It binds a nation once that nation ratifies it, and it reaches a manufacturer or a servicing organisation through a contract, tender or specification that names ISO 413:1974 or this STANAG, not by existing on its own. Whether it applies to a given programme is set by the specification in front of you.
STANAG 3766 is NATO's agreement to conform to ISO 413:1974 across participating nations, plus the clearance and grease-gun-pressure requirements that make cross-servicing practical. ISO 413:1974 is the civil standard the agreement calls up for the heads of aircraft lubricating nipples themselves.
Edition 4, promulgated 23 May 2017. It supersedes an earlier edition of STANAG 3766; the document available to us does not give that earlier edition's number.
No. There is no accredited certification for STANAG 3766 to hold, and ComplyTrain does not claim one. What we support is the evidence trail around procedures and training for fitting and servicing conforming grease nipples, at an informational level.
At least once every three years, with the result recorded in the NATO Standardization Document Database. Nations and NATO bodies can also propose changes at any time through a standardization proposal to the tasking authority.
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.