- Date
- June 13, 1970
- Place
- Fort Worth, TX · FORT WORTH, TX
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N60730Cessna 150
- Status
- Completed · report August 13, 1970
- Report
- Brief approved by the director
- Case key
- 125834
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-0694 70/6/13 FORT WORTH,TEX CESSNA 150 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 27, 80 TOTAL TIME - 0809 N60730 PX- 0 0 1 PLEASURE/PERSONAL TRANSP HOURS, ALL IN TYPE, NOT DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - MEACHAM FIELD DEPARTURE POINT INTENDED DESTINATION ENID,OKLA OAK GROVE ARPT TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION LANDING: FINAL APPROACH GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION FACTOR(S) POWERPLANT - POWERPLANT-INSTRUMENTS: FUEL QUANTITY GAUGE MISCELLANEOUS ACTS,CONDITIONS - ERRATIC MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND
Aircraft
- Registration
- N60730
- Reported as
- Cessna 150
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Meacham Field
N60730Registration cancelled Feb 15, 2018 · Cessna 150JAirframe modelCessna 150JEngine 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.