- Date
- March 31, 1972
- Place
- Charleston, SC · CHARLESTON, SC
- Injuries
- 5 fatal
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N3421QCessna 320E
- Status
- Completed · report September 18, 1972
- Report
- Brief approved by the director
- Case key
- 165335
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-0157 72/3/31 CHARLESTON,SC CESSNA 320E CR- 1 0 0 NONCOMMERCIAL AIRLINE TRANSPORT, AGE TIME - 1022 N3421Q PX- 4 0 0 PLEASURE/PERSONAL TRANSP 25, 3740 TOTAL HOURS, DAMAGE-DESTROYED OT- 0 0 0 UNK/NR IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - CHARLESTON AFB DEPARTURE POINT INTENDED DESTINATION MORRISTOWN,NJ CHARLESTON,SC TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION LANDING: MISSED APPROACH COLLISION WITH GROUND/WATER: UNCONTROLLED LANDING: MISSED APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION FACTOR(S) PILOT IN COMMAND - DIVERTED ATTENTION FROM OPERATION OF AIRCRAFT MISCELLANEOUS ACTS,CONDITIONS - IMPROPERLY LOADED AIRCRAFT-WEIGHT-AND/OR C.G. MISCELLANEOUS ACTS,CONDITIONS - INSTRUMENTS-MISREAD OR FAILED TO READ COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE REMARKS- ACFT DEPTD 687LB OVR G/W W INSUF FUEL TO ALTPT.ENG QUIT DURG GOARND,PLT LOST CTL.
Aircraft
- Registration
- N3421Q
- Reported as
- Cessna 320E
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Charleston Afb
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.