The Complete Part 135 Compliance Checklist for Charter Operators (2026)

A Part 135 compliance checklist gives your operation a repeatable control system for audit readiness. The first thing most inspectors notice is whether your records are organized and current, not whether your team can explain policy from memory.

For many charter operators, risk accumulates quietly: one recurrent training event is overdue, one medical certificate is filed in the wrong location, one revision to the General Operations Manual never reaches line pilots. A checklist catches these misses early.

If you are building your baseline process, start with our guide on how to prepare for FSDO audit, then operationalize each line item inside Navlyt Compliance.

Your training file must show initial and recurrent events by role, aircraft category, and date. Inspectors typically verify 135.293 competency checks, 135.297 instrument proficiency, and 135.299 line checks first because they directly connect to operational authority.

Build one row per pilot and one column per required event with due date logic. Include examiner credentials and references to check forms so each event can be validated in minutes, not hours.

Your GOM and any associated manuals must align with current operations, approved procedures, and actual crew behavior. The mismatch between written policy and day-to-day practice is one of the fastest ways to trigger findings.

Maintain revision history, distribution logs, and acknowledgement evidence. If you are unsure which sections are commonly missed, review aviation operations manual requirements.

Aircraft records should prove required inspections, AD compliance, MEL usage controls, and any deferred maintenance documentation. Auditors need traceability from discrepancy to closure.

Cross-check aircraft status with scheduled trips in Navlyt TripDesk for charter operators so dispatch cannot assign aircraft with unresolved blockers.

Crew records should include license copies, medical certificates, training completions, and route or equipment qualifications where applicable. Treat file naming and indexing as a safety control, not administrative overhead.

A centralized evidence trail is the difference between spending ten minutes and two days answering an inspector request.

Your testing program should show policy, random testing methodology, vendor documentation, and event logs for post-accident or reasonable-suspicion cases. Gaps often occur when ownership sits across multiple departments.

Schedule quarterly internal reviews and include policy acknowledgement renewals as recurring compliance tasks.

Emergency equipment checks are easy to overlook because they are operationally routine. During inspections, however, they quickly reveal whether your control system is active.

Track inspection intervals and expiration evidence with the same rigor you apply to pilot checks.

Use this article as your operating framework, then download the gated 2026 checklist from the sidebar to run monthly internal reviews with your DO, Chief Pilot, and maintenance lead.

When your team is ready, start a 14-day free trial on the pricing page and map every checklist line to tasks, evidence, and deadlines in Navlyt.