MIA02LA042 · Ferguson A 26 Vulcan SS
Ferguson A 26 Vulcan SS · Accident: loss of control on ground/water during landing
From Newnan, GA to an unrecorded destination
Event
- NTSB case
- MIA02LA042
- 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
- 1 · 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
Ferguson A 26 Vulcan SS
- Aircraft type
- Ferguson A-26
- 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
- N6129F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Newnan, 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
- Landing · landing roll
- 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 on ground/water
- 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
- Tree(s)
- 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 › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to eyewitnesses to the landing, the twin Rotax powered, pusher configured, 2-place light experimental aircraft's landing touchdown occurred about 130 feet down the 600-foot private grass runway. After touchdown, the left wing dropped, and a small puff of dust was observed under the left wing as in something dragging concurrently with commencement of a left drift. A go around attempt was heard and observed, and the left wing collided with a fence pole on the left runway edge at about 336 feet down the runway. Following the fence pole collision, the aircraft continued left until small tree collision with the right wing caused a right yaw and a secondary severe, sideward collision between a large tree and the cockpit left side. The day before, the pilot experienced a similar loss of runway directional control and, via an e-mail to a friend following the occurrence, attributed it to either not having both main landing gear firmly on the runway before application of wheel braking, or the difference in wheel-to-surface friction properties while braking. Postcrash examination of the main wheel brakes revealed no locked up condition.
Probable cause
The pilot's failure to maintain directional control during landing and go-around, resulting in a collision with a runway perimeter fence pole and trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA02LA042
- Event ID
- 20011211X02386
- Case number
- MIA02LA042
- 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: ad3fb5aa88d8802eca0541d6774e53865ef257150dcf7c506bbeb7951fef95fc; retrieved 2026-09-20T20:16:29.993Z.