- Date
- August 5, 1969
- Place
- Windsr Locks, CT · WINDSR LOCKS, CT
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N448QPiper PA-30
- Status
- Completed · report March 31, 1970
- Report
- Brief approved by the director
- Case key
- 161869
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-3438 69/8/5 WINDSR LOCKS,CONN PIPER PA-30 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 51, 1990 TIME - 0951 N448Q PX- 0 0 0 BUSINESS TOTAL HOURS, 930 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - BRADLEY INT DEPARTURE POINT INTENDED DESTINATION WINDSR LOCKS,CONN CLEVELAND,OHIO TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION TAKEOFF: INITIAL CLIMB STALL: MUSH TAKEOFF: INITIAL CLIMB PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING POWERPLANT - FUEL SYSTEM: FUEL INJECTION SYSTEM MISCELLANEOUS ACTS,CONDITIONS - WATER IN FUEL PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED MISCELLANEOUS ACTS,CONDITIONS - IMPROPER EMERGENCY PROCEDURES COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE REMARKS- WATER FOUND IN L FUEL LINE,INJECTOR,AND SCREEN PORT. POOR SEAL AT FUEL TANK FILLER NECK GASKETS.
Aircraft
- Registration
- N448Q
- Reported as
- Piper PA-30
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Bradley Int
N448QRegistration cancelled Jul 9, 2012 · Piper PA-30Airframe modelPiper PA-30Engine modelLycoming IO-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.