Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AFSP-1.4
Contractors and operators supporting wildlife hazard management at a NATO nation's military airfield
AFSP-1.4 is NATO's publication standardising how nations manage wildlife strike risk at military airfields, adopted through STANAG 3879 and implemented through each nation's own orders and instructions.
AFSP-1.4, Wildlife Strike Prevention, is a NATO Allied Flight Safety Publication that standardises the measures nations take to avoid collisions between wildlife and military aircraft. Section 1.1 states that the publication's aim "is to standardize the measures to avoid collisions between wildlife and aircraft." It sits under STANAG 3879, the standardization agreement that records nations' commitment to use it, and the current edition, Edition B Version 1, was approved by the nations in the Military Committee Air Standardization Board and promulgated in December 2024, superseding Edition A Version 1.
The publication works by having nations adopt, as far as practicable, the wildlife hazard management standards already set out in ICAO Doc 9137, Part 3, and by translating references to civil aviation authorities into their military equivalent where the two do not map directly - "one acts in the spirit of the ICAO doc 9137 instead of to the letter of the document." Annex B lists the specific terminology and role changes this translation needs, and a nation records any further deviations of its own from the ICAO baseline in the reservations at the front of the document.
AFSP-1.4 binds at the level of nations, not companies. A nation takes the standard on by ratifying STANAG 3879, and the publication itself becomes real only "when a nation has issued the necessary orders/instructions putting the procedures detailed in this standard into effect." It carries no certification or audit scheme of its own, and how fully a specific airfield applies it depends on that nation's own instructions: twelve nations, including Bulgaria, Canada, Denmark, Estonia, Finland, Croatia, Hungary, Italy and Romania, recorded reservations at promulgation, mostly because they lack the radar or national reporting system the exchange requirement assumes.
Section 1.3 sets out nine numbered obligations. A nation must manage its military airfields' habitat, infrastructure and human activity so the site is unattractive to hazardous wildlife (point 1), assess the wildlife hazard "on a permanent base, using the Safety Management System approach" and work to minimise it (point 2), and restrict activities and land-use practices near an airbase that increase the risk of a strike (points 3 and 4). Each airbase must be staffed with a Wildlife Control Unit responsible for the hazard, whose personnel are competent, educated, trained and properly equipped to monitor, assess and manage it (point 5) - an auditor looking at this clause would ask for the unit's staffing and training records, not for a description of how it does its work. Section 1.2 adds that wildlife strike prevention should serve the environment alongside flight safety wherever the two are not in conflict.
The remaining obligations in section 1.3 are about exchange between nations rather than airfield management. Nations agree to provide bird strike warning information to the flying community as a BIRDTAM or a NOTAM (point 6), and where a defined bird-intensity threshold is reached, on a scale running from 0 ("Nil") to 8 ("Extremely great") - referred to in one nation's reservation as "the 0-8 taxonomy specified in AFSP-1.4, paragraph 1.3.7" - they must exchange that information with neighbouring countries in the format Annex A sets out: an issuing station, a validity window, the intensity, a geographic reference taken from the low-flying chart, the hazard's lower and upper height limits, and additional information. Nations also agree to calibrate the information they disseminate this way (point 8) and to collect, document and identify evidence from strikes for reporting purposes (point 9).
Annex B separately maps a handful of ICAO Doc 9137 civil terms onto their military equivalent - adding "Military Aviation Authority" to the glossary in place of "Civil Aviation Authority," for example - and, in one case, loosens rather than tightens the underlying ICAO wording, changing a "should include" list of national-committee representatives to "may include."
AFSP-1.4 is a standardization agreement, not an operating manual. It states what a nation's airfields and reporting must achieve, and it leaves the detail of how a hazard is actually managed on the ground, and any specific method used, to the nation's own procedures and to ICAO Doc 9137 itself. It names no certification scheme, no accredited body and no notified body: the only mechanism the text describes is a nation issuing its own implementing orders, and the Record of Reservations shows that what a specific nation actually applies can already fall short of the full text.
AFSP-1.4 is an operational standard, not a management-system one: the work it describes - habitat and activity management, permanent hazard assessment, staffing a competent Wildlife Control Unit, and BIRDTAM/NOTAM reporting - happens at the airfield itself, in the day-to-day handling of the site, not in software. For a company supporting a military airfield, what helps is the documentation trail that work leaves behind: the procedures a specific airfield's wildlife hazard management programme sets out, training and competency records for personnel assigned to the Wildlife Control Unit, records of the hazard assessments actually carried out, and the reservations or deviations a customer nation has recorded against the ICAO Doc 9137 baseline, kept so they are not lost between contract and delivery.
What ComplyTrain does not do: it does not manage habitat, assess a live wildlife hazard, staff or run a Wildlife Control Unit, or issue a BIRDTAM or a NOTAM. That work stays with the airfield operator and the nation's own safety management system.
Which parts of a wildlife hazard management programme a specific airfield contract requires, and what else sits alongside it in a NATO flight-safety package, is set by the customer's contract and quality clause, not by us. See what else is in the catalogue in the standards explorer, and talk to us about the evidence trail behind it.
Tell us how you need to work with AFSP-1.4 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.
Not directly on a company. AFSP-1.4 binds a NATO nation once that nation ratifies STANAG 3879 and issues its own orders putting the standard into effect (section 1.4). For a company supporting an airfield, it becomes a requirement only where a specific airfield's programme or contract names it.
Both are how a nation warns the flying community of a bird hazard. A BIRDTAM is the geographic-reference message defined in Annex A, built around radar-based bird migration data; a NOTAM is a position-based notice from other sources. Section 1.3 lets a nation use either.
No. AFSP-1.4 names no certification scheme and no accredited or notified body. The only mechanism it describes is a nation issuing its own implementing orders, and the reservations recorded at promulgation show that what a nation actually applies can already differ from the full text.
Edition B, Version 1, promulgated in December 2024, is current. It superseded Edition A, Version 1, which nations were told to destroy under their own local document-destruction procedure.
No. It sets out what a nation's airfields and cross-border reporting must achieve, largely by adopting ICAO Doc 9137, Part 3. The specific methods used to manage a hazard on the ground are a matter for the airfield's own procedures, not for this publication.
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.