LAX02FA251 · Aero Commander 690A
Aero Commander 690A · Accident: in flight collision with terrain/water on approach
From Oakland San Francisco Bay Airport (OAK) to Eastern Sierra Regional Airport (BIH)
Event
- NTSB case
- LAX02FA251
- 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
- 4 · 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
Aero Commander 690A
- Aircraft type
- Aero Commander 690
- 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
- N690TB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Oakland San Francisco Bay Airport (OAK), Oakland, CATo Eastern Sierra Regional Airport (BIH), Bishop, 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
- Approach · VFR pattern base
- 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 collision with terrain/water
- 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, inadequate
- Pilot in command › Proper descent rate, not obtained/maintained
- Pilot in command › Visual/aural perception
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot entered the left-hand traffic pattern at an uncontrolled airport on a dark moonless night. Witnesses reported observing the airplane in a left descending turn. As the airplane turned onto the base leg, its left bank angle suddenly became steep. The airplane rapidly descended until colliding with level desert terrain 1.63 nm from runway 30's threshold. There were no ground reference lights in the accident site area. An examination of the airplane structure, control systems, engines, and propellers did not reveal any evidence of preimpact malfunctions or failures. Signatures consistent with engine power were found in both the engines and the propellers. The wreckage examination revealed that the airplane descended into the terrain in a left wing and nose low attitude. Fragmentation evidence, consisting of the left navigation light lens and left propeller spinner, was found near the initial point of impact. The wreckage was found principally distributed along a 307- to 310-degree bearing, over a 617-foot-long path. The bearing between the initial point of impact and the runway threshold was 319 degrees. The pilot's total logged experience in the accident airplane was 52 hours, of which only 1.6 hours were at night. The pilot was familiar with the area, but he had made only two nighttime landings within the preceding 90 days. Review of the recorded ATC communications tapes did not reveal any evidence of pilot impairment during voice communications with the pilot.
Probable cause
The pilot's failure to maintain an appropriate terrain clearance altitude while maneuvering in the traffic pattern due to the sensory and visual illusions created by a lack of ground reference lights and/or terrain conspicuity, and the dark nighttime conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02FA251
- Event ID
- 20020819X01425
- Case number
- LAX02FA251
- 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: f255ae48f7c854d7ec6ab1fcd305c65bb391fd52666f0e67752a1cdd1ba4b87c; retrieved 2026-09-20T19:55:10.763Z.