FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA013 · Beech A36 UNDESIGNAT

25 Oct 2016 · Pittsburg, CA, United States

Beech A36 UNDESIGNAT · Accident en route

From Buchanan Field (CCR) to Buchanan Field (CCR)

Report a problem

Event

NTSB case
WPR17FA013
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Beech A36 UNDESIGNAT

Aircraft type
Beechcraft 36
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N364RM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Buchanan Field (CCR), Concord, CATo Buchanan Field (CCR), Concord, CA
Aircraft age
About 21 years (built 1995)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · descent
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Not determined › Not determined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot and the pilot-rated passenger were making a local personal flight in the airplane in visual flight rules conditions so that the passenger could assist the pilot in becoming familiar with avionics components that had recently been installed. The new avionics components were upgrades of the previously-installed combination communication, ground-based navigation, and GPS navigation units. No flight testing of the airplane was conducted after the installation of the new avionics, nor was any required. The airplane was only flown once in the period between the avionics installation and the accident flight. That flight was conducted by the pilot who was the passenger on the accident flight and was uneventful.

According to acquaintances, both pilots were experienced in the accident airplane make and model. The pilots planned to fly to a practice area east of the airport, but the details of their plans were not known. Following a normal takeoff, the airplane began a turn to the east at an altitude of about 500 ft and climbed at a normal speed and rate for about 3 1/2 minutes. The airplane reached a maximum radar-indicated altitude of about 3,400 ft, where it leveled off for about 8 seconds. It then entered a descending left turn, and the descent rate and airspeed increased continuously. Analysis indicated that the average descent rate was about 5,000 ft per minute (fpm), and the maximum rate was about 10,000 fpm. During the descent, the speed increased from about 120 kts to nearly 250 kts, which was significantly above the airplane's never-exceed speed of 203 kts. During the descent, the pitch attitude decreased from about 5° airplane nose up to nearly 30° airplane nose down, and the total heading change was about 70°. The high descent rate, airspeed, and nose-down pitch attitude were consistent with an uncontrolled descent. About 30 seconds after the descent began, the airplane struck high-tension powerlines and then impacted terrain.

The airplane was highly fragmented by impact with the line, ground impact, and a post-impact fire altered or consumed much of the remaining structure and other evidence. All flight control surfaces were accounted for; however, flight control continuity could not be confirmed due to the extent of the damage.

No evidence of an in-flight fire or a bird strike was observed in the wreckage. Further, the two occupants were both capable of flying the airplane, any incapacitation would have had to affect both. Although ethanol was detected in the passenger's tissues, the levels varied widely, consistent with post-mortem ethanol formation; therefore, the ethanol did not contribute to the accident. Thus, it is unlikely that a flight control malfunction or failure or pilot incapacitation contributed to this accident.

It is possible the recent avionics installation may have resulted in physical control interference or mechanical failure; while no direct evidence of this was found, the condition of the wreckage precluded elimination of that possibility. Also, although there were no reports of any previous problem with the airplane's electronic flight control system, it is possible that an uncommanded or inadvertent control input via the autopilot or electric trim may have occurred and led to the loss of control. No direct evidence of an electronic flight control system malfunction was found; however, the condition of the wreckage precluded elimination of the possibility.

Probable cause

A loss of airplane control for reasons that could not be determined due to the extensive impact and fire damage to the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA013
Event ID
20161025X71815
Case number
WPR17FA013
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 1f63f2f4a5324f66556be3b836f64aa997fc935294b55d6e8310e90f7259e0cf; retrieved 2026-09-14T22:01:41.689Z.