FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA21LA299 · Vans RV6 A

25 Jul 2021 · Ocracoke, NC, United States

Vans RV6 A · Accident: nose over/nose down during landing

From Martin County Airport (MCZ) to an unrecorded destination

Report a problem

Event

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

Vans RV6 A

Aircraft type
Vans RV6
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
N464DM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Martin County Airport (MCZ), Williamston, NCTo not recorded
Aircraft age
About 19 years (built 2002)
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
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
Nose over/nose down
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 › 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 pilot reported that windspeed at the nearest weather reporting facility was 14-16 knots, and the windsock at the accident airport indicated a 90° crosswind. He stated that his approach was “too high and fast”, and he crossed the runway threshold about 70 ft above ground level (AGL) at a speed of 90 mph. About ½ way down the runway, the airplane was about 30 ft AGL at a speed of about 45 mph, and “oscillating 20° either side of center.” The pilot believed he could “straighten the flight path and touch down in time to stop” before the end of the runway. However, a gust of wind “would not allow the aircraft to slow” and it ran off the end of the runway about 20 mph, nosed over, and sustained substantial damage to the vertical and horizontal stabilizers, the rudder, and the left wing.

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

Probable cause

The pilot's failure to perform a go-around during the unstabilized approach, which resulted in the airplane landing too far down the runway, and a subsequent runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA21LA299
Event ID
20210726103548
Case number
ERA21LA299
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: 62a26f4f7f95e41eb5b5ab9aadf71825b4e328c866dcbdfd9c5b28e98c58c54a; retrieved 2026-09-16T14:19:28.985Z.