Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AASSEP-03
Aircraft manufacturers and the maintenance and ground-handling organisations that mark and service aircraft under STANAG 3109
AASSEP-03 sets NATO's common symbol scheme for marking aircraft servicing, ground-handling and safety/hazard points, so ground crews from different nations recognise them consistently.
AASSEP-03 is a NATO Allied Technical Publication that standardises the symbols used to mark an aircraft's servicing, ground-handling, safety/hazard, and armament/ammunition points. Its aim, in the document's own words, is "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" (clause 1.2). Nations record their agreement to use it in STANAG 3109; that agreement, not AASSEP-03 on its own, is what gives the publication force for a given nation. The current edition is Edition A, Version 1, promulgated in September 2014.
The problem AASSEP-03 solves is interoperability, not aesthetics. When one nation's ground crew services or handles another nation's aircraft under a cross-servicing arrangement, a locally invented symbol for a hazard or a servicing point is worse than useless to a crew that has never seen it before. So the standard fixes a single symbol set, held in five annexes grouped by the kind of point marked: general servicing and maintenance, ground handling, safety and hazard, and armament and ammunition. Clause 2.1.1 requires that markings "shall be in accordance with the symbols and allied data shown and as described in the Annexes", which rules out a manufacturer's own house symbols for these points.
Chapter 2 sets requirements for how the markings are formed, located, sized and coloured. Location has one exemption worth knowing: a marking is "not compulsory" wherever there is no possibility the point could be mistaken for anything else. Size is tied to legibility rather than a fixed figure alone: the symbols and inscriptions have to be commensurate with the distance from which they need to be read. Colour follows a convention that differentiates the categories of point, with allowances for camouflaged aircraft, so the marking does not undermine the paint scheme, and for aircraft that may be exposed to atomic flash, where legibility takes priority. The exact dimensions, colour assignments and reflectivity figures are the annexes' own content; a supplier or a maintenance organisation works from the document itself rather than a summary of it.
The standard is explicit about one exclusion: "Safety markings as applied to rescue are not covered by this standard" (clause 2.3). It also cross-references two non-NATO documents rather than restating their content: ISO 1950, on identifying aircraft servicing, maintenance, ground-handling and safety/hazard points, and ISO 3864, whose Safety Yellow definition AASSEP-03 uses for its own yellow/orange marking.
AASSEP-03 addresses whoever marks and maintains an aircraft: the organisation that builds it, and the maintenance and ground-handling organisations that service it once fielded. It reaches a supplier the way most Allied Technical Publications do, through the STANAG that carries it, and from there through a contract or a type-design requirement that names it. The standard itself names no certification body, notified body, or audit cycle; it does not describe who checks a marking against it or how often. Because what it specifies is a physical feature of the aircraft, checking it in practice falls to whatever quality or airworthiness process a customer or authority already runs.
AASSEP-03 is an operational marking standard, not a management system: the actual work is physical - applying and maintaining the correct symbol on the correct point of an aircraft - and no software does that work. ComplyTrain's part is the paperwork around it: a controlled procedure that tells a build or maintenance team which symbol set applies, a training record showing ground crew have been briefed on the current marking scheme before a cross-servicing task, and the audit finding or corrective action if a marking turns out to be missing, wrong, or obscured. What ComplyTrain does not do is apply, paint, or physically inspect the markings themselves; that stays with the people doing the servicing. The tier of standards that applies to a given contract, and whether AASSEP-03 is among them, is set by the contract and the customer's quality clause - explore the standards library to see what sits alongside it, and talk to us about the evidence trail behind it.
Tell us how you need to work with AASSEP-03 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 through a contract. AASSEP-03 gets its force from STANAG 3109, which a NATO nation ratifies; a supplier meets it because a specific tender, contract, or type-design requirement names it, not because the AP applies by default.
STANAG 3109 is the agreement nations use to commit to this publication; AASSEP-03 is the technical content itself, the symbol set and the rules for applying it. The STANAG is why it binds a nation, the AP is what it requires.
No. The document states plainly that safety markings applied to rescue are not covered by this standard, so a separate reference applies to those.
No. The document names no certification body, notified body, or audit scheme. It is a marking specification checked as part of an aircraft's normal quality or airworthiness process, not something an organisation holds a certificate against.
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.