Kaleidoscope Charter Services Hawker Siddeley 125-700 accident
Hawker Siddeley 125-700 · Accident: dragged wing, rotor, pod, float or tail/skid on approach
From Addison Airport (ADS) to William P. Hobby Airport (HOU)
Event
- NTSB case
- DFW06CA017
- 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
- 0 · 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
- Charter & commuter
- 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 125-700
- Aircraft type
- Hawker Siddeley 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
- N564BR
- Operator
- Kaleidoscope Charter Services
- Onboard fatalities
- Unknown
- Route
- From Addison Airport (ADS), Dallas, TXTo William P. Hobby Airport (HOU), Houston, 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 135: Air Taxi & Commuter
- 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 · VFR pattern final
- 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
- Dragged wing, rotor, pod, float or tail/skid
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Proper alignment, not attained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The transport category twin-jet airplane was on the first leg of its 215-nautical mile cross-country flight. During the approach at their destination, the two airline transport pilots were advised to expect a visual approach to runway 12R. The flight crew reported that they set-up for the approach and were on a stabilized visual approach to runway 12R. While on final approach, the tower asked the crew where they intended to park on the airport. The flight crew responded that the intended to park at Millionaire, a fixed-base operator (FBO). The flight crew was then asked by Air Traffic Control (ATC) if they would prefer landing on runway 17, which is adjacent to their destination FBO. The flight crew acknowledge that they would prefer runway 17, and the tower cleared the flight to land on runway 17. The pilot-in-command elected to "side step" to runway 17 and initiated a right descending turn to the runway, landing approximately 2,000 feet down the 6,000-foot by 150-foot wide runway. The airplane over-shot the final approach course, and the pilot-in-command corrected with a sudden right turn to align the airplane prior to touchdown. The right wing dragged the ground during the last turn to align the airplane prior to touch down. After the eight passengers exited the airplane, ground personnel informed the crew that the right wing had sustained damage consistent with a ground strike during the approach/landing.
Probable cause
The pilot-in-command's failure to attain proper runway alignment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA017
- Event ID
- 20051130X01907
- Case number
- DFW06CA017
- 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: 7eb4759433ad5f3f8405d6eca84c7e2f9abc1ca19d57a1b2c7486dac0fd8c494; retrieved 2026-09-18T14:58:02.656Z.