- Date
- November 30, 1971
- Place
- Opa Locka, FL · OPA LOCKA, FL
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N2279PPiper PA-23
- Status
- Completed · report May 10, 1972
- Report
- Brief approved by the director
- Case key
- 164381
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-3724 71/11/30 OPA LOCKA,FLA PIPER PA-23 CR- 0 0 2 INSTRUCTIONAL COMMERCIAL, FL.INSTR., TIME - 1000 N2279P PX- 0 0 0 DUAL AGE 25, 1148 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 70 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - OPA LOCKA WEST DEPARTURE POINT INTENDED DESTINATION OPA LOCKA,FLA LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: RUN GROUND-WATER LOOP-SWERVE TAKEOFF: RUN PROBABLE CAUSE(S) PILOT IN COMMAND - EXERCISED POOR JUDGMENT PILOT IN COMMAND - FAILED TO FOLLOW APPROVED PROCEDURES,DIRECTIVES,ETC. PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION MISCELLANEOUS ACTS,CONDITIONS - SIMULATED CONDITIONS DUAL STUDENT - FAILED TO MAINTAIN DIRECTIONAL CONTROL COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE REMARKS- IP CUT MIXTURE CTL ON L ENG TO SIMULATE FAILURE.ACFT RAN OFF RWY,NOSE GR COLLAPSED.
Aircraft
- Registration
- N2279P
- Reported as
- Piper PA-23
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Opa Locka West
N2279PRegistration cancelled Mar 14, 2011 · Piper PA-23Airframe modelPiper PA-23Engine modelLycoming 0-320 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.