Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3109
National authorities and NATO bodies that ratify and implement the agreement, reaching aircraft servicing organisations once a nation has adopted it
STANAG 3109 is the NATO agreement bringing AASSEP-03 into force, standardizing symbol marking of aircraft servicing and safety/hazard points across ratifying nations.
STANAG 3109 is the NATO standardization agreement covering symbol marking of aircraft servicing and safety/hazard points. Like every STANAG, it is not itself a technical specification: it is the agreement by which NATO nations commit to implement one, and the specification lives in the Allied Publication it covers, here AASSEP-03, Edition A. Participating nations "agree to implement the following standard for symbol marking of aircraft servicing and safety/hazard points" - that standard, not the STANAG's own text, is what actually defines the markings. This is the sixth edition, dated 15 September 2014, superseding an earlier edition of STANAG 3109.
The stated aim is interoperability. The STANAG exists "to standardize servicing markings on aircraft for cross-servicing and to give warnings, the neglect of which may cause damage to equipment or injury to personnel." In plain terms: when ground crews from different nations service or cross-service each other's aircraft, they need to recognise the same markings for servicing and safety/hazard points, or the risk is damage to the aircraft or injury to the people working on it. The STANAG does not describe what those markings look like; that detail belongs to AASSEP-03.
Ratification and implementation are separate steps here. The STANAG is "effective upon receipt and ready to be used by the implementing nations and NATO bodies" once ratified, but a nation is only considered to have implemented it "when the provisions specified therein have been included in the national documentation concerned with reference to STANAG 3109." Partner nations sit outside ratification altogether: they "are invited to adopt this STANAG" rather than being bound by it. So "is STANAG 3109 mandatory" has no single answer - it depends on ratification, national documentation, and whether a contract or tender then invokes it. For an aircraft servicing organisation, that route is how the obligation actually arrives; the STANAG itself binds nations, not companies.
Nations record their ratification and implementation decisions with the NATO Standardization Office (NSO), in the NATO Standardization Document Database (NSDD). A nation reports its effective implementation using the form in Annex H to AAP-03(J); a partner nation uses Annex G of the same publication to report adoption. The STANAG "is to be reviewed at least once every three years", with the result recorded in the NSDD, and a nation or NATO body can propose a change at any time to the tasking authority for the next review. The agreement is unclassified, handled under C-M(2002)60, and is not for commercial reproduction or sale without the publisher's permission, though member nations, Partnership for Peace countries, and NATO commands and bodies are exempted.
The STANAG names two other documents covering related ground without stating whether either binds alongside it: ISO 1950 (Aircraft - Identification of Servicing, Maintenance, Ground Handling and Safety/Hazard Points) and ISO 3864 (Graphical symbols - Safety colours and safety signs). Both sit outside our catalogue. The marking specification itself - what the symbols look like, where they go, what they mean - is entirely in AASSEP-03, not here.
No organisation is certified against STANAG 3109. What the document describes is a national reporting and periodic-review cycle: a nation's ratification and implementation decision is recorded with the NSO, effective implementation is reported on a standard NSDD form, and the STANAG is reviewed at least every three years. There is no accredited body, notified body or third-party audit anywhere in this mechanism, and nothing in it is assessed against a company directly.
STANAG 3109 is a framework agreement, not a technical specification, so there is nothing in the STANAG itself to implement in software. The actual requirements sit in AASSEP-03, and the work of meeting them - marking and checking servicing and safety/hazard points on real aircraft - happens on the ground, not on a screen.
What ComplyTrain does for that kind of work in general: hold the procedure that tells ground crews how marking and inspection is meant to be carried out, keep the training records for the people who service or cross-service aircraft, and retain the audit trail showing the procedure was followed and any deviation was corrected. That is the same evidence trail an auditor or a customer would ask for on any operational standard, whatever the specific markings AASSEP-03 requires.
ComplyTrain does not mark an aircraft, inspect existing markings, or take any part in a nation's own ratification, reporting or three-year review with the NSO. The applicable tier and the standards that come with it are set by the contract and the customer's quality clause, not by us - if you are working out what sits alongside this agreement, the standards explorer shows the related publications, and we are glad to talk through what evidencing it in practice would involve.
Tell us how you need to work with STANAG 3109 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 where a nation has ratified it and folded its provisions into national documentation, or a contract or tender invokes it. The STANAG binds nations on ratification, not companies directly, and partner nations are invited to adopt it rather than bound by it.
Very little on its own. It is the agreement by which nations commit to implement AASSEP-03, Edition A, which is the publication that defines the actual symbol marking of aircraft servicing and safety/hazard points.
No. The document describes a national ratification, implementation and review cycle run through the NATO Standardization Office, not a certification scheme, and no organisation is assessed against it directly.
STANAG 3109 is the agreement; AASSEP-03 is the specification it brings into force. Reading the STANAG tells you how it comes to bind a nation. Reading AASSEP-03 tells you what the markings actually are.
At least once every three years, with the result recorded in the NATO Standardization Document Database. Nations and NATO bodies can propose changes at any time, and they are processed at the next review.
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.