Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3117
Defence organisations whose personnel marshal aircraft on NATO or allied airfields under a directive or contract that invokes STANAG 3117 or the AFSP-02 publication it covers
STANAG 3117 is NATO's ratification agreement committing member nations to implement AFSP-02, Edition B, the Allied publication that sets out aircraft marshalling signals.
STANAG 3117 is the NATO Standardization Agreement covering aircraft marshalling signals used across NATO nations. This is Edition 10, promulgated 3 June 2025, superseding Edition 9 of 4 September 2014.
A STANAG is the agreement by which NATO nations commit to implement a standard, not the technical specification itself. STANAG 3117's own text is short and administrative: an aim, an interoperability requirement, and the ratification and reporting machinery. The marshalling signals named in its title are specified in a separate publication, AFSP-02, Edition B, which the STANAG names as the standard participating nations "agree to implement". Anyone training personnel against those signals, or referencing them directly, needs AFSP-02's own text, not this cover agreement.
The stated aim is interoperability: "to standardize within NATO nations the aircraft marshalling signals that apply to the operation of all aircraft", so that aircraft of one nation "can safely operate on any nations bases or ships". This edition was revised specifically "to include additional marshalling signals for tilt rotor aircraft", extending AFSP-02's scope without this STANAG detailing what those signals are.
STANAG 3117 binds nations, not suppliers or ground crews directly. It is effective "upon receipt for use by the participating nations and NATO bodies", and it becomes binding on a given nation through ratification, which NATO records in the NATO Standardization Documents Database (NSDD). Implementation is a separate, further step: the STANAG and AFSP-02 are "considered implemented when the national authorities have updated and distributed all applicable national guidance and training". Allied nations and NATO bodies are then obliged to report implementation details through NATO's electronic reporting tool; partner nations are only invited to do the same. This edition sets no NATO-wide effective date; its own "NATO Effective Date (NED)" field reads "Not applicable".
STANAG 3117 describes no certification scheme and no audit. What it describes is nations reporting their ratification and implementation status to NATO for the record; nobody is "STANAG 3117 certified", and the document never uses that language. Where an organisation's marshalling training or ground-handling procedures do get checked in practice, the assessor and the evidence required are set by the applicable national authority, service directive, or customer audit regime, not by this STANAG.
STANAG 3117 covers AFSP-02, the Allied Flight Signals Publication that carries the actual marshalling signals. Reviews of STANAG 3117 itself run under AAP-03. The document's own "Other Related Documents" entry names nothing further.
Aircraft marshalling is followed in day-to-day ground operations, not in a compliance platform: ground crews use the signals AFSP-02 specifies, a training programme teaches and assesses them, and a quality or safety department retains the records that prove personnel were trained on the current edition, including any scope addition such as the tilt rotor signals this edition introduced.
What ComplyTrain does for that kind of work generally is give a defence organisation one auditable place to hold the training procedures, the competency and refresher-training records for the people who marshal aircraft, and the evidence trail - non-conformances, corrective actions, document control - that a national authority or a customer's quality representative will ask to see when an edition changes.
ComplyTrain does not marshal aircraft, teach the signals, or determine which edition of AFSP-02 a given airfield or unit has adopted. That is ground-operations and national-authority work, carried out against the publication itself and whatever service directive or contract applies.
Which STANAGs and Allied Publications actually apply to a given airfield or contract is set by the customer's quality clause and national guidance, not by us. Browse the explorer to see what sits alongside STANAG 3117 and AFSP-02, and talk to us about the evidence trail once you know which ones are in your contract.
Tell us how you need to work with STANAG 3117 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 and implemented it, and it reaches ground crews or contractors only where a national directive or contract invokes it. The STANAG's own "NATO Effective Date (NED)" field reads "Not applicable", so there is no blanket start date to point to.
STANAG 3117 is the NATO ratification agreement; AFSP-02, Edition B is the publication that actually specifies the aircraft marshalling signals. Ratifying STANAG 3117 is how a nation commits to implement AFSP-02.
No. STANAG 3117 describes nations ratifying and reporting implementation to NATO, recorded in the NATO Standardization Documents Database. It describes no certification or audit scheme for a supplier, a ground crew, or a training programme.
This edition, Edition 10, promulgated 3 June 2025, supersedes "STANAG 3117, Edition 9, dated 4 September 2014" and was revised "to include additional marshalling signals for tilt rotor aircraft", though the signals themselves are set out in AFSP-02, not in this STANAG.
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.