ERA21LA352 · Hine T L/Johnson R BUSH WACKER
Hine T L/Johnson R BUSH WACKER · Accident: loss of control on ground during landing
From Vidalia Regional Airport (VDI) to an unrecorded destination
Event
- NTSB case
- ERA21LA352
- 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
Hine T L/Johnson R BUSH WACKER
- Aircraft type
- Hine T L/johnson BUSH WACKER
- 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
- N797RT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Vidalia Regional Airport (VDI), Vidalia, GATo not recorded
- Aircraft age
- About 22 years (built 1999)
- 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 · flare/touchdown
- 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 on ground
- 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 oper/perf/capability
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot had recently purchased the airplane and requested the airline transport pilot (ATP) assist him flying it back to his home airport. During an enroute stop, the ATP pilot reported that during the landing roll, the airplane became uncontrollable and veered off the left side of the runway, striking a runway sign, which resulted in substantial damage to the right horizontal stabilizer and elevator. The pilot reported that he believed there might have been rigging or tailwheel mechanical issues with the airplane. A visual examination of the brake system performed by a Federal Aviation Administration (FAA) inspector did not reveal any damage, however, the brakes were not tested. The NTSB was not notified of the accident until five months after the occurrence which precluded further examination of the brake and tailwheel system. According to an FAA inspector who reviewed the maintenance records and interviewed people familiar with the airplane’s history, the airplane had been flown about 10 hours in the previous 10 years. The condition inspection, accomplished about 2 months before the accident by a mechanic, revealed the airplane was “squirrely and sensitive” on the controls, but he considered the airplane airworthy. About a month before the accident, the brakes had been rebuilt, and the airplane was returned to service. The ATP pilot, who had never flown this make and model before, reported that he confirmed the airworthiness of the airplane prior to departure, however, he also reported to the FAA inspector that the airplane was not acting right during two takeoff attempts, before the third successful takeoff attempt that initiated the accident sequence. The accident likely could have been prevented if the pilot chose to further investigate the anomaly he experienced on the ground, rather than continuing the flight.
Probable cause
A loss of directional control upon landing for reasons that could not be determined as a result of a delayed report. Contributing was the pilot’s decision to continue a flight with an unknown airworthiness issue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA352
- Event ID
- 20210908103820
- Case number
- ERA21LA352
- 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, cause areas. 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: 0c8fe76124324aaf8aa49d89abbb3b1058b5ff0885ef35a97c16ecf2624cb5a1; retrieved 2026-09-16T14:30:17.888Z.