# Accident 19910531018459A: Piper PA32RT300, Wallingford, CT, May 31, 1991

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 31, 1991, 16:45 local time
- Place: Wallingford, CT
- Damage: Destroyed
- Phase of flight: Scud Running
- Operating rules: General operating rules (Part 91)
- Location: 41.4570° N, 72.8232° W: Placed by OpenAirDocs: center of Wallingford, CT, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.4570&lon=-72.8232&mi=10
- Aircraft: N36069, a cancelled registration (https://openairdocs.org/deregistered/N36069-2012-10-09) (OpenAirDocs)
- Registry model: Piper PA-32RT-300 (registry code 7103215, https://openairdocs.org/model/piper-pa-32rt-300) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32RT300
- Reported engine: LYC IO540K1G5D
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 950 total, 7 in this make and model, 7 in the last 90 days
- NTSB investigation: [NTSB NYC91FA145](https://openairdocs.org/ntsb/NYC91FA145) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19910531018459A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

STRUCK TREES IN AREA OF THUNDERSTORMS AND HEAVY RAIN.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB NYC91FA145](https://openairdocs.org/ntsb/NYC91FA145), May 31, 1991: Piper PA-32RT-300 (N36069), Wallingford, CT, destroyed, 1 fatal. Probable cause: THE PILOT ATTEMPTING A VFR FLIGHT IN ADVERSE WEATHER CONDITIONS, AT AN ALTITUDE THAT WAS INSUFFICIENT TO CLEAR TREES ALONG HIS ROUTE OF FLIGHT. FACTORS RELATED TO THE ACCIDENT WERE THE PILOT'S LACK…

## Other reports on N36069 (2)

Matched to the same aircraft by N-number and date.

- [Incident 19810313019919I](https://openairdocs.org/incident/19810313019919I), Mar 13, 1981: Piper PA32RT300 (N36069), Chester, CT, Minor damage. Nose gear collapsed during rollout due to downlock mechanism broke.
- [Incident 19800401046979I](https://openairdocs.org/incident/19800401046979I), Apr 1, 1980: Piper PA32RT300 (N36069), Ellington, CT, Minor damage. Pilot lost all electrical power, gear emergency procedure not properly performed. Landed gear up.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.