FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18FA139 · Beech 76

10 May 2018 · Julian, CA, United States

Beech 76 · Accident: controlled flight into terrain/object (CFIT) while maneuvering

From Apple Valley Airport (APV) to Gillespie Field (SEE)

Report a problem

Event

NTSB case
WPR18FA139
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
3 · 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 76

Aircraft type
Beechcraft 76
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
N803FC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Apple Valley Airport (APV), Apple Valley, CATo Gillespie Field (SEE), SAN DIEGO/EL CAJON, CA
Aircraft age
About 39 years (built 1979)
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
Maneuvering
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
Controlled flight into terrain/object (CFIT)
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

During the 2-hour nighttime visual flight rules instructional cross-country flight, radar data identified the airplane on an easterly flight track when the first of two maneuvers over mountainous terrain was initiated. The first maneuver was a left turn from about a 48° course heading to about a 176° course heading. Throughout the turn, the airplane's altitude remained about 5,600 ft mean sea level (msl), and the groundspeed decreased to 55 knots. At the completion of the turn, the groundspeed increased to about 67 knots, and the airplane began to climb to 6,600 ft msl while continuing to the southwest on a course heading of about 195°. The airplane then made a right turn course reversal and resumed the easterly heading for about 10 miles.

The radar data then depicted the airplane initiated a second left 180° turn maneuver at an altitude of 6,200 ft msl and a groundspeed of about 121 knots. At the apparent apex of the turn, the airplane was at 6,100 ft msl and a groundspeed of 50 knots. The airplane then began to descend, and the groundspeed increased to 74 knots and then decreased to 50 knots. The last radar return showed the airplane at an altitude of 5,700 ft msl and a groundspeed of 67 knots near the accident site. Radar data revealed that both maneuvers were similar except that the second maneuver began over higher elevation terrain. The airplane's separation from the terrain during the second maneuver was as low as 1,200 ft above ground level (when the airplane was at an altitude of 6,100 ft and was over terrain that was 4,900 ft) before radar contact was lost.

Weather reporting in the aera of the accident site indicated extreme turbulence and severe up and downdrafts during high wind conditions. Although there is evidence of strong wind in the area at the time of the second maneuver, there is no consensus among the available wind data. However, the upset occurred immediately downwind of relatively high terrain and inside of a temperature inversion, which can promote wave action and turbulence. Thus, the airplane likely encountered a downdraft and the pilot was unable to recover, resulting in the airplane's subsequent impact with terrain.

The operator reported that the instructor was newly hired to the flight school and that the accident flight was his first instructional flight with the company. The course syllabus for the flight identified that several tasks were to be accomplished. A representative of the operator reported that maneuvers were usually performed to facilitate a 2-hour flight. All flight was prohibited below 500 ft agl and minimum cruise altitude of 2,000 ft agl in mountainous terrain. No flight plan had been filed for the nighttime flight, and any en route flight planning documentation was destroyed in the postimpact fire; thus it could not be determined if the pilot or the flight instructor were aware of the weather conditions or terrain elevations while performing the maneuvers.

Probable cause

The pilot's failure to maintain sufficient altitude above mountainous terrain while maneuvering during night conditions in an area prone to turbulence, which resulted in a collision with terrain. Contributing to the accident was the flight instructor's decision to conduct maneuvers over mountainous terrain at night, and failure to ensure that the maneuver was conducted with sufficient separation from terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18FA139
Event ID
20180511X43419
Case number
WPR18FA139
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-05-11.
  • API snapshot SHA-256: 5338a449c2ccf80a024bf968b5e7a7d54fa136ebfa40dcb9b6f07180a60a4564; retrieved 2026-09-15T06:40:25.447Z.