ATL99LA057 · Beech 23
Beech 23 · Accident: airframe, component or system failure during takeoff
From 84A · Cumming, GA to Juína Airport (JIA)
Event
- NTSB case
- ATL99LA057
- 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 23
- Aircraft type
- Beechcraft 23
- 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
- N3621Q
- Operator
- Camilo Pereira
- Onboard fatalities
- Unknown
- Route
- From 84A · Cumming, GATo Juína Airport (JIA)
- 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
- Takeoff · roll/run
- 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
- 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
- Landing gear, nose gear attach point › Overload
- Reason for occurrence undetermined
Approximate · Estimated position: the centre of Jacksonville, FL, the place the record names. Not the accident site.
NTSB narrative
The solo cross-country flight was planned with a refueling stop in Jacksonville. The student pilot reported that the departure runway surface at the departure airport was rough and uneven. Upon arriving in the Jacksonville area, the student pilot was cleared for an approach to and a landing on runway 07. The student pilot stated that during the first landing he heard a cracking or popping sound. The student pilot described the touchdown as normal. At this point he elected to go-around for another approach and landing. The pilot was cleared for another landing on runway 07, and as soon as the airplane touched down on the runway surface, it veered to the right. The airplane rotated 180 degrees in the center of the runway. The post-accident examination of the airplane disclosed that the nose gear attach point had failed. The visual examination of the fracture surface revealed typical overload deformation. Prior to this occurrence, no mechanical problems with the airplane were reported by the pilot. Reportedly, during the wreckage examination, a small amount of corrosion was also discovered on the nose gear attach point.
Probable cause
THE OVERLOAD FAILURE OF THE LANDING GEAR ATTACH POINTS DURING TAKEOFF FROM A TURF AIRSTRIP. FACTORS ARE ROUGH AND UNEVEN TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99LA057
- Event ID
- 20001205X00261
- Case number
- ATL99LA057
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1999-03-21.
- API snapshot SHA-256: d7c1650fd3f6b4fac36c641c11ffe0c290ba480142d99c760a3aca5be9edfb3a; retrieved 2026-09-22T15:39:15.590Z.