- Date
- September 25, 1966
- Place
- Plainville, CT · PLAINVILLE, CT
- Injuries
- 4 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N5674WPiper PA-28
- Status
- Completed · report November 9, 1966
- Report
- Brief approved by the director
- Case key
- 121205
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-2646 66/9/25 PLAINVILLE CONN PIPER PA-28 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 40, 200 TIME - 1340 N5674W PX- 0 0 3 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 18 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - FROBERTSON TYPE OF ACCIDENT PHASE OF OPERATION OVERSHOOT LANDING: ROLL COLLIDED WITH: DITCHES LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED FACTOR(S) WEATHER - UNFAVORABLE WIND CONDITIONS WEATHER BRIEFING - NO RECORD OF BRIEFING RECEIVED WEATHER FORECAST - UNKNOWN/NOT REPORTED SKY CONDITION CEILING AT ACCIDENT SITE CLEAR UNLIMITED VISIBILITY AT ACCIDENT SITE PRECIPITATION AT ACCIDENT SITE 5 OR OVER(UNLIMITED) NONE OBSTRUCTIONS TO VISION AT ACCIDENT SITE RELATIVE BEARING OF WIND NONE RIGHT CROSS WIND 068-112 DEGREES WIND DIRECTION-DEGREES WIND VELOCITY-KNOTS 290 24 TYPE OF WEATHER CONDITIONS TYPE OF FLIGHT PLAN VFR NONE
Aircraft
- Registration
- N5674W
- Reported as
- Piper PA-28
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Frobertson
N5674WRegistered now · Piper PA-28-150Airframe modelPiper PA-28-150Engine 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.