# Accident 20061231029339A: Piper PA32300, Washingtontwnsp, MI, December 31, 2006

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: December 31, 2006, 18:32 local time
- Place: Washingtontwnsp, MI
- Damage: Destroyed
- Phase of flight: Final Approach-IFR
- Operating rules: General operating rules (Part 91)
- Location: 42.7961° N, 82.9750° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=42.7961&lon=-82.9750&mi=10
- Aircraft: N888PR, a cancelled registration (https://openairdocs.org/deregistered/N888PR-2013-04-30) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- Reported engine: LYC IO540K1A5
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 544 total, 302 in this make and model, 28 in the last 90 days
- NTSB investigation: [NTSB CHI07LA051](https://openairdocs.org/ntsb/CHI07LA051) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20061231029339A

## Narrative

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

(-23) THE AIRCRAFT WRECKAGE WAS EXAMINED AT THE ROMEO AIRPORT MAINTENANCE HANGAR ON 1/4/07. FLIGHT CONTROL CONTINUITY COULD NOT BE ESTABLISHED DUE TO SEPARATION OF BOTH WINGS AND THE EMPENNAGE FROM THE FUSELAGE DURING THE CRASH SEQUENCE. THE RUDDER, VERTICAL STABILIZER, AND STABILATOR HAD SEPARATED FROM THE EMPENNAGE, AND THE RUDDER HAD SEPARATED FROM THE VERTICAL STABILIZER. THE ENGINE AND PROPELLER CAME TO REST APPROXIMATELY 100 FEET FROM THE REST OF THE AIRCRAFT. IT APPEARED THAT THE ENGINE IMPACTED AND BOUNCED OFF SEVERAL TREES DURING THE IMPACT SEQUENCE, AS THERE WAS WOOD EMBEDDED IN SEVERAL PLACES. WITH THE EXCEPTION OF THE ENGINE DRIVEN FUEL PUMP AND PROPELLER GOVERNOR, ALL OTHER ENGINE ACCESSORIES HAD SEPARATED AS THE ENGINE FELL TO EARTH AND TUMBLED THROUGH THE TREES. FUEL WAS FOUND IN BOTH THE ENGINE DRIVEN FUEL PUMP AND FLOW DIVIDER, AND AN EXAMINATION OF THE PROPELLER SHOWED BENDING AND TWISTING OF ALL THREE BLADES, AND TWO BLADES WERE TWISTED IN THE HUB. THIS WOULD BE CONSISTENT WITH IMPACT OCCURRING WITH THE ENGINE OPERATING AND PRODUCING POWER. INSPECTION OF THE OIL SUCTION SCREEN AND OIL SUMP SHOWED THESE AREAS CLEAN OF DEBRIS. THE FUEL INJECTOR SERVO INLET SCREEN WAS CLEAN. WE WERE UNABLE TO ROTATE THE CRANKSHAFT, DUE TO SEVERE IMPACT DAMAGE TO THE ENGINE. HOWEVER, THE ENGINE CRANKSHAFT AND CAMSHAFT WERE INSPECTED BY USE OF A FLEXIBLE LIGHT SCOPE IN THE ACCESSORY GEARBOX AREA, AS WELL AS THROUGH THE CASE WHERE LARGE PIECES OF THE CASE WERE MISSING. THESE AREAS APPEARED TO BE IN GOOD CONDITION. VOICE COMMUNICATION TAPES WERE PROVIDED BY SELFRIDGE ANG ATC. THESE TAPES WERE ROUTINE COMMUNICATION, ADDRESSING CURRENT BAROMETRIC READINGS AT SELFRIDGE, AND AT NO TIME DID THE PILOT INDICATE ANY PROBLEMS, MECHANICAL OR WEATHER RELATED. RADAR ROUTE INFORMATION WAS NOT AVAILABLE FROM SELFRIDGE, SO I REQUESTED ATC ACCIDENT PACKAGE FROM DTW ATC, BUT HAVE NOT RECEIVED IT AT THIS TIME. TWO PASSENGERS ONBOARD THE AIRCRAFT WERE INTERVIEWED BY MACOMB COUNTY SHERIFF DEPUTIES IMMEDIATELY AFTER THE CRASH. BOTH STATED THAT THE FLIGHT HAD BEEN SMOOTH, THE PILOT HAD SAID NOTHING OR GIVEN ANY INDICATIONS OF PROBLEMS, AND THEY BOTH THOUGHT THEY WERE LANDING AT THE AIRPORT UNTIL THEY HIT THE TREES.

## 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 CHI07LA051](https://openairdocs.org/ntsb/CHI07LA051), Dec 31, 2006: Piper PA-32-300 (N888PR), Romeo, MI, substantial damage, 1 fatal. Probable cause: The pilot's failure to maintain aircraft control and proper rate of descent during the VOR approach. Factors associated with the accident were the low cloud conditions and moderate to heavy rain.

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.