Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3610
NATO nations that ratify and implement the agreement, and the suppliers who meet AAGSP-03 through a resulting tender or contract
STANAG 3610 is NATO's agreement committing member nations to implement AAGSP-03, the publication covering conditioned breathable air supplied to aircraft on the ground.
STANAG 3610 is NATO's Standardization Agreement covering conditioned breathable air supplied to aircraft on the ground. Ratified by member nations and promulgated by the NATO Standardization Office, the current text (Edition 4, dated 15 June 2015) supersedes Edition 3 and commits participating nations to implement the document that actually carries the technical requirement: AAGSP-03, Edition A. STANAG 3610 itself sets out the interoperability requirement and the mechanics of ratification, implementation and review. The air characteristics and purity requirements live in AAGSP-03, not here, and this page does not restate them.
Its stated aim is to define the requirements for conditioned breathable air supplied to aircraft on the ground so that pilots, crew and passengers have collective or individual environmental comfort. In practice, this is why the underlying specification exists in the first place: so that NATO forces servicing each other's aircraft on the ground, in whichever nation, can expect a comparable, breathable, conditioned air supply.
A STANAG binds a nation, not a supplier directly. NATO's own text describes it as effective upon receipt and ready for use by the implementing nations and NATO bodies, and partner nations are separately invited to adopt it, without the ratification step that binds a member nation. A nation is considered to have implemented STANAG 3610 once it has issued instructions that all future equipment it procures for its forces will be manufactured to the AAGSP-03 specification. No retrofit of equipment already in service is required. That is the detail worth noting: the agreement reaches new procurement, not existing fleets, unless a specific contract says otherwise.
Nations record their ratification and implementation decisions in the NATO Standardization Document Database (NSDD) and report effective implementation using the form at Annex H to AAP-03(J); partner nations report adoption using Annex G to the same publication. For a supplier, the practical route in is a tender or contract that requires conformance with AAGSP-03, not the STANAG itself, and it is worth checking which of those has actually been invoked before assuming either applies.
STANAG 3610 is reviewed at least once every three years, with the outcome recorded in the NSDD. Any nation or NATO body may propose a change at any time, through a standardization proposal to the tasking authority, and the change is processed at the next review. STANAG 3208, on air conditioning connections, is named as a related document, cited as background rather than something this agreement itself requires.
The agreement is supervised by the Military Committee's air standardization bureau, working group for aircraft gaseous systems. France's General Armaments Directorate holds custody of it on NATO's behalf.
NATO's Standardization Document Database lists the catalogue and serves the unclassified text of STANAG 3610 free of charge; NATO does not sell its standardization agreements and we do not host a copy. The NSDD record for STANAG 3610 is the authoritative source, and NATO is the publisher.
STANAG 3610 is the ratification and implementation record, not a document with its own audit checklist. That checklist, where one exists, belongs to AAGSP-03. Once a nation's procurement or a contract requires equipment to meet AAGSP-03, the practical work is holding evidence that it was met: the procurement specification that cites AAGSP-03, the documentation showing the equipment was manufactured to it, and a record of who signed that off. ComplyTrain is where an organisation keeps that kind of evidence: documented procedures, controlled specifications, training records for the people who write or check them, and an audit trail showing when a requirement changed and who approved the response.
What it does not do: it does not test or measure the breathable air a piece of ground support equipment actually delivers, and it does not inspect the equipment itself. That is engineering and test work, carried out against AAGSP-03's own requirements, not something a compliance platform performs.
Which tier of NATO air standards applies to a given programme, and what else sits alongside STANAG 3610 and AAGSP-03, is set by the contract and the customer's quality clause, not by us. The standards explorer shows what else is in scope for a defence aviation programme. Talk to us about how you would hold the evidence for it.
Tell us how you need to work with STANAG 3610 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.
Only for a nation that has ratified it, and even then it reaches a supplier only once a tender or contract requires conformance with AAGSP-03. NATO does not fine, inspect or certify a company directly under the agreement.
STANAG 3610 is the agreement; the technical requirement for conditioned breathable air supplied to aircraft on the ground sits in AAGSP-03, the publication it brings into force.
No. The agreement is considered implemented once a nation requires future procurement to conform; equipment already in service carries no retrofit obligation under the STANAG itself, though a specific contract could still ask for it.
No. The agreement names no certification scheme. Nations record their ratification and implementation status administratively in the NSDD, and a supplier's conformance is evidenced through the contract that invokes AAGSP-03, not through a certificate.
STANAG 3610 is the agreement by which nations commit to implement a standard. AAGSP-03 is the Allied publication that actually holds the technical requirement for conditioned breathable air.
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.