Authority readiness
Regulatory-surveillance records preparation for an authority review
Regulatory-surveillance records preparation gets an aircraft's maintenance records ready for an authority's surveillance review, ramp check, or scheduled audit of the operator. It is run by or for a lessor, airline, operator, or management company facing a planned or recurring inspection by its oversight authority. It covers the records the rules require an operator to hold, their retrievability, AD compliance evidence, release-to-service entries, and the consistency between status reports and the entries behind them. You receive an organized records package mapped to the regulatory record requirements, a register of gaps an inspector would raise, and a path to close each before the review.
When this review is needed
- An oversight authority has scheduled a surveillance audit of the operator and its records will be sampled.
- A recurring audit cycle is approaching and prior reviews raised records findings that must not recur.
- A ramp inspection program is active and the aircraft must be able to produce required records on demand.
- An airworthiness review is due and the records that the review will rest on need confirming first.
- A new aircraft entered the operator's certificate and its records must align with the operator's approved system.
The problem
An inspector samples records and expects each one to be present, retrievable, and consistent with the status the operator reports. Records are scattered across systems, prior operators, and storage formats, and a status report can read clean while the entry that supports it cannot be produced in the time an inspection allows. A missing release entry, an AD whose compliance evidence is filed somewhere else, or a retention gap reads as a finding even when the underlying maintenance was done correctly.
What gets reviewed
- The records the applicable rules require the operator to hold and retain
- Retrievability of each required record within an inspection timeframe
- Airworthiness Directive compliance with accomplishment and method evidence
- Release-to-service and return-to-service entries for accomplished work
- Maintenance program status and the reports an inspector will sample
- The airworthiness review documentation where the system requires it
- Consistency between status reports and the source entries behind them
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
- Each record the rules require the operator to hold is present and can be retrieved promptly
- AD compliance is supported by accomplishment evidence showing the method and the recurring terms
- Accomplished work carries a valid release-to-service entry by an authorized person or organization
- Status reports the inspector will sample reconcile with the underlying maintenance entries
- Record retention meets the period the applicable rule sets for each record type
- The maintenance program reflected in the records matches the operator's approved program
- Airworthiness review or equivalent documentation is current where the system requires it
Evidence normally required
- The operator's record-keeping requirements and applicable retention rules
- AD and SB status with accomplishment references
- Release-to-service and work-order documentation for recent accomplishments
- Status reports the audit is expected to sample
- The airworthiness review documentation if applicable to the system
- Findings from any prior surveillance to confirm closure
Common discrepancies
- A required record that cannot be retrieved within the inspection timeframe
- AD compliance evidence stored apart from the status, so the status cannot be substantiated on demand
- A release-to-service entry missing or incomplete for accomplished work
- A status report that disagrees with the entry an inspector would trace it to
- A record type held for less than its required retention period
- A prior surveillance finding that was reported closed but is not evidenced in the records
What is at stake
A finding in surveillance lands on the operator, can widen the scope of the review, and may carry corrective-action obligations and follow-up audits. Records that cannot be produced on demand draw the same conclusion as records that do not exist, and a poor review affects the operator's standing with its authority well beyond the aircraft in front of the inspector.
How the work runs
Map the requirements
Set the operator's required records and retention obligations against the authority that will conduct the review.
Confirm presence and retrieval
Verify each required record is present and can be produced within an inspection timeframe, building a retrievability index.
Substantiate the status
Reconcile the status reports the audit will sample to their accomplishment, release, and AD evidence.
Close gaps before the review
Register each likely finding with its location and a closure path so it is resolved while the operator controls the timeline.
What the buyer receives
- A records package organized and mapped to the regulatory record requirements
- A gap register listing each item an inspector would raise with its location and evidence
- A closure path for each gap with the responsible party and the record needed
- A retrievability index so any sampled record can be produced quickly during the review
Who uses the output
- Continuing-airworthiness and quality staff presenting records during the review
- Compliance leadership confirming the operator is ready for the audit
- Records teams closing gaps before the inspector arrives
How the work fits into the transaction or program
Preparation runs before the authority's review so gaps are closed while the operator still controls the timeline rather than discovered during sampling. It feeds the operator's audit readiness and leaves a retrievability index the records team keeps using afterward.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
What an inspector samples and which records are mandatory differ between authorities, so preparation is set against the specific system overseeing the operator. A record acceptable under one authority's requirements may be expected in a different form under another, and the preparation maps to the authority actually conducting the review.
Regulatory limits
Preparation organizes and checks records for an authority review and identifies likely findings in advance. It does not represent the operator to the authority, conduct the surveillance, issue any approval, or guarantee the outcome of the review.
What this review does not cover
- Representing the operator before the authority during the surveillance
- Issuing any release, approval, or airworthiness determination
- Performing the maintenance behind a missing release entry
Specific to this review
- An inspector treats a record that cannot be produced in the inspection timeframe the same as one that does not exist, so retrievability is checked as its own requirement.
- Surveillance samples the records, so the preparation tests whether sampled status reports reconcile to their source entries rather than only whether the maintenance was done.
- Closure of a prior finding has to be evidenced in the records, because reporting it closed is not the same as showing the inspector where the closure lives.
Sources
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Is this the same as the authority's surveillance itself?
No. The authority conducts its own surveillance. This preparation is the operator's own readiness check beforehand, so records are present, retrievable, and consistent before an inspector samples them.
Can you attend the review for us?
The preparation organizes and tests the records and identifies likely findings. Representing the operator to its authority during the review stays with the operator and its accountable staff.
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.