LAX92LA178 · Cessna 150G
Cessna 150G · Accident: in flight collision with object en route
From Sacramento Executive Airport (SAC) to Oakdale Airport (O27)
Event
- NTSB case
- LAX92LA178
- 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
- 0 · 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
- Visual Meteorological Cond
Cessna 150G
- Aircraft type
- Cessna 150
- 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
- N6213S
- Operator
- Haskell, Gregg Owen · private individual
- Onboard fatalities
- Unknown
- Route
- From Sacramento Executive Airport (SAC), Sacramento, CATo Oakdale Airport (O27), Oakdale, 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 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 › Altitude, improper
- Pilot in command › In-flight planning/decision, poor
Approximate · Estimated position: the centre of Galt, CA, the place the record names. Not the accident site.
NTSB narrative
THE AIRPLANE COLLIDED WITH SOME 25-FOOT TELEPHONE WIRES WHILE IN CRUISE FLIGHT. THE PILOT HAD WORKED 24-HOURS BEFORE DEPARTING ON THE ACCIDENT FLIGHT. AFTER DEPARTING THE AIRPORT, THE PILOT ENCOUNTERED HEADWINDS AND ELECTED TO DESCEND TO 500 FEET MEAN SEA LEVEL. DUE TO FATIGUE FROM THE LACK OF SLEEP AND INATTENTION, THE PILOT DESCENDED THE AIRPLANE SEVERAL HUNDRED FEET BELOW THE INTENDED ALTITUDE. AFTER THE PILOT LEVELED THE AIRPLANE, HE SAW THE TELEPHONE WIRES AND ATTEMPTED AN EVASIVE ACTION, BUT WITHOUT SUCCESS.
Probable cause
THE PILOT'S POOR IN-FLIGHT DECISION BY SELECTING AN IMPROPER CRUISE ALTITUDE. CONTRIBUTING TO THIS ACCIDENT WAS THE PILOT'S FATIGUE DUE TO LACK OF SLEEP.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX92LA178
- Event ID
- 20001211X14457
- Case number
- LAX92LA178
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1992-04-16.
- API snapshot SHA-256: 959b3e5c92f430ae2b71f2ae13214ea03d504c797afd25e3e42a132a61b34dfd; retrieved 2026-09-21T15:02:50.460Z.