The U.S. aircraft register, updated daily
Accidents · NTSB WPR15FA222 · Final report

Beech F35 accident near Riverside, California, July 27, 2015

On July 27, 2015, a 1955 Beech F35, registered N988RH, was destroyed in an accident during maneuvering near Riverside, California (Riverside Muni airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 27, 2015
Place
Riverside, California · Riverside Muni · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Beech F35 NO SERIES, built 1955 · all F35s on the register
Registration
N988RH · no longer on the register · serial D-4131
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of engine power (total) during maneuvering defining event
  2. Off-field or emergency landing during maneuvering
  3. Collision with terrain or object (not controlled flight into terrain) during maneuvering

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 415 hours in all
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 609.4 hours
  • Last inspection: 100-hour inspection, October 14, 2014; 1,497 hours since
  • Maximum gross weight: 2,754 lb
  • Landing gear: retractable
  • Engine: Continental Motors E225-8 (piston); 0 hours total

The flight

  • Departed from: POC La Verne CA at 11:19 pm
  • Destination: RAL Riverside CA
  • Flight plan: none
  • Runway 27, 5,401 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 290° at 12 knots, gusting 19
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 86°F (30°C), dew point 61°F (16°C)
  • Altimeter: 29.87 inHg
  • Observation at 11:53 pm from KRAL, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR15FA222.