FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20FA009 · Vans RV4 UNDESIGNAT

14 Oct 2019 · Cameron, NC, United States

Vans RV4 UNDESIGNAT · Accident: loss of control in flight on approach

From Woodward Field (CDN) to Rooster Field (84NC)

Report a problem

Event

NTSB case
ERA20FA009
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
1 · 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 RV4 UNDESIGNAT

Aircraft type
Vans RV4
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
N4332J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Woodward Field (CDN), Camden, SCTo Rooster Field (84NC), Cameron, NC
Aircraft age
About 27 years (built 1992)
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
Approach · VFR pattern base
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot of the experimental, amateur-built airplane departed for his home airport after attending a fly-in event. Shortly after takeoff, the airplane's canopy separated in-flight, and the pilot was able to land safely at the departure airport. Two days later, the pilot chose to fly his airplane home without the canopy and wore a full-face mask motorcycle helmet. Flight track data from an onboard GPS revealed that, after a seemingly normal flight, the airplane overflew the destination airport and entered the traffic pattern on a left downwind leg. The airplane’s groundspeed on the left base leg slowed to 57 knots, and as the airplane continued the left turn onto final approach, the last recorded groundspeed was 54 knots. The wreckage was located in a heavily wooded area near the runway’s extended centerline about .25 mile from the runway threshold. The initial impact point and main wreckage were located closely together, indicative of the airplane impacting terrain in a steep downward flightpath. Examination of the airplane and engine components revealed no evidence of preimpact mechanical malfunctions or failures, and propeller signatures were consistent with the engine producing power at the time of impact. Review of three previous GPS flight tracks all flown to the same runway in the same month as the accident flight revealed that the traffic pattern flown during the accident flight was considerably closer to the runway laterally. The closer proximity to the runway would have required steeper turns and likely more aggressive maneuvering compared to the recent traffic patterns the pilot had flown. The reason for the pilot’s decision to fly a closer traffic pattern than usual could not be determined. The pilot's decision to fly the airplane without the canopy, and with a motorcycle helmet, likely increased several risk factors for the flight. Although the kit manufacturer published no official data regarding how the airplane performed without a canopy, the manufacturer reported that its aerodynamic stall speed was likely increased, and it was possible that its elevator and rudder control effectiveness was decreased due to the change in airflow over the empennage. Additionally, the manufacturer reported the potential for pitot-static instrument error due to abnormal airflow over the airplane’s static ports.

The pilot's normal physical and perceptual cues to avoid a loss of control, such as normal airflow sounds over the canopy, were likely distorted since he had likely never flown the airplane with a motorcycle helmet and had only flown the airplane without the canopy in the previous flight. It is also likely that the pilot encountered an undesirable quartering gusting tailwind on base and final approach. Based upon the flight track data, the likely quartering tailwind, and the many risk factors added by flying the airplane without a canopy, it is likely that the pilot exceeded the airplane's critical angle of attack on the base to final turn, and the airplane entered an aerodynamic stall and spin and impacted trees and terrain short of the runway.

Probable cause

The pilot's exceedance of the airplane’s critical angle of attack during the landing approach, which resulted in a loss of control and a subsequent aerodynamic stall/spin. Contributing to the accident was the pilot's decision to fly the airplane in a configuration for which it was not certificated and in which the flight characteristics were not known.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20FA009
Event ID
20191015X65516
Case number
ERA20FA009
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: 645beb76a877261b19d47475ac565afb44f5dbabd43714638487f4a0fec0514c; retrieved 2026-09-15T07:06:54.517Z.