FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05FA184 · Bellanca 14-13-3

20 May 2005 · Caliente, CA, United States

Bellanca 14-13-3 · Accident: in flight encounter with weather en route

From Exeter Airport (O63) to Tehachapi Municipal Airport (TSP)

Report a problem

Event

NTSB case
LAX05FA184
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
Instrument Meteorological Cond

Bellanca 14-13-3

Aircraft type
Bellanca 14
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
N6511N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Exeter Airport (O63), Exeter, CATo Tehachapi Municipal Airport (TSP), Tehachapi, CA
Aircraft age
Not recorded
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 · cruise
First occurrenceThe 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
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › VFR flight into imc, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane impacted terrain while cruising in controlled flight (CFIT) after the pilot(s) reversed course upon encountering instrument meteorological conditions. Both of the pilots held commercial pilot certificates, but neither were instrument-rated. The flight was performed to relocate the airplane to the pilot-owner's home base airport. No witnesses to the accident were identified. Visual meteorological conditions existed at the departure airport beneath an overcast sky condition. Based on an evaluation of the weather conditions, the projected route between the departure and destination, and the impact heading of the airplane, and as the terrain elevation increased, the pilots most likely encountered less maneuvering room between the terrain and the overlying clouds, and they would have inadvertently entered instrument meteorological conditions. The pilots reversed course to a westerly direction and commenced flying back toward their departure airport. The underlying terrain was also obscured by clouds, and the airplane's clearance from the terrain was inadequate, resulting in a collision with mountainous terrain. A motorist, who held a private pilot certificate and was driving in a westerly direction near the accident site, reported that the roadway "was foggy" and his visibility was at most 1 mile. The motorist stated his elevation was about 3,000 feet mean sea level (msl). An examination of the accident site, elevation 2,380 feet msl, revealed the airplane impacted upsloping terrain while in a right bank, and with a near level pitch attitude. Thereafter, the airplane cart wheeled. The distance between the initial point of impact and the farthest component of wreckage was nearly 800 feet. No evidence of any preimpact mechanical malfunction was found.

Probable cause

The pilot's inadvertent encounter with instrument meteorological conditions and failure to maintain adequate terrain clearance, which resulted in controlled flight into the terrain. Contributing factors were the pilots' delayed decision to reverse course, the low clouds which obscured the rising terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05FA184
Event ID
20050601X00700
Case number
LAX05FA184
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 9daec1d11463866f37987a779604ab88000bcdb2aa7bc0405bb921b83315077d; retrieved 2026-09-20T18:02:50.113Z.