The U.S. aircraft register, updated daily
Accidents · NTSB FTW04FA172 · Final report

Piper PA-32-300 accident near Hot Springs, Arkansas, July 2, 2004

On July 2, 2004 at about 3:43 pm local time, a Piper PA-32-300, registered N4123R, was substantially damaged in an accident near Hot Springs, Arkansas (Hot Springs/Memorial Field). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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 or take alternate action.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 2, 2004 · about 3:43 pm local time
Place
Hot Springs, Arkansas · Hot Springs/Memorial Field · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32-300 · all PA-32-300s on the register
Registration
N4123R · registry record · serial 32-40441
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The 1,765-hour instrument rated private pilot was executing the ILS RWY 5 instrument approach when he over flew the airport, then made a left turn and collided with mountainous terrain approximately five miles northeast of the airport. A witness was in her home when she heard the sound of an airplane "flying really low." She said the engine sounded normal, and then the sound of the engine stopped very "abruptly." The pilot was vectored by air traffic control (ATC) to intercept the localizer course for the ILS RWY 5 approach. A review of ATC communications and radar data revealed at 1035:53, when the airplane was approximately 5.5 miles southwest of 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 towards the airport. Over the next two minutes, the airplane tracked a 020 degree heading but remained south of the final approach course. At 1038:10, the airplane was just southeast of HOSSY at an altitude of 3,000 feet msl. At this point, the airplane was 700 feet above the published approach altitude, which was 2,300 feet msl, and the pilot had not reported established on the final approach course. At 1039:25, the approach controller conducted a position relief briefing and discussed the airplane's approach with the relief controller. The controller stated to the relief controller, "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 1039:25, the pilot reported established on the final approach course. The airplane was 2.5 miles past HOSSY and three miles from the runway at an altitude of 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 replied, "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. Both controllers acknowledged the pilot's abnormal approach and failed to provide known information that may have assisted the pilot in determining whether to continue with the approach or take alternate action as required per FAA Order 7110.65, "Air Traffic Control" paragraph 5-9-2, Final Approach Course Interception. Examination of the airplane and engine revealed no mechanical deficiencies.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,765 hours in all
  • Last flight review: October 18, 2002
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,339 hours
  • Last inspection: annual inspection, January 2, 2004
  • Maximum gross weight: 3,400 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming IO-540 (piston); 0 hours total

The flight

  • Departed from: 6I2 Springfield KY at 12:00 pm
  • Destination: HOT Hot Springs AR
  • Flight plan: IFR
  • Runway 5, 6,595 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 220° at 4 knots
  • Visibility: 7 statute miles
  • Sky: broken clouds at 1,300 ft; scat at 800 ft
  • Temperature: 77°F (25°C), dew point 73°F (23°C)
  • Altimeter: 30.03 inHg
  • Observation at 4:43 pm from HOT, 5 miles away

Injuries

FatalSeriousMinorNone
Crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.