- Date
- December 14, 1972
- Place
- College Park, MD · COLLEGE PARK, MD
- Injuries
- 1 minor, 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N6434GCessna 150K
- Status
- Completed · report February 7, 1973
- Report
- Brief approved by the director
- Case key
- 168861
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-3447 72/12/14 COLLEGE PARK,MD CESSNA 150K CR- 0 0 2 INSTRUCTIONAL COMMERCIAL, FL.INSTR., TIME - 1455 N6434G PX- 0 0 0 DUAL AGE 24, 949 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 767 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - COLLEGE PARK DEPARTURE POINT INTENDED DESTINATION COLLEGE PARK,MD LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB STALL LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT. REMARKS- PIC ATTEMPTED LANDING ON TAXIWAY,ACFT STALLED DRG APPROACH TO TAXIWAY.
Aircraft
- Registration
- N6434G
- Reported as
- Cessna 150K
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- College Park
N6434GRegistration cancelled Sep 4, 1973 · Cessna 150KAirframe modelCessna 150KEngine 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.