ATL99LA024 · Beech 33-F33A
Beech 33-F33A · Accident: airframe, component or system failure en route
From Jacksonville Executive at Craig Airport (CRG) to Brunswick Golden Isles Airport (BQK)
Event
- NTSB case
- ATL99LA024
- 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
- 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
Beech 33-F33A
- Aircraft type
- Beechcraft 33
- 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
- N69FL
- Operator
- Cleon E. Moore · private individual
- Onboard fatalities
- Unknown
- Route
- From Jacksonville Executive at Craig Airport (CRG), Jacksonville, FLTo Brunswick Golden Isles Airport (BQK), Brunswick, GA
- 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
- 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
- Airframe, component or system failure
- 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
- Substantial
Cause areas
- Pilot in command › Airspeed, not maintained
- Pilot in command › Stall, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After the flight departed the pilot attempted to use the radios, but discovered that there was a loss of electrical power. Air Traffic Controller, observed the airplane as it circled near the airport. The pilot used a walkie-talkie and established radio contact with a man who was knowledgeable of the airplane. With the assistance of the ground person the pilot hand-cranked the landing gear down. The pilot made a low pass over the airport for a visual gear inspection. According to a witness at the airport, it appeared that the landing gear was extended. He continued to observe the airplane as the pilot executed a tight left turn. The airplane disappeared below the trees on the upwind side of runway 08. The airplane collided with a tree and the ground in a residential area.
Probable cause
The Pilot's failure to maintain flying airspeed that resulted in a loss of control and an inadvertent stall. Factors were several electrical system component malfunction.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99LA024
- Event ID
- 20001211X11370
- Case number
- ATL99LA024
- 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: 66ae886a91122269d26bee26459aad3ad4566ced5cee5ee34bce5196851abab0; retrieved 2026-09-21T11:18:22.212Z.