- Date
- October 17, 1980
- Place
- Columbia, SC · COLUMBIA, SC
- Injuries
- 2 serious
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N1167ZAero Comdr 680FLP
- Status
- Completed · report January 6, 1981
- Report
- Brief approved by the director
- FAA report
- 19801017057629A
- Case key
- 128393
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-3048 80/10/17 COLUMBIA,SC AERO COMDR 680FLP CR- 0 1 0 NONCOMMERCIAL COMMERCIAL, AGE 50, 6150 TIME - 2222 N1167Z PX- 0 1 0 BUSINESS TOTAL HOURS, 225 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - COLUMBIA METRO DEPARTURE POINT INTENDED DESTINATION CLEVELAND,OH COLUMBIA,SC TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION LANDING: FINAL APPROACH COLLIDED WITH: DIRT BANK LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION FACTOR(S) TERRAIN - ROUGH/UNEVEN MISCELLANEOUS ACTS,CONDITIONS - FAILURE OF TWO OR MORE ENGINES COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-2 ENGINES EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- DRG TURN TO FINAL,SWITCHED FM AUX TO MAIN FUEL TNK,BOTH ENGS LOST PWR.BOTH AUX TNKS NR EMPTY.
Aircraft
- Registration
- N1167Z
- Reported as
- Aero Comdr 680FLP
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Columbia Metro
N1167ZRegistration cancelled Aug 27, 2014 · Aero Commander 680FL PAirframe modelAero Commander 680FL PEngine modelLycoming IGSO-540-B1A
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.