DFW06FA019 · Cessna 500
Cessna 500 · Accident: loss of control in flight during initial climb
From William P. Hobby Airport (HOU) to Corpus Christi International Airport (CRP)
Event
- NTSB case
- DFW06FA019
- 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
- Visual Meteorological Cond
Cessna 500
- Aircraft type
- Cessna 500
- 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
- N505K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From William P. Hobby Airport (HOU), Houston, TXTo Corpus Christi International Airport (CRP), Corpus Christi, 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
- Initial climb
- 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/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 › Directional control, 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 4,100-hour commercial pilot lost directional control of the single-pilot twin-engine turbojet while taking off from runway 22 (7,602-feet long by 150-feet wide), and impacted the ground about 3,750 feet from the point of departure. Several witnesses reported that the airplane climbed to approximately 150 feet, rolled to the right, descended, and then struck the ground inverted. The weather was day VFR and the wind was reported from 170 degrees at 10 knots. Examination of the wreckage revealed that none of the main-entry door latching pins were in their fully locked position. The airplane's flight controls and engines did not disclose any mechanical discrepancies. The flaps were in the takeoff position and the control lock was unlocked. The pilot had not flown the airplane for over nine months because of extensive maintenance; the accident occurred on its first test flight out of maintenance. Since the pilots flight records were not found, it is unknown how much flight time the pilot had flown in the last nine months. The other airplane that the pilot owned was a Cessna 650, but witnesses stated that the pilot was only qualified as a co-pilot. Most of the maintenance records that were located were not completed; an approval for return-to-service was not found. Another airplane that had declared an emergency was on a 10-mile final when the tower cleared the accident airplane for takeoff, with no delay on the takeoff roll. No additional communication or distress calls were reported from the accident airplane. The airplane was not equipped with either a flight data recorder or a cockpit voice recorder. No anomalies were found on either engine that could have prevented normal engine operation.
Probable cause
The pilot's failure to maintain directional control of the airplane resulting in an inadvertent stall/mush. Contributing factors were the unsecured passenger door and the pilot's diverted attention.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06FA019
- Event ID
- 20051110X01829
- Case number
- DFW06FA019
- 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: e1896aed61d033ec4dd3716d908890453f09916a3dad9527a7ee4460f9fb6f7c; retrieved 2026-09-20T17:46:27.784Z.