Casualties unknown

Mountainous Terrain Collision During ILS Approach (N4123R)

Hot Springs, AR, US

On July 2, 2004, a Piper PA-32-300 (registration N4123R) was involved in an aviation accident near Hot Springs, AR. Investigators recorded the probable cause as: The pilot's failure to fly a stabilized, published instrument approach procedure, which resulted in a collision with mountainous terrain. 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-09-03Data APIEditorial standards

A private pilot executing an ILS approach to runway 5 overflew the airport and collided with mountainous terrain. The pilot was 700 feet above the published approach altitude and failed to report established until too late.

Incident Overview and Pilot Background The aircraft was operated by a 1,765-hour instrument-rated private pilot who was conducting an ILS approach to runway 5. During the approach, the pilot overflew the airport, executed a left turn, and struck mountainous terrain approximately five miles northeast of the airport. A witness in a nearby home reported hearing the aircraft flying very low with a normal engine sound before the engine stopped abruptly. ## Approach Sequence and ATC Communications Air traffic control vectored the pilot to intercept the localizer course for the ILS runway 5 approach. At 1035:53, with the aircraft approximately 5.5 miles southwest of the HOSSY intersection, an approach controller instructed the pilot to fly heading 020 degrees, intercept the localizer, and maintain 3,000 feet until established. The pilot acknowledged and began a right turn toward the airport. Over the following two minutes, the aircraft tracked a 020-degree heading but remained south of the final approach course. At 1038:10, the aircraft was just southeast of HOSSY at 3,000 feet MSL, which was 700 feet above the published approach altitude of 2,300 feet MSL. The pilot had not yet reported established on the final approach course. At 1039:25, the approach controller conducted a position relief briefing and discussed the aircraft's approach with the relief controller, stating, “he's probably going to miss...I turned him on too late probably gonna miss yeah he's too high he's missed it now.” At the same time, the pilot reported established on the final approach course. The aircraft was 2.5 miles past HOSSY and three miles from the runway at 3,000 feet MSL. The relief controller responded, “roger change to advisory approved report your arrival time this frequency.” The pilot acknowledged. The relief controller then added, “well just make sure you got this approach you are cleared for the i l s runway five approach and change to advisory approved report your arrival time this frequency.” The pilot responded, “two three romeo cleared for the i l s runway five I'll report to you when I am down.” No further transmissions were received from the pilot. ## Contributing Factors and Findings Both controllers acknowledged the pilot's abnormal approach but failed to provide known information that could have assisted the pilot in determining whether to continue with the approach or take alternate action, as required by FAA Order 7110.65, “Air Traffic Control,” paragraph 5-9-2, Final Approach Course Interception. Examination of the aircraft and engine revealed no mechanical deficiencies.

All Piper PA-32 accidents →

Frequently asked questions

What happened in the 2 Jul 2004 Piper PA-32-300 accident near Hot Springs, AR?

A private pilot executing an ILS approach to runway 5 overflew the airport and collided with mountainous terrain. The pilot was 700 feet above the published approach altitude and failed to report established until too late.

What aircraft was involved and where did it happen?

The accident on 2 Jul 2004 involved a Piper PA-32-300, registration N4123R, at Hot Springs, AR.

What was the probable cause of the accident?

The pilot's failure to fly a stabilized, published instrument approach procedure, which resulted in a collision with mountainous terrain. Factors were the clouds and the air traffic controllers' failure to provide known information that may have assisted the pilot in determining whether to continue with the approach…

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