ATL01LA102 · Beech 55
Beech 55 · Accident: airframe, component or system failure during landing
From Naval Station Mayport / Admiral David L McDonald Field (NRB) to an unrecorded destination
Event
- NTSB case
- ATL01LA102
- 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
- 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 55
- Aircraft type
- Beechcraft 55
- 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
- N521U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Naval Station Mayport / Admiral David L McDonald Field (NRB), JacksonvilleTo 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
- Landing
- 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, normal retraction/extension assembly › Bent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot completed the landing check and verified that the landing gear cockpit indicators light showed that the landing gear was down and locked position. The pilot continued the approach and the airplane touched down with the left wheel retracted. The subsequent examination of the airplane revealed that the left main landing gear extension rod was bent. The landing gear extension rod was replaced, and a successful functional check of the landing gear system was accomplished. According to the flying club assistant chief pilot, this airplane was used for training, and the origin of the extension rod deformation was not determined. Additionally, the pilot had no means of verifying when the main and nose gear assemblies are in the extended and locked positions.
Probable cause
The failure of the left landing gear extention rod for undetermined reasons that resulted in a landing with the gear retracted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL01LA102
- Event ID
- 20010905X01880
- Case number
- ATL01LA102
- 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, 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: 4aa8b8ae3d9af57f2f36c15cd162b838b92bedf1b0bb9005eef878bc3364e82d; retrieved 2026-09-22T11:37:30.701Z.