FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA451 · Vans RV 6 Undesignat

28 Jul 2018 · Pickens, SC, United States

Vans RV 6 Undesignat · Accident: abnormal runway contact during landing

From Asheville Regional Airport (AVL) to Asheville Regional Airport (AVL)

Report a problem

Event

NTSB case
GAA18CA451
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

Vans RV 6 Undesignat

Aircraft type
Vans RV-6
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
N24CM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Asheville Regional Airport (AVL), Asheville, NCTo Asheville Regional Airport (AVL), Asheville, NC
Aircraft age
About 24 years (built 1994)
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
Abnormal runway contact
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
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot in the tailwheel-equipped, experimental, amateur-built airplane, he had practiced two takeoffs and landings and then decided to refuel the airplane. After refueling the airplane, he flew one more pattern before flying to his home airport. The pilot stated that, during the landing flare, the airplane "seemed as if it was being pushed down." The left wing struck the runway, the airplane landed on the right main landing gear, and the airplane then bounced. The propeller struck the ground, and the airplane exited the right side of the runway and then stopped.

The airplane sustained substantial damage to the left wing spar.

The METAR at the airport about the time of the accident reported that the wind was calm.

The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's improper landing flare, which resulted in a bounced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA451
Event ID
20180730X45055
Case number
GAA18CA451
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. 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: b2220729d036d7985d06ec66f675e915932cebcc9eb4aaf14d6439d8109326f1; retrieved 2026-09-16T08:01:39.708Z.