FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR19CA197 · Avid AVID MAGNUM

20 Jul 2019 · Yellow Pine, ID, United States

Avid AVID MAGNUM · Accident: collision during takeoff/landing

From Johnson Creek Airport (3U2) to Reed Ranch Airport (I92)

Report a problem

Event

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

Avid AVID MAGNUM

Aircraft type
Avid MAGNUM
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
N777DV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Johnson Creek Airport (3U2), Yellow Pine, IDTo Reed Ranch Airport (I92), Yellow Pine, ID
Aircraft age
About 21 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
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
Collision during takeoff/landing
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot reported that, after the airplane touched down on the grass airstrip and rolled about 130 ft, the nose landing gear impacted a depression and then bent aft. The nosewheel dragged through the grass about 30 ft, and the airplane then nosed over and came to rest inverted. The pilot added that this was the first time he had landed at this airstrip and that he was not aware of the hazards on the rough surface. The airplane sustained substantial damage to the rudder and wing struts. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's improper decision to land on a rough, grass airstrip, which resulted in the nose landing gear collapsing and a subsequent nose-over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR19CA197
Event ID
20190720X80210
Case number
WPR19CA197
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. 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: b5b35618d3caa101f6caefcd782602367d6de91e7379695e53192ef8103a951c; retrieved 2026-09-16T09:28:48.123Z.