The airport SMS rule is
not the Part 5 rule.

The full answer is in the highlighted block above the contents list. The rest of this article separates the airport rule from the operator rule, explains the triggering criteria and the staggered deadlines, walks through what an airport SMS actually manages, and shows why the tenant and ground-handler interfaces are the hard part.

The single most important thing to get right about airport SMS is that it is not the rule everyone has been talking about since 2024. Two different FAA SMS rules exist, on different timelines, with different citations, covering different organizations:

• The Part 5 SMS rule (2024) governs operators. Published April 26, 2024 and effective May 28, 2024, it revised 14 CFR Part 5 and extended a formal Safety Management System to all Part 135 certificate holders, 91.147 air tour operators and certain Part 21 design and production holders. Part 121 airlines were already there. Our Part 5 final rule explainer covers that side, and the Part 21 design and manufacturing piece covers the manufacturing case.
• The airport SMS rule (2023) governs airports. Published February 23, 2023 and effective April 24, 2023, it is codified at 14 CFR 139.343 and applies to Part 139 certificated airports that meet triggering criteria. It predates the operator rule by more than a year.

They are easy to confuse because both are SMS and both use the same four components. But an airport does not implement its SMS under Part 5, and an operator does not implement under 139.343. If you run or hold a certificate for an airport, 139.343 is your rule, and its deadlines, not the May 2027 date attached to the operator rule, are the ones that bind you. Mixing the two is the most common planning error in this area, and it usually surfaces as a missed plan-submission date because someone tracked the wrong regulation.

The airport rule does not apply to every Part 139 certificated airport. It uses triggering criteria, tied to hub classification and international traffic, to decide which airports are in scope and, for those that are, how quickly they must act. Larger and busier airports are captured first and given the tighter timeline; others are phased in behind them.

The obligations come in two stages, and both are staggered by criteria:

• Implementation plan. Airports in scope must submit an SMS implementation plan to the FAA. Depending on which criteria an airport meets, that plan is due somewhere between 12 and 24 months after the April 24, 2023 effective date.
• Full implementation. After the plan is accepted, the airport builds and operates its SMS, with full implementation running roughly 4 to 5 years from the effective date. In practice those final deadlines land in 2027 and 2028.

We are deliberately not printing a per-hub date table here, and you should be wary of any source that does without pointing straight at the FAA. The exact plan-submission and implementation deadlines depend on your airport's specific classification, and the authoritative source is the FAA's published applicability list, not a summarized table. Find your airport on that list, read the dates attached to your category, and build your program backward from the implementation deadline with the plan-submission date as the first hard milestone. A compliance workspace that tracks each obligation against its own due date keeps that schedule honest.

An airport SMS applies the same four components an operator uses, but the hazards are specific to running an aerodrome, and they differ enough from an operator's that lifting an airline SMS manual wholesale does not work. If you want the components themselves, the four components of SMS are the primer; here is the airport-specific subject matter they govern:

• Movement and non-movement areas. The movement area (runways and taxiways under air traffic control) and the non-movement area (aprons, ramps and service roads) each carry their own hazards: runway incursions, vehicle and pedestrian deviations, foreign object debris, surface condition and apron congestion. An airport SMS has to see both, because a large share of ground risk lives in the non-movement area where control is looser.
• Wildlife. Wildlife hazard management is a defining airport concern, from bird strike risk to larger animals on the field. The SMS treats wildlife activity as a hazard stream to be identified, assessed and controlled, with the results feeding indicators rather than a once-a-year report.
• Construction safety and phasing. Airfield construction is a rolling hazard: partial runway closures, changed taxi routes, marking and lighting changes, and contractors operating near live movement areas. Each construction phase is a change that safety risk management has to clear before it goes live and monitor while it runs.
• Tenant and ground-handler interfaces.Airlines, ground handlers, fuel providers, caterers and fixed-base operators all work on the field under the airport's certificate. Their activities create hazards the airport is accountable for managing, even though it does not directly employ the people doing the work.

The last item is where an airport SMS is hardest, and it deserves its own section.

An airport is not a single organization with one workforce. It is a shared operating environment where many independent companies work side by side on the same movement and non-movement areas, and the airport certificate holder is accountable for the safety of the whole field. That makes the interfaces between organizations the central SMS challenge, in the same way supplier interfaces are the challenge for a manufacturer.

A ground handler's ramp incident, a fueler's spill, a construction contractor's incursion into a live area, a tenant airline's vehicle running a hold line: each is a hazard on the airport's field, reported into the airport's system, even though the people involved answer to a different employer. The airport SMS has to collect those reports, assess the risk, drive corrective action across an organizational boundary it does not command, and then verify the control held.

The structural trap is the same one every large safety operation hits. Ramp reports sit in one system, the wildlife log in another, construction notices in a third, and the airport's own inspections in a fourth. Nobody can answer “is runway incursion risk trending up this quarter” because the events that would show the trend are scattered across systems and owners. A just-culture reporting climate matters even more here, because a tenant's staff will only report into the airport's system if they trust it will not be turned against their employer.

eAviora is built for exactly this shape: many reporters, many interfaces, one accountable operator, and a requirement to prove the system works rather than assert it. It runs occurrences, hazards, investigations, corrective actions, audits, findings, documents, training, compliance and indicators as one operational graph, so a ramp report, the hazard it reveals, the corrective action across a tenant boundary, and the runway-incursion indicator it moves are linked records rather than entries in four disconnected systems.

Three properties matter most for an airport:

• Confidential reporting with a closed loop.A tenant's staff can report confidentially, and the loop closes with de-identified bulletins and reporter feedback, so the reporting climate an airport SMS depends on is built in, not bolted on.
• Closure gates over open risk. A record cannot close over open risk: a degraded barrier requires a linked corrective action, proven effective, before the parent closes. A construction hazard or a repeated ramp deviation cannot be signed off while its control is still open, a property proven by a 13-of-13 live scenario suite. See how the enforced closure gates work.
• Real statistical process control on indicators. eAviora runs Western Electric rules on indicators instead of coloring a trend arrow, so a genuine rise in incursions or wildlife activity shows up as a signal, and the computed Safety Risk Profile fuses eight components into a single ICAO Doc 9859 aligned four-level score.

The platform ships with a pre-built aviation risk model (101 bow-tie models, 804 named barriers, 210 scenarios and a 610-indicator SPI library) that an airport scopes to its own operation, so the SMS starts with structure rather than a blank hazard log. Specialist AI agents can draft a hazard analysis for review, but every AI proposal is human-gated (accept, modify or reject) and audit-logged, AI consumption is metered in plain credits with hard caps, and operator data never trains any model. Tenant isolation is enforced by the database, not application code. The SMS module is where an airport runs this day to day.