Models
Daher TBM Maintenance Records: Read the History of the Aircraft You Are Buying
A useful TBM records review begins by identifying the certified model, marketing designation, serial number and installed engine. Then it connects inspection status, engine and propeller histories, equipment changes and significant repairs to their supporting documents.
“TBM” covers aircraft with different configurations and maintenance histories. A checklist built around one generation can send a reviewer looking for the wrong equipment—or applying the wrong maintenance assumptions to another.
Resolve the model names before reviewing the maintenance
The name on the sales listing may differ from the model name in official documents. For example, Canada's Transportation Safety Board identifies the TBM 910 as a production name for the TBM700 N. Its description also explains the relationship to the TBM 850 and TBM 900. A record bearing “TBM700 N” therefore does not automatically conflict with a listing for a TBM 910. TSB aircraft identification and model history.
Engine generation is another important boundary. The TBM 850 described by the TSB uses the PT6A-66D; Daher identifies the TBM 960 with the PT6E-66XT and its digitally integrated engine-and-propeller control system. Those are not interchangeable descriptions of the same installation. Daher TBM 960.
Create an identity sheet before drawing conclusions:
| Identifier | Why it belongs in the review |
|---|---|
| Certified model and marketing designation | Reconciles registry, manual and sales terminology |
| Airframe serial number | Helps determine the applicable documentation and configuration |
| Engine model and serial number | Connects the installed engine to its own records |
| Propeller model and serial number | Identifies the actual assembly and its history |
| Avionics and installed options | Establishes which capability claims apply to this aircraft |
Use the aircraft's actual records and current technical publications to resolve uncertainty. Do not substitute a newer TBM's brochure for an older airplane's equipment list.
Reconcile the inspection schedule with completed work
Ask for the current maintenance-status report and the records supporting significant completed items. For each upcoming event, identify the applicable basis: calendar date, operating time, cycles, or a combination.
The key question is not simply “Was the last inspection done?” It is “What inspection was performed, under which applicable program, and what remains due?”
An entry may reference a work order containing numerous tasks. Obtain that work order when it is needed to understand findings or closures. Where a tracking report and a signed entry disagree, have the maintenance provider resolve the discrepancy rather than choosing the more favorable date.
Daher's MyTBM portal provides technical-publication support and upgrade information. It also publishes model-specific service information. This is a better starting point for checking applicability than an unsourced maintenance schedule copied between listings. MyTBM technical support and publications.
Follow engine work beyond the headline
For each major engine visit, look for the reason for removal or inspection, engine identity, recorded time, findings, work performed and release documentation. Include available trend-monitoring or related reports when they are part of the supplied history.
Keep these questions separate:
- What work was performed?
- What did the shop find?
- What component time or life remains documented?
- What is next under the applicable maintenance instructions?
- What, if anything, is covered by a maintenance agreement?
The TBM 960's PT6E-66XT illustrates why model specificity matters. Pratt & Whitney describes a distinct digital control architecture and maintenance features for that engine. A review should use the instructions and status applicable to that installation, not assume that a PT6A-powered TBM's schedule carries over. Pratt & Whitney PT6E-66XT fact sheet.
Give upgrades their own paper trail
A TBM may have accumulated substantial equipment changes over its service life. Review an upgrade as a sequence: original configuration, installation, approval documentation, equipment and weight-and-balance changes, applicable supplements, and subsequent maintenance.
For avionics, distinguish installed hardware from advertised functionality. For the propeller, identify the actual hub and blade configuration instead of relying on a blade count in a photograph. For emergency automation or other advanced features, confirm their presence on the specific aircraft.
The same discipline applies to repairs. A short log entry may point to a detailed engineering or shop package. Bring that package into the review before deciding what the entry means for purchase negotiations or inspection scope.
Read support-program claims as contract questions
A listing's reference to a maintenance program should lead to the current agreement and written status confirmation. Ask which aircraft or engine is enrolled, which owner is covered, what remains available, and what transfer conditions apply.
Daher describes its Total Care Maintenance Program with defined eligibility, duration and exclusions. Those distinctions are why a buyer should not assume that an earlier owner's benefits accompany a used aircraft unchanged. Daher maintenance-program information.
Program coverage and completed maintenance answer different questions. Keep the agreement, payment or enrollment status, actual work records and next-due schedule distinguishable in the diligence file.
What makes a TBM history ready for a decision?
The basic logbook-reading workflow applies here, with special attention to the TBM's configuration and component identities. A useful review allows an owner, broker or inspecting shop to answer:
- Which aircraft and installed components do these records describe?
- Which inspections and major maintenance events are supported?
- Which upgrades or repairs need a closer look?
- Are important work packages or periods missing from the supplied set?
- What needs specialist verification before purchase or continued operation?
Missing evidence should be described precisely. “Engine shop report referenced in the June entry was not supplied” is more actionable than “incomplete logs.” It also avoids implying that work was never performed simply because an attachment is absent. The same precision helps when presenting documented maintenance to support aircraft value.
Common questions
Why might a TBM 910's records say TBM700 N?
Certified model designations and marketing names can differ. Reconcile them using the aircraft's serial number and identification documents; a name difference alone does not establish a records error.
Can I compare two TBMs using engine hours alone?
No. Compare engine identity, documented shop work, component status, applicable upcoming maintenance and any support agreement. The same number of hours can sit within materially different histories.
Does a maintenance-tracking report replace the underlying logbooks?
Use it to organize the review and identify due items. For important conclusions, follow the listed event back to the supporting maintenance entry and work package, and resolve discrepancies with the responsible provider.
Make the history easier to review. PlaneFacts brings supplied TBM records into a consistent Summary and Full Report, with supporting sources and questions for the next stage of diligence.
Frequently asked questions
Why might a TBM 910's records say TBM700 N?
Certified model designations and marketing names can differ. Reconcile them using the aircraft's serial number and identification documents; a name difference alone does not establish a records error.
Can I compare two TBMs using engine hours alone?
No. Compare engine identity, documented shop work, component status, applicable upcoming maintenance and any support agreement. The same number of hours can sit within materially different histories.
Does a maintenance-tracking report replace the underlying logbooks?
Use it to organize the review and identify due items. For important conclusions, follow the listed event back to the supporting maintenance entry and work package, and resolve discrepancies with the responsible provider. Make the history easier to review. PlaneFacts brings supplied TBM records into a consistent Summary and Full Report, with supporting sources and questions for the next stage of diligence.
PlaneFacts reports support diligence. They do not establish current airworthiness or replace an aircraft inspection or a qualified maintenance review.