MIA08CA049 · Airborne Redback
Airborne Redback · Accident: loss of control in flight during initial climb
From 19A · Jefferson, GA to 19A · Jefferson, GA
Event
- NTSB case
- MIA08CA049
- 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
Airborne Redback
- Aircraft type
- Airborne REDBACK
- Category
- Weight-Shift
- 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
- N1847
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 19A · Jefferson, GATo 19A · Jefferson, 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
- Initial climb
- 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
- 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
- Personnel issues › Action/decision
- 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 reported to NTSB there was no intention for flight, he was taxiing and practicing radio communication procedures. The pilot reported to the airport manager immediately after the accident that the accident flight was his first solo flight. While taxiing on runway 34 with partial power applied, a strong gust of wind occurred and the aircraft became airborne inadvertently, and climbed to approximately 50 feet. He did not apply power and the aircraft drifted to the side of the runway then impacted the ground. The engine remained running postaccident and he had to secure it before being rescued. He further reported there was no preimpact mechanical failure or malfunction with the aircraft. He did state that the AWOS indicated the wind was from 5 mph, gusting to 10 mph, and the AWOS was wrong. The airport manager reported that at the time of the accident, the wind was from the west and north with gusts to 20 plus mph. The installed AWOS was certificated approximately 1 year and 3 months before the accident, but the wind information has been deemed unreliable since certification due to the location of trees within a 500 foot radius of the wind sensor. There was no NOTAM and no information was published in the FAA Airport/Facility Directory pertaining to the unreliable wind information. At the time of the accident, the AWOS on the airport recorded the wind was from 310 degrees at 5 knots; no gusts were reported.
Probable cause
The failure of the pilot-in-command to maintain control of the airplane and his poor weather evaluation before attempting to taxi the airplane. A factor in the accident was the failure of airport personnel to correct the inaccurate wind information reported by the AWOS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA08CA049
- Event ID
- 20080312X00303
- Case number
- MIA08CA049
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
- 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: 965a443b929c627455029b07d3a56965bd25f61522ef6e8f60ce7d6dddaf53be; retrieved 2026-09-15T09:25:26.744Z.
- Corrected after a review of the NTSB narrative and the aircraft's make and model, which establish these values: aircraft category. Airborne Redback is a weight-shift (trike); the manufacturer builds nothing else. The NTSB MDB codes it AIR (Airplane), which is how the aircraft was registered rather than what it is.