Aviation Crash Map

Beechcraft A36 N364RM

25 October 2016 · Pittsburg, California, United States · Fatal

Summary

On 25 October 2016 at about 19:20 local time, a Beechcraft A36 registered N364RM was involved in an accident near Pittsburg, California, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 19:20
Classification
Accident
Location
Pittsburg, California, United States
Coordinates
37.9689, -121.8894
Aircraft
Beechcraft A36
Registration
N364RM
Category
Airplane
Year built
1995
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Concord → Concord
Aircraft damage
Destroyed
Weather
VMC
Light
Day
NTSB number
WPR17FA013

People

2 people died.

On board Died Serious Minor Uninjured
2 2 0 0 0

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full 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.

Quoted verbatim from the NTSB record.

Other Beechcraft A36 accidents

Date Aircraft Location Operator Outcome Died
12 Dec 2016 Beechcraft A36
N776WM
New Smyrna Beach, Florida, United States - Minor injuries -
11 Dec 2016 Beechcraft A36
N69286
Shoreham, New York, United States - No injuries -
17 Dec 2016 Beechcraft A36
N410BC
Ormond Beach, Florida, United States - Serious injuries -
31 Aug 2016 Beechcraft A36
N985CA
Sparks, Nevada, United States Flying Start Aero Fatal 2
31 Aug 2016 Beechcraft A36
N8283D
Bentonville, Arkansas, United States - Fatal 1
19 Feb 2016 Beechcraft A36
N61WB
Marshville, North Carolina, United States - Fatal 1

All 559 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
6 Oct 2016 Joe Salomone SUPER CUB SQ2
N786AB
Boca Reservoir, California, United States - No injuries -
12 Dec 2016 Cessna T210M
N761SZ
Mecca, California, United States - Serious injuries -
25 Aug 2016 Siai-Marchetti SF260
N16FD
Fullerton, California, United States Air Combat, USA Minor injuries -
15 Dec 2016 Bombardier CL 600 2B19
N986SW
San Francisco, California, United States Skywest Airlines Inc Unknown -
24 Aug 2016 Cessna 182
N4810N
Fallbrook, California, United States Civil Air Patrol Inc. Minor injuries -
8 Jul 2016 Cessna 172
N9488G
San Diego, California, United States - No injuries -

All 170,864 records in United States