How to Survive an FAA Surveillance Visit Under the New SAS System

The Safety Assurance System (SAS) is the FAA's data-driven approach to oversight of Part 135 (and other certificate holder) operations. It replaced the older Air Transportation Oversight System (ATOS) approach for Part 135.

SAS uses risk indicators from multiple data sources — accident/incident reports, enforcement history, operational complexity, fleet changes, and surveillance findings — to prioritize which operators receive surveillance and what areas are examined.

SAS surveillance can be triggered by: incident or accident history, enforcement actions, certificate changes (fleet additions, new OpSpecs), ramp check findings, pilot deviations, ASRS reports, and scheduled routine surveillance cycles.

Operators with clean records and stable operations may receive less frequent surveillance, while operators with risk indicators receive more targeted attention. This is a fundamental shift from calendar-based to risk-based oversight.

Under SAS, inspectors follow structured work programs — not free-form inspections. Each work program targets specific operational areas based on the risk indicators that triggered the surveillance.

This means inspectors arrive with specific questions and data requirements. They are not browsing — they are investigating particular operational areas. Your preparation should focus on the areas most likely to trigger risk indicators in your operation.

The shift to data-driven surveillance means continuous readiness replaces periodic preparation. You cannot predict exactly when surveillance will occur or what area will be examined.

Maintain your compliance data in a readily accessible, organized format at all times. Use Navlyt Compliance to keep all compliance tasks, evidence, and corrective actions current and retrievable.

Conduct quarterly internal audits mimicking SAS work program structure. This builds organizational muscle for responding to surveillance efficiently and confidently.