Part 139 Airport SMS Software: What to Look For
01An airport SMS is not an airline SMS
Most safety management software on the market was designed around an air carrier: one employer, one workforce, one fleet, and hazards that travel with the aircraft. An airport is a different shape, and the differences are what a product has to be tested on.
- Tenants. Airlines, ground handlers, fuelers, caterers and fixed-base operators work on your field and answer to other employers. The safety awareness orientation in Subpart E reaches everyone authorized to access the regulated areas of the airport, not only your staff, and the reporting system has to be usable by all of them.
- Movement and non-movement areas. The rule sets the scope of the Airport Safety Management System as aircraft operations in the movement area and the non-movement area, plus the other airport operations Part 139 addresses. Location on the airfield (a runway, a taxiway intersection, a stand) is the main way your records are sorted, where an airline sorts by flight.
- Wildlife. Strikes and sightings are a standing hazard stream with its own Part 139 section and, at many airports, its own management plan.
- Construction. A live airfield is rebuilt in phases. Each phase changes taxi routes, markings and lighting, and Subpart E expects hazards to be identified in changes to airport operations, not only in steady state.
- Self-inspection. The airfield is inspected daily under its own Part 139 section. Those inspections find conditions; the SMS decides which of them are hazards worth a risk analysis.
The rule itself, who it covers and when, is in our Part 139 airport SMS rule and deadlines article. This one is about what to buy to run it.
02What Subpart E asks the system to hold
The requirement sits in 14 CFR Part 139 Subpart E (sections 139.401 to 139.403), with FAA Advisory Circular 150/5200-37A, Safety Management Systems for Airports, as the guidance. Section 139.402 lists the components, and read as a software specification it is short and specific:
- Safety Policy. A named accountable executive, a signed policy statement available to employees and tenants, a safety organizational structure and safety objectives.
- Safety Risk Management. A way to identify operational safety issues and a systematic hazard analysis in five steps: describe the system, identify the hazards, analyze the risk, assess the risk, and mitigate where appropriate. Records must show that airport management accepts the assessed risks and mitigations.
- Safety Assurance. Safety performance monitoring against the objectives, a safety reporting system that protects the confidentiality of the reporter, and regular reports to the accountable executive, including the status of ongoing mitigations.
- Safety Promotion. A safety awareness orientation reviewed at least every 24 calendar months, SMS training at least every 24 months for employees with SMS responsibilities, and formal safety communications, including feedback to people who reported.
Each of these comes with a retention period: 36 months for hazard analyses (or 12 months after the mitigations are completed, if that is later), 24 months for orientation and training records, and 12 months for communications. The rule also says the system should correspond in size, nature and complexity to the airport's operations, which is worth remembering when a vendor shows you a configuration built for a large hub.
If the four components are new to you, start with the four components of SMS. The confidentiality requirement in particular deserves care at an airport, because a ramp agent reporting into the airport's system is also reporting on their own employer. Our piece on confidential reporting systems was written for the operator rule, but the design questions carry over.
03Operations software and SMS software are two purchases
A search for Part 139 software returns two kinds of product, and telling them apart saves a wasted evaluation.
Part 139 operations software runs the airfield day to day. It holds the self-inspection program under 14 CFR 139.327 (daily unless the Airport Certification Manual says otherwise, plus inspections during unusual conditions and after an accident or incident, with records kept for at least 12 consecutive calendar months), wildlife hazard management under 139.337, and airport condition reporting under 139.339, which uses the Notice to Air Missions (NOTAM) system. It usually includes work orders for the discrepancies an inspection finds.
Airport SMS software runs Subpart E: reports, hazards, risk, mitigations, indicators, governance and the promotion records.
Some vendors sell both in one product and some airports prefer that. Others keep the operations tool they already trust and add an SMS layer. Neither is wrong. What fails is two systems with no handoff, where a recurring inspection discrepancy never becomes a hazard because nobody carried it across. Whichever way you buy, ask to see one item travel from an inspection finding to a hazard with a risk assessment and back to a closed action.
04A requirements table for the vendor call
Use this as the agenda for a demonstration. The middle column is where the need comes from, so you can check it against the regulation and your own Implementation Plan. The last column is the question to ask with the product open, not on a slide.
| What you need | Where it comes from | What to ask the vendor |
|---|---|---|
| Reporting open to everyone on the field | 139.402(c): a safety reporting system that protects reporter confidentiality | Can a tenant’s employee with no account file a report from a phone? Who can see the reporter’s name, and where is that enforced? |
| A five-step hazard analysis | 139.402(b): describe the system, identify hazards, analyze risk, assess risk, mitigate | Show one hazard from identification to mitigation. Is the risk matrix yours or the vendor’s, and can it match the one in our SMS Manual? |
| Management acceptance on the record | 139.402(b): records showing airport management accepts the assessed risks and mitigations | Who signed for this residual risk, and can someone below the required role sign it? |
| Mitigations tracked to completion | 139.402(c): status of ongoing mitigations reported to the accountable executive | Can an action assigned to a tenant or a contractor be owned, dated and verified by someone other than the person who did the work? |
| Safety performance monitoring | 139.402(c): monitoring against the airport’s safety objectives | Can we define our own airfield indicators and thresholds? What happens when one breaches? |
| Reports to the accountable executive | 139.402(c): regular reporting of safety information | What does the accountable executive open each month, and is it computed from the records or assembled by hand? |
| Orientation, training and communication records | 139.402(d): orientation and SMS training at least every 24 months, with records kept | How do we see who is due? Does it cover people who are not our employees but hold access to the movement area? |
| Change and construction | 139.402(b): hazards in changes to airport operations | Can a construction phase be risk-assessed and approved before it opens, then reviewed after it closes? |
| Self-inspection, wildlife and condition reporting | 139.327, 139.337 and 139.339: separate Part 139 programs that feed the SMS | Does the product run these, or receive from the system that does? Show the handoff from a failed inspection item to a hazard. |
| Tenant data sharing | 139.401: an optional data sharing and reporting plan with tenants that run their own Part 5 SMS | How does a tenant airline’s report reach us? By import, by interface, or by email? |
| Retention and exit | 139.402: 36, 24 and 12 month retention periods | How do we export everything, with its change history, on the day we stop paying? |
Two rows decide most evaluations. The first is reporting: if a fueler on the night shift cannot file quickly from a phone without an account, your report volume will come only from your own staff. The second is the mitigation that crosses an organizational boundary, because most airfield fixes are carried out by someone you do not employ. A product with an enforced closure gate makes that visible; a product with a free-text status field hides it.
05Where eAviora fits, and where it does not
eAviora is built for air operators first: airlines, maintenance organizations, ground handlers and training organizations. Airports are not the operation it was designed around, so here is the plain split.
What it covers of an airport SMS:
- Reporting. Occurrence reports come in on the web, in the eAviora app with or without signal, or through a public reporting page. A reporter chooses identified, confidential or anonymous.
- Hazards and risk. Each hazard sits on a bow-tie with named barriers, with initial and residual risk scored on the ICAO 5 by 5 matrix and the approver on the record.
- Mitigations. A corrective action stays linked to its source, is verified by a named person and, by default, closes only after an effectiveness review.
- Audits, governance and indicators. An audit programme with findings driven to actions, a Safety Action Group and a Safety Review Board with recorded votes, and safety performance indicators checked daily against their own thresholds. You can add your own indicators.
- Change, documents and training. Management of change approved at the rank its risk requires, controlled documents with read-and-sign, and training requirements with their recurrence.
What it does not cover:
- A Part 139 daily self-inspection checklist with airfield work orders.
- A wildlife strike and sighting log, or a wildlife hazard management plan.
- NOTAM management or airport condition reporting.
- A construction safety and phasing plan template. Management of change was written around operator changes such as a new route, aircraft type or procedure.
- An airport-specific indicator library. The indicators and bow-tie models that ship were written for air operators, so an airport would be building its own airfield set.
One module name needs a warning. eAviora's aerodrome risk assessment is an operator's assessment of the aerodromes it flies into, categorised A, B or C against EASA, FAA or ICAO criteria. It is not an airport operator's assessment of its own field and it is not a self-inspection system.
So the fit is narrow and real: an airport that keeps its airfield operations tool and wants the SMS layer on top, or a ground handler or tenant airline that needs its own SMS and reports into the airport's. If you want one product for inspections, wildlife, NOTAMs and SMS, eAviora is not that product today.
06How to run the evaluation
Skip the feature tour. Bring one real airfield hazard from the last year, something like a recurring vehicle deviation at one taxiway intersection during a construction phase, and ask each vendor to follow it through the product while you watch:
- A tenant employee reports it, without an account, and asks to stay confidential.
- It becomes a hazard, with the five-step analysis and a risk level.
- A named manager accepts the risk and the mitigation.
- The mitigation is assigned to the contractor and verified by you.
- An indicator shows whether deviations at that intersection fell.
- The accountable executive sees all of it in the regular report.
A product that completes the six steps by navigation, with every signature and date on the record, can show an inspector how your SMS works. One that needs a spreadsheet beside it at step four or five cannot, however good the dashboard looks. Our buyer's guide has the wider questions on data ownership, security and contract terms that apply to any safety platform.
Questions
It is software that holds the records and workflows an airport needs to run the Airport Safety Management System required by 14 CFR Part 139 Subpart E: a confidential safety reporting system, a hazard register with a five-step risk analysis, mitigations tracked to completion, safety performance monitoring, reports to the accountable executive, and the orientation, training and communication records the rule asks the airport to keep. It is not the same thing as Part 139 operations software, which runs the daily self-inspection, the wildlife log and airport condition reporting.
No. Subpart E sets out what the Airport Safety Management System must do and the FAA approves the airport’s Implementation Plan and the Airport Certification Manual or SMS Manual that describes it. The rule does not name, approve or certify a software product, and it does not require software at all. A vendor that says its product is FAA approved for airport SMS is describing something the rule does not provide for.
Either can work. The self-inspection program (14 CFR 139.327), wildlife hazard management (139.337) and airport condition reporting (139.339) are separate Part 139 requirements with their own records. Many airports run them in an airfield operations tool and the SMS in a safety tool. What matters is the handoff: an unsafe condition found on an inspection that is a real hazard has to reach the hazard register with its source attached, without somebody retyping it and losing the link.
Subpart E sets the periods in 14 CFR 139.402. Hazard risk analysis records are kept for the longer of 36 consecutive calendar months after the analysis is completed or 12 consecutive calendar months after the mitigations are completed. Safety awareness orientation materials and SMS training records are kept for 24 consecutive calendar months, and records of safety communications for 12 consecutive calendar months. Ask a vendor how the product shows which records are still inside their period and what happens to them if you leave.
Partly, and it depends on what you are buying. eAviora is built for air operators first: airlines, maintenance organizations, ground handlers and training organizations. It covers the SMS core an airport needs (confidential reporting, hazards on a bow-tie, risk scoring, corrective actions with an effectiveness review, audits, governance boards and indicators). It does not ship a Part 139 daily self-inspection checklist, a wildlife log or NOTAM management, and its aerodrome risk assessment is an operator’s assessment of the aerodromes it flies into. An airport that already has an airfield operations tool and needs the SMS layer is the closer fit.