Turboprop records
Q400 landing gear AD and overhaul file evidence review for gear overhaul / transaction
This page scopes a records review for lessors, operators, CAMOs facing gear overhaul / transaction. Reviewers test gear-related AD/SB compliance records with method, date, overhaul reports, component replacement certs against the reported status and the configuration that will be delivered or operated. Discrepancies include missing certificates, wrong serial effectivity, weak task closure, date conflicts, and unsupported program assumptions. The buyer receives a register for commercial use and a record-by-record list for technical closeout.
When this review is needed
- Gear overhaul / transaction is approaching and the delivered records need a defensible acceptance position.
- The summary for Q400 landing gear AD and overhaul file cannot yet be tied to source documents.
- A prior shop, operator, or manager may need to supply replacement evidence.
- Commercial timing requires a short list of blockers and closeable gaps.
The problem
Records teams often inherit Q400 landing gear AD and overhaul file as a mix of scanned source pages, status exports, and old acceptance notes. The review rebuilds the chain around the event that matters for the current buyer.
What gets reviewed
- Review gear-related AD/SB compliance records with method against serial identity, date, cycle basis, configuration, and closure evidence.
- Cross-check date against serial identity, date, cycle basis, configuration, and closure evidence.
- Validate overhaul reports against serial identity, date, cycle basis, configuration, and closure evidence.
- Locate component replacement certs against serial identity, date, cycle basis, configuration, and closure evidence.
- Screen incident/hard-landing inspection write-ups against serial identity, date, cycle basis, configuration, and closure evidence.
- Document dispositions. against serial identity, date, cycle basis, configuration, and closure evidence.
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
- A status claim is accepted only after the underlying record supports the same event.
- Task closure is challenged if sign-off wording omits the referenced inspection, repair, or build data.
- Program or coverage statements are compared with logbook totals and transfer dates.
- Records filed under a donor asset are flagged until serial movement is proven.
- The final register keeps factual defects apart from presentation cleanup.
Evidence normally required
- Gear-related AD/SB compliance records with method
- Date
- Overhaul reports
- Component replacement certs
- Incident/hard-landing inspection write-ups
- Dispositions.
Common discrepancies
- Gear SBs recorded as terminated when only repetitive inspections were done, hard-landing checks signed without the referenced inspection data, overhaul exchange legs whose AD history was not carried over
What is at stake
If the review is skipped, the team may rely on a clean summary that fails under source-record review. The practical effect is extra shop queries, closing conditions, or a valuation adjustment tied to missing proof.
How the work runs
Frame Q400 Landing
Confirm the exact event, affected file set, buyer role, and decision standard before any gear-related ad/sb compliance records with method is treated as sufficient.
Trace Records Review
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort File Evidence
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Turboprop History
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- Discrepancy register with owner and due evidence
- Accepted-evidence bundle for the transaction file
- Technical questions for prior operator, shop, or manager
- Closeout tracker separating blockers from cleanup
Who uses the output
How the work fits into the transaction or program
Confirm a Q400's landing gear directive and service bulletin compliance history alongside overhaul status, on a type whose gear has a well-known AD/SB history and high-cycle regional duty; Evidence: gear-related AD/SB compliance records with method and date, overhaul reports, component replacement certs, incident/hard-landing inspection write-ups and dispositions. The evidence set centers on gear-related AD/SB compliance records with method, date, overhaul reports, and component replacement certs. The likely weak points are gear SBs recorded as terminated when only repetitive inspections were done, hard-landing checks signed without the referenced inspection data, overhaul exchange legs whose AD history was not carried over. Handoff: technical manager, gear overhaul / transaction, Q400 landing gear AD and overhaul file.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
For Dash 8 Q400, configuration, utilization, exchanged assemblies, and prior program control determine which documents matter most. The review keeps those model-specific issues separate from broad fleet assumptions.
Jurisdiction-specific considerations
Jurisdiction references are used as records criteria where they apply to the file. A release, inspection, or approval record from one system is not treated as automatic acceptance by another authority.
Regulatory limits
EE records findings describe support, gaps, and inconsistencies in the file. They do not certify the aircraft, engine, component, or modification, and final acceptance stays with the responsible authority and approved organization.
What this review does not cover
- Physical condition survey beyond records evidence
- Warranty administration or program claim filing
- Authority liaison unless separately contracted
Specific to this review
- Q400 landing gear AD and overhaul file is evaluated around q400 gear ad sb history verification, rather than a generic asset checklist.
- The first review target is the record line most likely to move value, availability, or acceptance timing.
- Serial continuity is tested separately from task completion because evidence can follow a different asset.
- A useful register preserves accepted evidence, disputed evidence, and missing evidence as separate outcomes.
- The scope uses the Q400 Landing Gear Records question as the control point, so the review stays tied to Gear overhaul / transaction and the buyer decision behind it.
- The evidence starts with Gear-related AD/SB compliance records with method and follows Review Overhaul File Evidence references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for technical manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Transaction Turboprop History Verification questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Discrepancy register with owner and due evidence; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
Transport Canada. Canadian airworthiness, maintenance records (CAR 605/571), and Airworthiness Directive requirements (CAR 593).
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Frequently asked questions
What makes this aircraft review different from a general file audit?
The scope is tied to q400 landing gear records and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block gear overhaul / transaction or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is gear-related ad/sb compliance records with method, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives technical manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.
Talk through the aircraft, records, evidence, deadline, and next useful step.