- Date
- June 23, 1978
- Place
- Goshen, IN · GOSHEN, IN
- Injuries
- 6 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N4117WPiper PA-32
- Status
- Completed · report February 7, 1979
- Report
- Brief approved by the director
- FAA report
- 19780623042419A
- Case key
- 140446
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-3990 78/6/23 GOSHEN,IN PIPER PA-32 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 30, 210 TIME - 1045 N4117W PX- 0 0 5 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 16 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - GOSHEN MUNICIPAL DEPARTURE POINT INTENDED DESTINATION TOLEDO,OH CHICAGO,IL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: NORMAL CRUISE FIRE OR EXPLOSION: IN FLIGHT IN FLIGHT: NORMAL CRUISE PROBABLE CAUSE(S) PERSONNEL - MAINTENANCE,SERVICING,INSPECTION: IMPROPER MAINTENANCE (MAINTENANCE PERSONNEL) POWERPLANT - ENGINE STRUCTURE: CYLINDER ASSEMBLY MISCELLANEOUS ACTS,CONDITIONS - FATIGUE FRACTURE FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - FIRE IN ENGINE COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT. REMARKS- #4 CYL FAILED
Aircraft
- Registration
- N4117W
- Reported as
- Piper PA-32
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Goshen Municipal
N4117WRegistration cancelled Dec 18, 2014 · Piper PA-32-300Airframe modelPiper PA-32-300Engine modelLycoming TI0-540 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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.