DFW08LA166 · Beech 99
Beech 99 · Accident en route
From Bowling Green Municipal Airport (H19) to an unrecorded destination
Event
- NTSB case
- DFW08LA166
- 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
Beech 99
- Aircraft type
- Beechcraft 99
- 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
- N99NN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bowling Green Municipal Airport (H19), Bowling Green, MOTo not recorded
- 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 · 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
- Miscellaneous/other
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial pilot reported that he was en route to a parachutist jump zone on the first of two planned jumps. Prior to the first jump, before he had slowed the airplane, or illuminated the green jump light, indicating that the parachutists had permission to jump, two of the parachutists prematurely jumped. The first parachutist stated that as soon as he jumped, he realized that the airplane was going faster than normal, and he tucked into a ball, barely missing the horizontal stabilizer. According to the other parachutists still aboard, the second jumper exited, and struck the horizontal stabilizer with his head. He never opened his parachute. All of the other parachutists and the pilot stated that the green jump light was never turned on. Post-accident toxicology testing was consistent with impairment of the fatally injured parachutist by recent marijuana use.
Probable cause
The parachutist's failure to follow procedures/directives by not waiting to jump until the green jump light was illuminated, resulting in his collision with the airplane's tail. Contributing to the accident was the parachutist's impairment by the use of marijuana prior to performing a parachute jump.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW08LA166
- Event ID
- 20080627X00939
- Case number
- DFW08LA166
- 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: 56369d697f37df21d714ca68b9b726d40dc7d729e4b5365a5ddf51e5c96be731; retrieved 2026-09-13T19:10:08.836Z.