What Is the FAA Safety Assurance System (SAS)?
How the FAA Oversees Part 135 Operators

SAS, in One Sentence

If you have ever wondered what the FAA is actually doing when it certificates and then keeps an eye on a Part 135 operator, the answer has a name: the Safety Assurance System. SAS is the standardized framework Flight Standards uses to decide what to look at, build an oversight plan, collect data, and act on what it finds. It replaced the older oversight approaches with a risk-based, data-supported model — the idea being to point finite inspector resources where the data suggests they are most warranted.

Two clarifications upfront, because both are easy to get wrong. First, SAS is not a regulation. You will not find "SAS" as a section of 14 CFR. It is FAA guidance and internal policy — principally FAA Order 8900.1, Volume 10. The rules SAS helps the FAA oversee live in the CFR (Part 5, Part 119, the Part 135 operating rules). Second, SAS is not your SMS; that distinction gets its own section below, because conflating the two is the most common SAS misunderstanding among operators.

The FAA describes SAS as the combination of people, processes, and technology that constitutes Flight Standards' safety-assurance capability. It is the oversight system for 14 CFR parts 121 and 135 air operators and parts 141, 142, 145, and 147 agencies. It was developed by the FAA's System Approach for Safety Oversight (SASO) program, and its policy and procedures are documented in FAA Order 8900.1, Volume 10. None of that is a regulation — it is how the agency organizes itself to conduct the oversight the regulations authorize.

The single most useful line in the FAA's own SAS overview is this one: "SAS is not a separate safety standard and does not impose additional requirements on certificate holders." That is the whole philosophy in a sentence. SAS does not add to the rulebook; it standardizes how inspectors evaluate whether you are meeting the rulebook you already have. The FAA frames the larger goal as enhancing the risk-based, data-supported approach to oversight — concentrating attention where the data points.

For Part 135 operators, the FAA notes a wrinkle worth knowing: some of the data collection is done by the operator, much like a compliance statement — you identify where in your manual system a required procedure or record is located, and your principal inspectors verify it. That is why a clean, cross-referenced documentation system is not just nice to have under SAS; it is part of how data collection actually happens.

Here is the confusion in plain terms. Your Safety Management System (SMS) under 14 CFR Part 5 has four pillars: safety policy, safety risk management, safety assurance, and safety promotion (the safety-assurance pillar lives in Subpart D, §§5.71–5.75). The FAA's oversight system is called the Safety Assurance System. Same two words — completely different owners.

The reason the names overlap is genuine, not coincidental: the FAA describes SAS as the safety-assurance component of the FAA's own internal management system. In other words, the FAA applies SMS thinking to itself, and SAS is how the agency "assures" the safety of the system it oversees. So both you and your regulator have a "safety assurance" function — yours is one pillar of your Part 5 SMS, and the FAA's is the SAS surveillance it runs on you.

Why this matters for you right now: the Part 5 SMS mandate is the big near-term obligation. The FAA's 2024 final rule extended SMS to all Part 135 operators — regardless of size, including single- and two-aircraft operations — with a single compliance deadline of May 28, 2027, by which each operator must submit a Declaration of Compliance under 14 CFR 5.9. That is your system. SAS is the lens the FAA will use to look at it — and at everything else you do. For the SMS obligation itself, see Part 135 SMS requirements and the May 28, 2027 SMS deadline. The accountable-executive role that anchors both — 14 CFR 5.25 — is covered in the Part 135 accountable executive, and the emergency response plan under 14 CFR 5.27 in our Part 135 emergency response plan guide.

The engine of SAS is data collection. An Aviation Safety Inspector collects information while conducting oversight of your processes — both how they are designed and how they perform — so your principal inspectors can make informed decisions about your operating systems, both before approving or accepting them when regulations require, and during ongoing assessments. The structured questionnaires inspectors use to do this are called Data Collection Tools (DCTs).

DCTs come in a few flavors. A useful way to think about them is design-versus-performance: some tools ask whether a process is properly designed (is the procedure written into your manuals, are responsibilities clear?), and others observe whether it actually performs as designed in the real operation. Here are the main types in plain terms — and, more usefully for you, the records each one tends to land on.

The historical names for the underlying inspection types — Safety Attribute Inspections (SAIs) for design and Element Performance Inspections (EPIs) for performance — predate SAS and carried over from the older oversight system; the DCT questions descend directly from them. You do not need to memorize the acronyms. The takeaway is structural: every DCT question is testing whether a safety attribute (covered next) is present and working in some part of your operation, and the evidence the inspector weighs is almost always a document.

The Six Safety Attributes SAS Questions Are Built On

The FAA defines safety attributes as the qualities present in a well-designed, safety-centered system and process — the things that help ensure repeatable safety performance. SAS Data Collection Tools are organized around six of them. Read them as a checklist the inspector is mentally running against each part of your operation: is there someone responsible, someone with authority, a written procedure, a control, a way to measure it, and managed interfaces?

Notice how directly the first two map to your management structure. Responsibility and Authority are, in effect, asking whether the right people are named, qualified, and actually empowered — which is exactly what the Part 119 required-management-personnel rules and your Part 5 SMS roles establish. If you want to see how that side of the house is built, our guides on required management personnel qualifications and the director of safety role under the SMS rule walk through the designations and the records that prove them.

What SAS Surveillance Really Examines: Your Records

Strip SAS down to what an inspector physically does, and a pattern emerges: the design questions are answered by your documents, and the performance questions are answered by your records. Is the procedure written into the manual? That is a document. Did the training actually happen, was the recurring inspection done on time, is the airworthiness directive complied with? Those are records. SAS is, in the day-to-day, a structured examination of your documentation — which is precisely why the operators who fare best under it are the ones whose records are continuously organized, dated, and producible, not the ones who scramble before an inspection.

That is a document-management capability, and it is exactly the layer FileFlo is built for. Below is the record set SAS data collection typically draws on, what each one proves, and where a compliance document intelligence platform helps. None of these documents is exotic — they are the same records a Part 135 operator is already required to keep.

The SAS-relevant record set

The same records discipline carries you through the adjacent oversight situations in this cluster. SAS sits behind a routine Part 135 surveillance audit, it informs what triggers an FAA audit, and it is the framework against which grey-area operations get scrutinized in the FAA illegal-charter crackdown — itself a question of whether you are operating under Part 91 or Part 135 (compensation or hire), and where the flight department company trap and business-jet ownership structure come into play. The broader oversight context — and how SAS fits the agency's overall framework — is laid out in this guide and the related Part 91 vs. Part 121 vs. Part 135 comparison.

Specific authorizations carry their own SAS-examined paperwork too. International operations bring a dedicated document set — see international operations documents and records and the Part 135 international operations requirements — and RVSM authorization is anchored in inspection records covered in RVSM altimeter and transponder inspection records and how to get RVSM authorization. And if an oversight finding ever moves toward action, the difference between a letter of correction, a warning, and an investigation — and how voluntary programs like ASAP, VDRP, and ASRS (including the NASA ASRS enforcement protection) fit — is worth understanding before, not during, the event.

Frequently Asked Questions