FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20LA310 · Vans RV4

19 Sept 2020 · Clovis, NM, United States

Bishop Ag Air Vans RV4 · Accident: loss of control in flight during initial climb

From Aero Tech Inc Airport (NM42) to Heber Springs Municipal Airport/Charlie Evans Field (HBZ)

Report a problem

Event

NTSB case
WPR20LA310
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 RV4

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
N250LB
Onboard fatalities
Unknown
Route
From Aero Tech Inc Airport (NM42), Clovis, NMTo Heber Springs Municipal Airport/Charlie Evans Field (HBZ), Heber Springs, AR
Aircraft age
About 22 years (built 1998)
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
Initial climb
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 › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot was departing from an airport when the accident occurred. During the initial climb, he became momentarily distracted when his mobile phone rang. He looked down at the phone, which was on the floor, and within 2 seconds, the airplane had rolled inverted. At this time, the pilot looked outside the cockpit and became aware of the inflight upset. He immediately recovered the airplane into an upright attitude, but the airplane impacted the ground, nosed over, and came to rest inverted. The pilot reported no preimpact mechanical anomalies or malfunctions that could have precluded normal operation.

Probable cause

The pilot’s failure to maintain lateral control during initial climb due to distraction, which resulted in an in-flight upset and impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20LA310
Event ID
20200919X60939
Case number
WPR20LA310
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: f3694b74ec6ac737cdda268cdd16c058c70ef38d604263481a8a90e773fdf363; retrieved 2026-09-16T13:04:09.269Z.