Aviation Crash Map

Beechcraft F35 N988RH

27 July 2015 · Riverside, California, United States · Fatal

Summary

On 27 July 2015 at about 00:04 local time, a Beechcraft F35 registered N988RH was involved in an accident near Riverside, California, United States. One person was on board and one 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 00:04
Classification
Accident
Location
Riverside, California, United States
Nearest airport
Riverside Muni (RAL)
Coordinates
33.9444, -117.4336
Aircraft
Beechcraft F35
Registration
N988RH
Category
Airplane
Year built
1955
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
La Verne → Riverside
Aircraft damage
Destroyed
Weather
VMC
Light
Day
NTSB number
WPR15FA222

People

1 person died.

On board Died Serious Minor Uninjured
1 1 0 0 0

Probable cause

The total loss of engine power for reasons that could not be determined during postaccident examination of the airplane and engine. Also causal to the accident was the pilot's decision to attempt to reach the farthest runway and land into the wind instead of conducting a crosswind or downwind landing at a closer runway following the loss of engine power.

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

Read the full NTSB narrative

The private pilot was receiving vectors for an instrument landing system approach during daytime visual flight rules conditions when he advised the controller that the engine had lost power and that he needed to land at a nearby airport located northeast of his position. The controller responded with the distance and direction from the airport and asked the pilot if he had the airport in sight, which he acknowledged. The controller advised the pilot to proceed inbound to the airport, told him that he could land on the runway of his discretion, and asked him to tell him which runway he was going to use; however, the pilot only responded that he was going to land into the wind. The controller repeated that the runway was at his discretion and the pilot repeated that he was going to land into the wind. Shortly after, the controller provided the pilot with the current weather conditions at the airport, which included wind from 280° at 12 knots gusting to 18 knots, and he then cleared the pilot to land on runway 27. Subsequently, the pilot responded that he was not going to make it to the airport. No further radio communications were received from the pilot. Review of recorded radar data revealed that, when the pilot initially reported the loss of engine power, the airplane was about 1,644 ft above ground level; traveling on a heading of about 094°; and about 1.65 nautical miles (nm) west-southwest from the approach end of runway 34, 1.74 nm southwest of the approach end of runway 9, and 2.3 miles southwest of the approach end of runway 27. The radar data showed the flight track of the airplane continued on an easterly heading until it was about 0.96 nm south of runway 27 and about 653 ft above ground level. The airplane then turned left to a northerly heading while continuing to descend until radar contact was lost. Postaccident examination of the airplane revealed that the landing gear were in the extended position and that the wing flaps were extended to about 20°. A postimpact fire and impact damage precluded a determination of the fuel quantities in all three fuel tanks. The engine test run did not reveal evidence of any preexisting anomalies that would have precluded normal operation. The reason for the loss of engine power could not be determined. The Pilot's Operating Handbook for the accident airplane states that the maximum glide configuration includes landing gear and flaps up, cowl flaps closed, propeller low rpm, with an airspeed of 105 knots. With this configuration, the glide distance is about 1.7 nm per 1,000 ft of altitude above the terrain. It is likely that, if the airplane had been properly configured for a maximum glide distance and if the pilot decided to turn directly toward runway 34 or runway 9, for a downwind or crosswind landing, the airplane would have been able to reach either of those runways.

Quoted verbatim from the NTSB record.

Other Beechcraft F35 accidents

Date Aircraft Location Operator Outcome Died
10 Jun 2015 Beechcraft F35
N4224B
Everett, Washington, United States - Fatal 1
30 Mar 2016 Beechcraft F35
N4212B
Long Island, North Carolina, United States - Minor injuries -
7 Feb 2018 Beechcraft F35
PT-AVO
Itaituba, Brazil Conal Construtora Nacional de Avioes Ltd Fatal 3
27 Jul 2010 Beechcraft F35
N3858B
Enid, Oklahoma, United States - No injuries -
24 Dec 2010 Beechcraft F35
N3448B
Syracuse, New York, United States - No injuries -
5 Jul 2020 Beechcraft F35
N4219B
Ravenna, Texas, United States - Minor injuries -

All 139 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
26 Dec 2015 Boeing 737 76N
N7733B
San Diego, California, United States Southwest Airlines Co Serious injuries -
9 Jun 2015 Grumman Acft Eng Cor-Schweizer G 164A
N8372
Bakersfield, California, United States Nelson Kenneth D No injuries -
1 Feb 2015 Robinson R44 II
N510KJ
Calexico, California, United States John Reed Aviation No injuries -
14 Apr 2015 Robert C Hanson PITTS S2E
N75BH
Lebec, California, United States - Fatal 1
17 Apr 2015 Piper PA 18-150
N162SC
La Quinta, California, United States - Minor injuries -
18 Apr 2015 Cessna 206H
N3535M
Redding, California, United States McClelland Aviation Inc Fatal 1

All 170,864 records in United States