LAX90FA123 · Cessna 172N
Cessna 172N · Accident: in flight collision with object on approach
From Santa Barbara Municipal Airport (SBA) to Fullerton Municipal Airport (FUL)
Event
- NTSB case
- LAX90FA123
- 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
- 1 · all aircraft and ground
- Ground fatalities
- 0
- 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
Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N2985E
- Operator
- Nevitt, Dale M. · private individual
- Onboard fatalities
- Unknown
- Route
- From Santa Barbara Municipal Airport (SBA), Santa Barbara, CATo Fullerton Municipal Airport (FUL), Fullerton, 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 · IFR final approach
- 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 object
- 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
- Wire, transmission
- 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 › Minimum descent altitude, not maintained
Approximate · Estimated position: the centre of Buena Park, CA, the place the record names. Not the accident site.
NTSB narrative
FOR OVER ONE YEAR THE INSTRUMENT-RATED PILOT REGULARLY FLEW HIMSELF TO WORK BETWEEN HIS SANTA BARBARA HOME AND HIS BUSINESS OFFICE NEAR THE SANTA ANA AIRPORT (SNA). UPON APPROACHING SNA THE PILOT MADE AN ILS APPROACH, FOLLOWED BY A MISSED APPROACH. HE CLIMBED TO 2,500 FEET AND DIVERTED TO THE FULLERTON AIRPORT (FUL). THE PILOT WAS CLEARED FOR A VOR APPROACH AND RADAR SERVICE WAS TERMINATED AT THE FAF. THE PILOT DESCENDED ON THE PRESCRIBED TRACK TOWARD FUL BUT FAILED TO ARREST HIS DESCENT AT THE MDA, COLLIDED WITH POWER LINES AND TERRAIN 1.9 STATUTE MILES BEFORE THE AIRPORT. THE 65-YR-OLD PILOT'S MEDICAL CERTIFICATE HAD EXPIRED. THE PILOT HAD A RECENT HISTORY OF HYPERTENSION, AND AT AUTOPSY EVDIECNE WAS FOUND OF HYPERTENSIVE CARDIOVASCULAR DISEASE.
Probable cause
THE PILOT NOT MAINTAINING THE PRESCRIBED MINIMUM DESCENT ALTITUDE DURING AN INSTRUMENT APPROACH.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90FA123
- Event ID
- 20001212X22735
- Case number
- LAX90FA123
- 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. 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: 482fc100fa6c96cd696e56d4348dab6e3db132f3465fdd14971d22e4cfc59cc1; retrieved 2026-09-21T02:52:42.539Z.