ERA11LA239 · Beech BE99
Beech BE99 · Accident: system/component malfunction/failure (non-power) on approach
From Polk County Airport- Cornelius Moore Field (4A4) to Polk County Airport- Cornelius Moore Field (4A4)
Event
- NTSB case
- ERA11LA239
- 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 BE99
- 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
- N899AE
- Operator
- Skydive Georgia
- Onboard fatalities
- Unknown
- Route
- From Polk County Airport- Cornelius Moore Field (4A4), Cedartown, GATo Polk County Airport- Cornelius Moore Field (4A4), Cedartown, 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
- Approach
- 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
- System/component malfunction/failure (non-power)
- 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
- Aircraft › Aircraft systems
- 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 pilot received an unsafe landing gear indication for the left main landing gear when he configured the airplane for landing. He cycled the gear and then attempted a manual extension, both without success. The pilot then completed the landing on the nose and right main landing gear. A postaccident examination of the left main landing gear actuator revealed that the supports for the actuator bearings lacked lubrication and that the bearings displayed wear due to inadequate lubrication. The overhauled actuator had accumulated 377.5 hours and 285 cycles since overhaul and was installed about 31 months before the accident; the manufacturer's maintenance manual prescribed lubrication of the retract actuator and actuator support bearings every 1,000 cycles or 30 months (whichever occurs first). It could not be determined if inadequate lubrication was applied at installation or if a loss of lubrication was not detected in subsequent inspections. The manufacturer’s maintenance manual cautioned: "When washing the airplane with soap and water, use special care to avoid washing grease away from lubricated area. After washing the wheel well areas with solvent, lubricate all lubrication points. Premature wear of the lubricated surfaces may result if these precautions are not observed."
Probable cause
The failure of the left main landing gear bearings and supports due to inadequate lubrication by unknown maintenance personnel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11LA239
- Event ID
- 20110412X21246
- Case number
- ERA11LA239
- 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: a4363a7f00845518fca403e03a3c1ab58cc803dae86cf236d6e89973f2fca7c5; retrieved 2026-09-15T16:02:53.045Z.