# Accident 20060121001609A: Piper PA28140, East Killingly, CT, January 21, 2006

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 21, 2006, 09:50 local time
- Place: East Killingly, CT
- Damage: Destroyed
- Phase of flight: Sfl Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 41.8558° N, 71.8172° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=41.8558&lon=-71.8172&mi=10
- Aircraft: N32729, a cancelled registration (https://openairdocs.org/deregistered/N32729-2007-06-26) (OpenAirDocs)
- Registry model: Piper PA-28-140 (registry code 7102802, https://openairdocs.org/model/piper-pa-28-140) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA28140
- Fatal injuries: 0
- Pilot flight hours: 420 total, 350 in this make and model, 8 in the last 90 days
- NTSB investigation: [NTSB NYC06CA056](https://openairdocs.org/ntsb/NYC06CA056) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060121001609A

## Narrative

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

(-23) ^PRIVACY DATA OMITTED^, PRIVATE PILOT, WAS TAKING A BIANNUAL FLIGHT REVIEW (BFR) WITH ^PRIVACY DATA OMITTED^ A CERTIFIED FLIGHT INSTRUCTOR (CFI). THIS WAS THE FIRST TIME THEY HAD MET. THEY DID NOT DISCUSS WHAT WOULD HAPPEN IF THERE WAS A REAL EMERGENCY DURING THE FLIGHT, OR WHO WOULD HAVE CONTROL OF THE AIRCRAFT. AFTER DEPARTING WINDHAM AIRPORT, THEY PERFORMED A SERIES OF MANEUVERS, INCLUDING A SIMULATED ENGINE FAILURE INITIATED AT APPROXIMATELY 2500 FEET ASL (ALTIMETER). ^PRIVACY DATA OMITTED^ HAD INTENDED THAT THE SIMULATED EMERGENCY LANDING LOCATION WOULD BE AT DANIELSON AIRPORT. BOTH AGREED THAT THE AIRCRAFT WOULD NOT BE ABLE TO GLIDE TO THE AIRPORT. THE PILOT ^PRIVACY DATA OMITTED^ SELECTED THE EMERGENCY LANDING AREA AS A FIELD IN EAST KILLINGLY, CT. DURING THE FINAL APPROACH TO THE FIELD, THE PILOT ^PRIVACY DATA OMITTED^ RECOGNIZED HE WAS TOO LOW AND REQUESTED HE BE ALLOWED TO ADD POWER. WHEN HE ADDED POWER, THE ENGINE RESPONDED. ^PRIVACY DATA OMITTED^ REQUESTED THAT THE PILOT ^PRIVACY DATA OMITTED^ LOWER THE NOSE OF THE AIRCRAFT BECAUSE THE ATTITUDE OF THE AIRCRAFT WAS NOSE HIGH. MOMENTS LATER, THE AIRCRAFT STRUCK THE TREES, AND THEN IMPACTED THE GROUND IN THE FIELD. THE ELEVATION OF THE FIELD AT THE POINT OF IMPACT IS APPROXIMATELY 720 FEET ASL.

## 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 NYC06CA056](https://openairdocs.org/ntsb/NYC06CA056), Jan 21, 2006: Piper PA-28-140 (N32729), East Killingly, CT, substantial damage. Probable cause: The flight instructor's delayed decision to discontinue the simulated forced landing, which resulted in a collision with trees.

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.