ATL98LA018 · John T. Simpson CHALLENGER II CHALLENGER
John T. Simpson CHALLENGER II CHALLENGER · Accident: loss of control in flight en route
From AL (private airstrip) to an unrecorded destination
Event
- NTSB case
- ATL98LA018
- 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
- 0
- 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
John T. Simpson CHALLENGER II CHALLENGER
- Aircraft type
- John T Simpson CHALLENGER
- 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
- N11644
- Operator
- Bruce Diener
- Onboard fatalities
- Unknown
- Route
- From AL (private airstrip)To 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 · climb to cruise
- 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
- Pilot in command › Airspeed, inadequate
- Pilot in command › Stall, encountered
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses stated that the airplane appeared over the tops of the trees, flying towards them. The witnesses saw the airplane gain altitude, then stall into the trees, and nose dive into the ground. The pilot had about 5 hours of flight training in another airplane. According to the co-owner of the airplane, the non-certificated pilot had no formal training in the airplane.
Probable cause
The pilot's failure to maintain adequate airspeed which resulted in a stall and subsequent impact with the ground. A related factor was the pilot's lack of flying experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL98LA018
- Event ID
- 20001208X09258
- Case number
- ATL98LA018
- 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. 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: 4d210ef4aaf3d9470137d294fb67778da57ff88a3348b5af3b755a23706c6a8b; retrieved 2026-09-20T22:44:30.097Z.