# Accident 19820329006489A: Piper PA32R300, Rochester, MA, March 29, 1982

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 29, 1982, 09:59 local time
- Place: Rochester, MA
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 41.7318° N, 70.8200° W: Placed by OpenAirDocs: center of Rochester, MA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.7318&lon=-70.8200&mi=10
- Aircraft: N1104Q, a cancelled registration (https://openairdocs.org/deregistered/N1104Q-2009-06-26) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-300) (OpenAirDocs)
- Reported make and model: PIPER PA32R300
- Reported engine: LYC IO540*
- Fatal injuries: 0
- Pilot flight hours: 1,658 total, 988 in this make and model, 21 in the last 90 days
- NTSB investigation: [NTSB NYC82FNA12](https://openairdocs.org/ntsb/NYC82FNA12) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19820329006489A

## Narrative

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

ENGINE QUIT, CRASH LANDED IN TREES. FUEL PUMP ROCKER ARM HAD FAILED DUE TO METAL FATIGUE.

## 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 NYC82FNA12](https://openairdocs.org/ntsb/NYC82FNA12), Mar 29, 1982: Piper PA-32R (N1104Q), Rochester, MA, substantial damage

## Other reports on N1104Q (1)

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

- [Incident 19780223001549I](https://openairdocs.org/incident/19780223001549I), Feb 23, 1978: Piper PA32/ (N1104Q), Norfolk, VA. Pilot cleared to land on assigned runway, landed on taxiway.

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.