May 28, 2027 Is Approaching

FAA Part 5 SMS: Flight Data Monitoring Support for Part 135 and §91.147 Operators

Existing FAA Part 135 certificate holders and covered 14 CFR (Code of Federal Regulations) §91.147 commercial air-tour operators must develop and implement a Safety Management System (SMS) that meets FAA Part 5 requirements by May 28, 2027. Existing Part 121 certificate holders were required to implement the revised Part 5 requirements by May 28, 2025.

‍Applicability note: The May 28, 2027 requirement does not apply to every Part 91 operator. It applies to covered §91.147 commercial air-tour operators holding a Letter of Authorization (LOA). Other Part 91 and Part 91K operators may participate voluntarily or may be subject to other requirements. Operators should confirm applicability with the FAA or qualified regulatory counsel.

Schedule an SMS Data-Readiness Assessment
FAA Part 5 SMS: Flight Data Monitoring Support for Part 135 and §91.147 Operators

Reliable Flight Data for Your Safety Management System

An effective SMS depends on timely operational information, documented hazard identification, risk assessment, safety-performance monitoring and evidence that corrective actions are working. Flight Data Technologies (FDT) helps automate the flight-data portion of this process, turning routine aircraft data into consistent, reviewable safety intelligence.

REQUEST DEMO
FAA Part 5 SMS: Flight Data Monitoring Support for Part 135 and §91.147 Operators
FAA Part 5 SMS: Flight Data Monitoring Support for Part 135 and §91.147 Operators
The FDT Solution

How FDT Supports Your FAA Part 5 SMS Framework

WQAR (uQAR) acquires the evidence

The Wireless Quick Access Recorder (WQAR/uQAR) captures available flight data from compatible Digital Flight Data Recorder (DFDR) or Flight Data Acquisition Unit (FDAU) installations and transfers it securely after landing. This reduces removable-media handling and manual collection.

XpressA processes available flight data

XpressA automatically decodes and validates received data, applies configured event definitions and generates analysis-ready reports. In a compatible, correctly configured deployment, reports may be available within 14 minutes after landing. Timing depends on connectivity, file size and configuration.

Automated event detection supports hazard identification

Detected deviations, recurring patterns and emerging operational concerns are identified for assessment within the operator's Safety Risk Management process.

Dashboards support Safety Assurance

Safety teams can monitor safety-performance indicators, event rates, trends and the effectiveness of risk controls across aircraft, bases and operating periods.

Pilot-performance tools support follow-up

Authorized analysts get graphs, maps, animation and review tools for debriefing, investigation and documented corrective action.

Predictive maintenance adds technical-risk insight

Developing aircraft-system trends that may affect reliability, operational continuity and safety can be identified, helping maintenance and safety teams coordinate earlier.
View Certifications & Approved Models
SMS Components

Support for the Four Components of SMS

Safety Policy

Controlled access, assigned responsibilities and repeatable data workflows can support documented safety objectives.

Safety Risk Management

Objective flight evidence can support hazard identification, risk analysis and the evaluation of proposed controls.

Safety Assurance

Operators can monitor operational performance, trends and recurring events, and preserve evidence for management review and oversight.

Safety Promotion

Analyzed events become focused feedback, training topics and safety communication for pilots, maintenance personnel and management.
IMPLEMENTATION PATH

A Practical Path to SMS Flight-Data Implementation

1. Assess

Review fleet recording capability, available parameters, current reporting processes, safety objectives and Part 5 implementation status.

2. Connect

Select the appropriate WQAR (uQAR) configuration and secure transfer method for supported aircraft.

3. Configure

Set event definitions, alert priorities, user roles, dashboards and reports around the operator's hazards and safety-performance indicators.

4. Validate

Confirm data quality, event logic, workflow responsibilities and reporting performance with representative flights.

5. Operate and improve

Use recurring reviews, trend monitoring and documented follow-up to strengthen the SMS over time.
REQUEST DEMO
FAA Part 5 SMS: Flight Data Monitoring Support for Part 135 and §91.147 Operators

Start Now, Before Implementation Becomes a Deadline Project

Data acquisition, aircraft integration, event configuration, internal responsibilities, validation and workforce adoption all require lead time. Starting now gives Part 135 and covered §91.147 operators time to establish a repeatable process before May 28, 2027.
Build Your SMS Data Implementation Plan
FAA Part 5 SMS: Flight Data Monitoring Support for Part 135 and §91.147 Operators