CEN13FA326 · Hawker Beechcraft B200GT
Osage Air Hawker Beechcraft B200GT · Accident: aerodynamic stall/spin en route
From Baton Rouge Metropolitan Airport (BTR) to McComb-Pike County Airport / John E Lewis Field (MCB)
Event
- NTSB case
- CEN13FA326
- 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
- 1 · 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 Beechcraft B200GT
- Aircraft type
- Beechcraft 200
- 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
- N510LD
- Operator
- Osage Air
- Onboard fatalities
- Unknown
- Route
- From Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LATo McComb-Pike County Airport / John E Lewis Field (MCB), McCOMB, MS
- 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
- En route · climb to cruise
- Defining eventThe 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
- Aerodynamic stall/spin
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The accident pilot and two passengers had just completed a ferry flight on the recently purchased airplane. A review of the airplane's cockpit voice recorder audio information revealed that, during the ferry flight, one of the passengers, who was also a pilot, was pointing out features of the new airplane, including the avionics suite, to the accident pilot. The pilot had previously flown another similar model airplane, but it was slightly older and had a different avionics package; the new airplane's avionics and flight management system were new to the pilot.
After completing the ferry flight and dropping off the passengers, the pilot departed for a short cross-country flight in the airplane. According to air traffic control recordings, shortly after takeoff, an air traffic controller assigned the pilot a heading and altitude. The pilot acknowledged the transmission and indicated that he would turn to a 045 heading. The radio transmission sounded routine, and no concern was noted in the pilot's voice. However, an audio tone consistent with the airplane's stall warning horn was heard in the background of the pilot's radio transmission. The pilot then made a radio transmission stating that he was going to crash. The audio tone was again heard in the background, and distress was noted in the pilot's voice. The airplane impacted homes in a residential neighborhood; a postcrash fire ensued. A review of radar data revealed that the airplane made a climbing right turn after departure and then slowed and descended. The final radar return showed the airplane at a ground speed of 102 knots and an altitude of 400 feet. Examination of the engines and propellers indicated that the engines were rotating at the time of impact; however, the amount of power the engines were producing could not be determined. The examination of the airplane did not reveal any abnormalities that would have precluded normal operation. It is likely that the accident pilot failed to maintain adequate airspeed during departure, which resulted in an aerodynamic stall and subsequent impact with terrain, and that his lack of specific knowledge of the airplane's avionics contributed to the accident.
Probable cause
The pilot’s failure to maintain adequate airspeed during departure, which resulted in an aerodynamic stall and subsequent impact with terrain. Contributing to the accident was the pilot’s lack of specific knowledge of the airplane’s avionics.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13FA326
- Event ID
- 20130607X70213
- Case number
- CEN13FA326
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: fbb6bb46a452af249f29b7424518ddffab10e452bb8c7726d2e0617d7e09ea41; retrieved 2026-09-14T15:58:15.209Z.