FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW04FA036 · Beech S35

4 Dec 2003 · Harrison, AR, United States

Beech S35 · Accident on approach

From Bill & Hillary Clinton National Airport/Adams Field (LIT) to Boone County Airport (HRO)

Report a problem

Event

NTSB case
FTW04FA036
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Beech S35

Aircraft type
Beechcraft 35
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N350JL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, ARTo Boone County Airport (HRO), Harrison, AR
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · IFR initial approach
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/mush
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Stall/mush, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Prior to departure, the 6,000-hour instrument rated private pilot obtained a weather briefing and filed an IFR flight plan for 103-nautical mile flight, which he estimated to be a 45 minute flight. The flight was cleared by the ILS RWY 36 approach into his destination airport, which was an uncontrolled airport. While on the approach, the pilot reported on the airport’s Unicom frequency, that he was a "little" high and was going to make a downwind entry for runway 36. A witness first observed the airplane when it was midfield of the runway at an approximate altitude of 300 to 400 feet agl. The airplane then made a left crosswind turn; followed by another left turn and entered a narrow downwind leg for runway 36. While on the downwind leg, the airplane appeared to get "lower and slower than usual." As it crossed over buildings located southwest of the runway, it turned left onto the base leg, and made a steep bank as it turned onto final approach; however, the airplane "overshot" the runway. A second witness observed the airplane traveling north to south approximately 50-60 feet agl when it made a "hard" left turn. The airplane then made a "hard twisting movement" and the nose of the airplane pointed down toward the ground. The airplane came to rest upright in a 15-foot deep drainage ditch on a magnetic heading of 100-degrees, approximately 1/4-mile southeast and about 400 feet east of the extended centerline. There was no post-impact fire. The airplane, which was not equipped with shoulder harnesses, was configured with the landing gear down, the flaps extended to 12 degrees and the speed brakes deployed at the time of the impact. At the time of the accident the weather was reported as overcast skies at 700 feet with visibility at 4 miles. Flight control continuity was established and the examination of the airframe and engine did not reveal any anomalies that could have prevented normal operations.

Probable cause

The pilot's failure to maintain the proper airspeed, which resulted in an inadvertent stall. Contributing factors were the pilot's failure to follow the published instrument approach procedures, and his failure attain the proper glidepath.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW04FA036
Event ID
20031211X02019
Case number
FTW04FA036
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d5e9c08cbe11288f61981284b6f4befdd6c18980f428a4bcfa44f363ff82ab21; retrieved 2026-09-20T18:44:53.833Z.