Part 135 operators
Part 135 operator records-readiness review
A Part 135 records-readiness review checks that an on-demand or commuter operator's maintenance records satisfy the recordkeeping the rule requires before surveillance, a transaction, or adding a tail to the certificate. It is run by or for the operator ahead of an event that scrutinizes the records. It covers AD and inspection status, the maintenance program in use, life-limited and time-controlled component status, and the retention the operator must hold. You receive a readiness assessment, a gap list against the recordkeeping requirement, and the evidence needed to close each item.
When this review is needed
- Surveillance is expected and the operator wants records confirmed against the recordkeeping requirement first.
- A tail is being added to the certificate and its history has to fit the operator's program.
- The operation is being bought or sold and records readiness affects the value.
- A mixed fleet has drifted and the operator wants a consistent read across tails.
The problem
Part 135 operators often run mixed fleets on varied programs with leaner records staff than an air carrier. Inspection status, AD compliance, and component control can be tracked differently from tail to tail, and the recordkeeping requirement is easy to drift from when the same small team covers many aircraft and operating demands.
What gets reviewed
- AD compliance status with accomplishment evidence across the fleet
- Per-tail inspection records and the current return-to-service basis
- The maintenance program in use and its consistency across the fleet
- Life-limited and time-controlled component status
- The recordkeeping retention the operator must hold
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- The records present the content 135.439 requires the operator to keep
- AD compliance is supported by accomplishment evidence with the method recorded
- Recorded inspection status and the program in use agree per tail
- Time-controlled components show status consistent with the maintenance program
- Tracking practice is consistent enough across the mixed fleet to compare tail to tail
Evidence normally required
- Airframe and engine logbooks or digital records per tail
- Current AD status and accomplishment records
- The maintenance program documents in use
- Inspection records and recent return-to-service entries
Common discrepancies
- AD compliance tracked inconsistently across a mixed fleet
- A tail whose program in use does not match its inspection status
- Time-controlled component status that cannot be reconciled to the program
- A retention gap on an aircraft recently added to the certificate
What is at stake
Records that fall short of the requirement expose the operator at surveillance and weaken a sale of the operation. Adding a tail whose history does not fit the program creates a mismatch that surfaces at its first inspection under the certificate.
How the work runs
Set the standard per fleet
Establish the recordkeeping content and the program each tail must demonstrate.
Check status to evidence
Confirm AD, inspection, and component status against the logbooks and program.
Compare across tails
Identify where mixed-fleet tracking diverges from the requirement.
List the gaps
Record each shortfall per tail and the evidence that closes it.
What the buyer receives
- A readiness assessment against the recordkeeping requirement
- A gap list per tail with the evidence needed to close each item
- A consistency view of program and inspection status across the fleet
Who uses the output
- Operators confirming the fleet will hold up at surveillance or a deal
- Continuing-airworthiness teams aligning a newly added tail with the program
- Asset and buyer teams reading records readiness into the value of the operation
How the work fits into the transaction or program
The review takes a fleet-wide read before the event that will test it, then narrows to the tails that drift from the program. Its per-tail gap list drives the corrections that clear surveillance, support a sale, or settle a newly added aircraft onto the certificate.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Regulatory limits
The review measures the records against the recordkeeping the rule requires the operator to keep. It does not conduct surveillance, return any aircraft to service, or make an airworthiness determination across the fleet.
What this review does not cover
- Physical inspection or return-to-service of any tail
- Authoring or revising the operator's maintenance program
- Any airworthiness determination on the fleet
Specific to this review
- Mixed Part 135 fleets often run different programs per tail, so the review checks consistency across aircraft alongside per-aircraft completeness.
- Leaner records staffing makes drift from the recordkeeping requirement gradual and easy to miss until surveillance.
- A newly added tail is the most common source of a retention gap, because its history was built under a different operator.
Sources
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
How does this differ from a Part 121 records review?
The recordkeeping content and retention follow the Part 135 rule, and the typical fleet is more mixed and leaner-staffed. The review pays particular attention to consistency across tails that run different programs.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Walk through your situation with an engineer who has done this work.