ATL95LA125 · Luscombe 8A/E
Luscombe 8A/E · Accident: loss of control in flight on approach
From Middle Georgia Regional Airport (MCN) to an unrecorded destination
Event
- NTSB case
- ATL95LA125
- 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
Luscombe 8A/E
- Aircraft type
- Luscombe 8
- 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
- N2853K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Middle Georgia Regional Airport (MCN), Macon, GATo 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
- Approach · VFR pattern final
- 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
- 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, main gear › Overload
- Pilot in command(cfi) › Aircraft control, not maintained
- Pilot in command(cfi) › Compensation for wind conditions, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT WAS ON A NORMAL FINAL APPROACH PATH UNTIL IT CLEARED THE TREES THAT PRECEDED THE 3100 FOOT GRASS STRIP. THE AIRCRAFT THEN BEGAN TO SINK RAPIDLY AND THE FLIGHT INSTRUCTOR CALLED FOR A GO-AROUND. THE FLIGHT INSTRUCTOR STATED THAT DESPITE FULL POWER, THE AIRCRAFT WOULD NOT CLIMB OR MAINTAIN LEVEL FLIGHT. HE FURTHER STATED THAT THERE MAY HAVE BEEN CONVECTIVE ACTIVITY IN THE AREA, AND THAT THEY HAD ENCOUNTERED A WIND SHEAR. THE AIRCRAFT MADE A HARD LANDING, AND THE MAIN LANDING GEAR ASSEMBLY COLLAPSED UPON IMPACT.
Probable cause
THE PILOT IN COMMAND'S FAILURE TO COMPENSATE FOR WIND CONDITIONS WHICH RESULTED IN A FAILURE TO MAINTAIN CONTROL OF THE AIRCRAFT WHEN A WINDSHEAR WAS ENCOUNTERED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL95LA125
- Event ID
- 20001207X03858
- Case number
- ATL95LA125
- 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: ff265d536524a87d606ece0427eeed4d54cc035f67451ef9d2e16de33a74e632; retrieved 2026-09-22T23:42:31.995Z.