Models

Beechcraft Bonanza Maintenance Records: Connect the Decades

By PlaneFacts · Updated October 30, 2026

A Bonanza’s maintenance history may span several owners, engines, avionics installations and sets of logbooks. The central task is continuity: establish which airplane and components the records describe, connect significant work to its supporting documents and identify what still needs explanation.

“Bonanza” is too broad a starting point for a technical review. A V35B, an A36 and a modified older Model 35 do not share one interchangeable set of configuration assumptions or directive requirements.

Begin with the exact model and serial number

Confirm the aircraft’s model and serial number, then identify the installed engine, propeller and significant modifications. Keep those details beside the directive and inspection status.

This matters even within a familiar family. FAA AD 94-20-04 R2 addresses specified V-tail models and distinguishes certain aircraft with a particular straight-tail conversion. It is not a generic requirement for every aircraft called a Bonanza. The published FAA directive shows why model, configuration and the specific applicability language must be read together.

Treat any directive examples in an article as review prompts, not a complete or current compliance list. The reviewing maintenance professional should establish the requirements applicable to the actual aircraft and its installed equipment.

Reconcile time across books and replacements

Create a chronology of the supplied airframe, engine and propeller records. Note the date span of each book and where one ends and the next begins. The general method is in how to read aircraft maintenance logbooks.

Look for explanations of tachometer replacements, engine exchanges, registration changes and reconstructed records. A reset meter reading should not be mistaken for a reduction in aircraft total time. An engine installation entry should connect the incoming engine’s identity and history to the airframe.

When a gap appears, classify it carefully:

• A missing scan may be resolved by obtaining the omitted page.
• A missing book may require a broader search through prior owners or shops.
• A period with few entries may reflect low activity, incomplete records or another explanation that has not yet been established.

FAA Advisory Circular 43-9D discusses lost or destroyed records and reconstruction. Reconstruction should be identified as such; it should not be presented as equivalent to an uninterrupted original history.

Give V-tail work its own review

For an applicable V-tail aircraft, read ruddervator repairs, refinishing, balancing and related control-system work together. Ask what was done, what maintenance data was referenced and where the supporting measurements or reports reside.

A fresh paint date is not a substitute for documentation of the associated control-surface work. Conversely, a balancing entry is not proof of damage. It establishes a specific maintenance action whose significance depends on the surrounding history.

The distinction between completed and recurring work also matters. AD 94-20-04 R2 includes both one-time actions and repetitive fuselage-bulkhead inspections for affected aircraft. An old compliance entry should be read against the actual requirement rather than treated as a permanent blanket clearance. FAA AD 94-20-04 R2.

Follow structural findings through to their resolution

Wing and carry-through records deserve a model-specific read. FAA AD 95-04-03 concerns the wing front spar carry-through frame structure of specified Beech aircraft. Its original Federal Register publication is a useful example of why “spar AD complied with” needs context.

For any applicable structural inspection, ask for the inspection date, aircraft time, findings, referenced procedure and subsequent repair or monitoring requirements. If a repair kit or structural modification is documented, connect the installation record to the supporting approval and any continuing instructions.

The same approach applies to corrosion findings: identify the location, recorded extent, corrective work and follow-up evidence. “Corrosion treated” may describe a small localized task or a more substantial event. The entry and supporting work order should establish which.

Connect landing-gear work to the event that prompted it

Landing-gear maintenance should form an understandable sequence: reported discrepancy, inspection or troubleshooting, parts or adjustments, and the documented return to service.

If a history includes a gear-up landing or propeller strike, gather the associated airframe, engine and propeller records rather than reading each in isolation. A replacement propeller entry alone does not establish why it was replaced. A stated event should lead to the documents describing the inspection and repair scope. See damage history in aircraft records for how to document an event and its repair.

The useful question is not whether the book contains many entries. It is whether the significant event and its resolution can be followed without unsupported assumptions.

Treat modifications as a current configuration file

Engine conversions, tip tanks, propeller changes and panel upgrades can accumulate over decades. For each significant alteration, look for the installation entry and applicable approval documents, operating supplements, continued-airworthiness instructions and weight-and-balance changes.

An STC establishes an approved design change; it is not, by itself, evidence that the change was installed on this particular airplane. Connect the design approval to the aircraft’s installation record. FAA AC 43-9D explains maintenance documentation and major-alteration records.

A useful handover file distinguishes equipment still installed from modifications later removed. That makes it easier for the next owner and maintenance shop to understand which instructions remain relevant.

Bonanza records questions

Do all Bonanzas have the same inspection and AD requirements?

No. Exact model, serial number, installed components and modifications affect applicability. V-tail-specific requirements should not be applied indiscriminately to straight-tail models, or vice versa.

Should an older Bonanza be rejected because a logbook is missing?

A missing book is a diligence issue to investigate, not a universal purchase verdict. Establish what period is missing, what can be reconstructed and whether required status information can be supported. Have the shop and transaction advisers assess the remaining uncertainty.

Does an engine conversion erase the older engine history?

It changes which engine is installed. The prior records may still explain an event or the reason for the conversion. Review the incoming engine’s history and the installation documentation separately from the airframe’s accumulated time.

Put the long history into a usable format

PlaneFacts organizes supplied maintenance records into a Summary and Full Report with links to supporting sources. A decades-long Bonanza history becomes easier to discuss when significant work, configuration changes and unresolved questions are presented consistently.

*A clear record history supports the next stage of diligence. It does not replace inspection of the aircraft or a qualified review of current compliance and condition.*

PlaneFacts reports support diligence. They do not establish current airworthiness or replace an aircraft inspection or a qualified maintenance review.