Casualties unknown

Night Forced Landing Ends in Powerline Collision (N15852)

Danville, AR, US

On November 5, 2006, a Piper PA-32-300 (registration N15852) was involved in an aviation accident near Danville, AR. Investigators recorded the probable cause as: 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. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 8 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

A single-engine aircraft on an IFR night flight experienced engine roughness and attempted a forced landing in a pasture, but struck unmarked powerlines short of the field. The wreckage was found inverted with post-impact fire damage.

Accident Overview

A single-engine airplane, operating under an instrument flight rules flight plan at a cruising altitude of 6,000 feet mean sea level, encountered engine trouble during a night cross-country flight in visual meteorological conditions. The pilot reported a rough-running engine to air traffic control and subsequently transmitted a distress call. The pilot diverted toward a municipal airport but discontinued the approach and initiated a forced landing in a cleared pasture that appeared suitable.

Descent and Impact

Radar data indicated the airplane descending toward the pasture with a reduction in ground speed consistent with the forced landing. However, the aircraft collided with unmarked powerlines that ran perpendicular to the selected clearing, short of the intended landing area. No eyewitnesses reported the accident.

Wreckage Examination

The wreckage was discovered the following morning. Ground signatures were consistent with an impact in an inverted position. A post-impact fire consumed most of the airframe, leaving only the right wing and aft tail section intact.

Engine Findings

Examination of the engine revealed that both crankcase halves bore matching serial numbers. Approximately half of the oil pan had been consumed by the post-impact fire. Due to the severity of the fire and separation from the engine mounts, engine control continuity could not be established. A large hole was found on top of the engine case between the number 4 and number 6 cylinders. Thermal patterns consistent with a lack of oil lubrication were evident on both the number 4 and number 6 cylinders. The number 5 cylinder was separated from its mount, and the number 5 connecting rod cap had separated from the connecting rod and was not recovered.

Maintenance Records

Maintenance records for both the airframe and the powerplant were not located during the investigation.

All Piper PA-32 accidents →

Frequently asked questions

What happened in the 5 Nov 2006 Piper PA-32-300 accident near Danville, AR?

A single-engine aircraft on an IFR night flight experienced engine roughness and attempted a forced landing in a pasture, but struck unmarked powerlines short of the field. The wreckage was found inverted with post-impact fire damage.

What aircraft was involved and where did it happen?

The accident on 5 Nov 2006 involved a Piper PA-32-300, registration N15852, at Danville, AR.

What was the probable cause of the accident?

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.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20061108X01628. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.