DEN03FA155 · Hawker Siddeley HS-125-700A
Hawker Siddeley HS-125-700A · Accident: loss of control in flight while maneuvering
From William P. Hobby Airport (HOU) to Jack Brooks Regional Airport (BPT)
Event
- NTSB case
- DEN03FA155
- 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
- 3 · 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
- Visual Meteorological Cond
Hawker Siddeley HS-125-700A
- Aircraft type
- Hawker Siddeley HS-125
- 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
- N45BP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From William P. Hobby Airport (HOU), Houston, TXTo Jack Brooks Regional Airport (BPT), Beaumont, TX
- 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
- Maneuvering
- 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
- Loss of control in flight
- 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
- 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
- Dual student › Aircraft control, not maintained
- Dual student › Airspeed, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The purpose of the flight was for the instructor-pilot to prepare the first and second pilots for their FAA Part 135 competency and proficiency checks scheduled to be conducted in the accident airplane the following week, with operator proving tests to follow shortly thereafter. The first pilot obtained a computer science corporation (CSC) direct user access terminal service (DUATS) weather briefing and filed an instrument flight rules (IFR) flight plan. The instructor-pilot was listed as the pilot-in-command. The airplane took off and proceeded to its designated practice area. According to the cockpit voice recorder (CVR), the pilots practiced various maneuvers under the direction of the instructor-pilot, including steep turns and approaches to stalls. Then the first pilot was asked the to demonstrate an approach-to-landing stall. The first pilot asked the instructor-pilot if he had "ever done stalls in the airplane?" The instructor-pilot replied, "It's been awhile." The first pilot remarked, "This is the first time I've probably done stalls in a jet. Nah, I take that back, I've done them in a (Lear)." The instructor-pilot said he had stalled "the JetStar on a [FAR] one thirty five ride." Flaps were extended and the landing gear was lowered. Digital electronic engine control (DEEC) recorded a power reduction that remained at idle. According to national track analysis program (NTAP) data, the stall was initiated from an altitude of 5,000 feet. The stick shaker sounded and shortly thereafter, the recording ended. The consensus of 25 witness' observations was that the airplane was flying at low altitude and doing "erratic maneuvers." One witness said it "seemed to stop in midair," then pitched nose down. Some witnesses said that the airplane was spinning. Other witnesses said it was in a flat spin. Still another witness said the airplane fell "like a falling leaf." The airplane impacted marshy terrain in a nose-down, wings-level attitude. Wreckage examination revealed the landing gear was down and the flaps were set to 25 degrees. Both engines' compressor/turbine section blades were gouged and bent in the opposite direction of rotation, and there were rotational scoring marks on both cases. No discrepancies were noted.
Probable cause
the first pilot's failure to maintain aircraft control and adequate airspeed. Contributing factors included performing intentional stalls at too low an altitude to afford a safe recovery, the pilot's failure to add power in an attempt to recover, and the flight instructor's inadequate supervision of the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN03FA155
- Event ID
- 20030930X01625
- Case number
- DEN03FA155
- 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: 9d361b4a06deccaa359cf94a5d60a3865cbbb8b09e4b954c8f31ab9fe8098bc2; retrieved 2026-09-20T18:56:57.427Z.