- Date
- February 18, 1980
- Place
- Columbus, GA · COLUMBUS, GA
- Injuries
- 1 uninjured
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N45384Cessna 150
- Status
- Completed · report July 14, 1980
- Report
- Brief approved by the director
- FAA report
- 19800218002909A
- Case key
- 134877
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-0940 80/2/18 COLUMBUS,GA CESSNA 150 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 25, 119 TIME - 1820 N45384 PX- 0 0 0 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 78 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - COLUMBUS METRO DEPARTURE POINT INTENDED DESTINATION COLUMBUS,GA LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: DESCENDING COLLIDED WITH: DIRT BANK LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - MISCALCULATED FUEL CONSUMPTION MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION FACTOR(S) TERRAIN - ROUGH/UNEVEN COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT. REMARKS- HIT EMBANKMENT APRX 200FT SHORT OF RWY.
Aircraft
- Registration
- N45384
- Reported as
- Cessna 150
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Columbus Metro
N45384Registration cancelled Jul 19, 2012 · Cessna 150MAirframe modelCessna 150MEngine modelContinental 0-200 series
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.