Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

January 30, 2008 · Airborne Redback · N1847

Jefferson, GA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
January 30, 2008
Injury Outcomes
1 injury (1 serious injury)
Location
Jefferson, GA
Aircraft
Airborne Redback
Tail Number
N1847
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
MIA08CA049

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.

NTSB 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.

Full 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 weight shift control 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.

Flight

Event TypeAccident
Event Time16:05 EST
Nearest AirportJackson County Airport (0nm)
Runway16
Runway Length4109 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftAirborne Redback
Tail NumberN1847
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsRotax · 503 · Reciprocating · 52
Seats2

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 59 · Third Class · Serious

Conditions

ConditionsVMC
LightDaylight
Wind310° @ 5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point52 / 10 C
Altimeter30.03 inHg
Observation Time21:05
Weather SourceWFAC

Appendix: Source Data