Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3212
National authorities implementing NATO aircraft interoperability agreements, and the manufacturers whose contracts call up ISO 102:1990
NATO agreement committing member nations to size aircraft gravity fuel filling orifices and nozzles to the tables in ISO 102:1990, so refuelling equipment is interoperable across nations.
STANAG 3212 is a NATO standardization agreement, not a technical specification in its own right. Its interoperability requirement is to establish a minimum and/or maximum size of orifice for the gravity filling point of the aircraft tank or reservoir relative to each fluid, and a minimum and/or maximum size for the external diameters of nozzles used for the gravity filling of aircraft with fuel or other fluids. The actual figures are not in this document. Participating nations agree that internal diameters of orifices used for the gravity filling of aircraft "shall be in accordance with Table 1 of ISO 102", that external diameters of fuelling nozzles "shall be in accordance with Table 2 of ISO 102", and that nozzles used for other fluids must still fit the relevant minimum orifice diameter given in Table 1. ISO 102:1990 (Aircraft - Gravity Filling Orifices) carries those tables; STANAG 3212 is the NATO agreement that makes following them a national commitment.
This is Edition 7, promulgated 23 May 2017, which supersedes Edition 6 of STANAG 3212.
A STANAG does not bind a supplier by existing. It binds a nation once that nation has ratified it, and a nation treats it as implemented once it has issued instructions that all future aircraft will be in accordance with this agreement - new aircraft going forward, not a retrofit of an existing fleet. Partner nations are separately invited to adopt it, without a ratification obligation. Nations record their ratification and implementation position in the NATO Standardization Document Database, and may report on it using the forms in Annex H (for members) or Annex G (for partners) to AAP-03 - a reporting mechanism, not a technical requirement of the STANAG itself.
For a supplier or manufacturer, the document does not create an obligation on its own. It becomes relevant once a contract, a tender, or a national requirement calls up STANAG 3212 or ISO 102:1990 directly for a given aircraft or fuel-system component.
The STANAG names no other related document beyond ISO 102:1990 for its technical content - the "OTHER RELATED DOCUMENTS" section reads "None." It says nothing about fuel or fluid quality, fuelling procedure, or the rest of an aircraft's fuel system; it covers the size of the gravity filling orifice and the fuelling nozzle only. It carries no in-service or maintenance obligation, and it does not describe what should happen to an aircraft already built before a nation's implementing instruction takes effect.
The STANAG is reviewed at least once every three years, with the result recorded in the NSDD, and nations or NATO bodies can propose changes at any time. The tasking authority for this STANAG is the Military Committee's air standardization body, MCASB.
Meeting STANAG 3212 in practice means specifying, during aircraft or fuel-system design, that a gravity filling orifice or fuelling nozzle follows the tables in ISO 102:1990, and being able to show that the decision was made and carried through: the drawing or interface control document that calls up the ISO 102 table, the design review record, and the change record if a later revision touched the interface. ComplyTrain gives a quality team a place to hold that kind of documented decision, the procedure or work instruction behind it, and the review and training records that go with it, alongside the rest of a defence quality system's evidence.
What ComplyTrain does not do: it does not measure an orifice or a nozzle, it is not a substitute for ISO 102:1990 as the source of the actual dimensions, and it does not verify a design's physical interoperability. That is engineering and inspection work carried out on the hardware and the drawings, not something a compliance platform can do in their place.
The tier and standards that apply to a given contract are set by the contract and the customer's quality clause, not by us. If STANAG 3212 or ISO 102:1990 sits alongside other NATO or civil aviation standards on a programme, the standards explorer shows what else is commonly required, and our team is glad to talk through how the supporting documentation fits together.
Tell us how you need to work with STANAG 3212 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.
There is no general answer in the document itself. A STANAG binds a nation once ratified, and reaches a supplier through the contract or tender for a specific aircraft programme, not automatically. Whether it applies to a given supplier depends on what the contract and the customer's quality clause call up.
No. STANAG 3212 commits nations to follow the tables in ISO 102:1990 (Aircraft - Gravity Filling Orifices); the dimensions themselves are set out in that document, not in the STANAG.
Edition 7, promulgated 23 May 2017, supersedes Edition 6 of STANAG 3212. The letter of promulgation names the earlier edition but does not give its date.
STANAG 3212 is a NATO document, free of charge, available through the NATO Standardization Document Database. ISO 102:1990 is a separate civil standard, sold by ISO and by national standards bodies; it is not distributed by NATO or by us.
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.