Casualties unknown

IFR Accident in Lincolnton, North Carolina (N42Y)

Concord, NC, US

On March 30, 2001, a Piper PA-32RT-300 (registration N42Y) was involved in an aviation accident near Concord, NC. Investigators recorded the probable cause as: An in-flight collision with terrain for undetermined reasons. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

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

A pilot departed Lincolnton, NC, for an IFR flight to Concord despite adverse weather and unmonitored navigation aids. The aircraft crashed near the airport after a pop sound was heard. No precrash mechanical failure was found.

Flight Operations and Weather Conditions

The pilot initiated an Instrument Flight Rules (IFR) journey from Lincolnton, North Carolina, to Concord, North Carolina. Prior to departure, he received a weather briefing from an FAA Automated Flight Service Station. The briefing indicated that conditions at Lincolnton included one hundred overcast skies, visibility limited to a quarter of a mile, and calm winds. Additionally, the service station reported that no weather data was available for Concord and that the Instrument Landing System (ILS) and Distance Measuring Equipment (DME) were unmonitored.

During the briefing, the pilot confirmed possession of Notices to Airmen (NOTAMs). However, he did not designate an alternate airport, which was mandatory given the prevailing weather conditions. Subsequently, a colleague from another company contacted the office to inform the pilot that he was canceling his flight due to the weather. The accident pilot acknowledged awareness that the glide slope was out of service and indicated he would likely delay his departure.

Departure and Approach

Despite these warnings, the pilot departed Lincolnton and established radio contact with approach control. Controllers informed him that the glide slope was inoperative and the ILS/DME remained unmonitored. The pilot received radar vectors and was subsequently cleared for an ILS approach. He was also instructed to report if he canceled his IFR flight on the ground or via the assigned frequency.

Accident Sequence and Investigation Findings

A witness residing near the airport reported hearing an aircraft approaching her location. She heard a distinct pop sound and observed nearby power lines shaking. At the time, fog reached halfway up the trees. After waking her son to investigate, he returned shortly after observing a crashed airplane.

Post-accident examination of the airframe, flight controls, engine assembly, and accessories revealed no evidence of precrash mechanical failure or malfunction.

Frequently asked questions

What happened in the 30 Mar 2001 Piper PA-32RT-300 accident near Concord, NC?

A pilot departed Lincolnton, NC, for an IFR flight to Concord despite adverse weather and unmonitored navigation aids. The aircraft crashed near the airport after a pop sound was heard. No precrash mechanical failure was found.

What aircraft was involved and where did it happen?

The accident on 30 Mar 2001 involved a Piper PA-32RT-300, registration N42Y, at Concord, NC.

What was the probable cause of the accident?

An in-flight collision with terrain for undetermined reasons.

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