ASN Wikibase Occurrence # 43961
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 4 November 2006 |
| Time: | 23:20 |
| Type: |  Piper PA-32-300 |
| Owner/operator: | Private |
| Registration: | N15852 |
| MSN: | 327340069 |
| Total airframe hrs: | 6581 hours |
| Engine model: | Lycoming IO-540-K1A5 |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Danville, AR -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Little Rock, AR (LIT) |
| Oklahoma City, OK (PWA) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The airplane was in cruise flight at an assigned altitude of 6,000 feet mean sea level while on an instrument flight rules flight plan operating on a night cross-country flight while in visual meteorological conditions. The pilot reported a rough running engine to air traffic controller before transmitting a distress call. The pilot headed towards a local municipal airport; however, discontinued the approach and initiated a forced landing in a cleared pasture that appeared to be a suitable for a forced landing. Radar data depicts the airplane descending toward the area and the ground speed is reduced for the imminent forced landing. Short of the selected landing area, the airplane collided with unmarked powerlines running perpendicular to the selected clearing. There were no reported eyewitness to the accident. The wreckage of the single engine airplane was discovered the next morning. Ground signature at the accident site were consistent with a ground impact in the inverted position. A post-impact fire consumed the airframe, with the exception of the right wing and the aft section of the tail section. An examination of the engine revealed both engine case halves had matching serial numbers. About half of the engine oil pan was consumed by a post-impact fire. Engine control continuity could not be established due to the severity of the fire and separation from the engine mounts. A large hole was found on top of the engine case between the number 4 and number 6 cylinders. In addition, thermal signatures consistent with the lack of oil lubrication were noticeable on both the number 4 and number 6 cylinders. The number 5 cylinder was found separated from its mount. The number 5 connecting rod cap separated from the connecting rod and was not recovered. The maintenance records for the airframe and the powerplant were not located during the course of the accident investigation.
Probable Cause: Failure of the number 5 cylinder which resulted in oil starvation and the subsequent loss of engine power, and the pilot's inability to see the transmission line during the forced landing. Factors Contributing to the accident were the dark night and the transmission line.
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20061108X01628&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Oct-2008 00:45 | ASN archive | Added |
| 21-Dec-2016 19:24 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 05-Dec-2017 09:28 | ASN Update Bot | Updated [Operator, Other fatalities, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation