WPR21LA176 · Vans RV4
Vans RV4 · Accident: loss of control in flight on approach
From Sedona Airport (KSEZ) to an unrecorded destination
Event
- NTSB case
- WPR21LA176
- 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
- Event fatalities
- Unknown
- 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
- N345DL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sedona Airport (KSEZ), Sedona, AZTo not recorded
- Aircraft age
- About 27 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
- Approach · VFR pattern final
- 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 › Task performance
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, as he approached the airport, he noted there was turbulence, and that the windsock was indicating light winds. While on the short-final leg of the traffic pattern for runway 16, the airplane encountered a downdraft. The airplane’s sink rate increased and in response, the pilot applied full engine power. Despite his attempt to arrest the descent, the airplane touched down about 200 ft before the runway in soft terrain. The airplane nosed over coming to rest inverted. Both wings were substantially damaged.
Probable cause
The pilot’s failure to maintain airplane control while compensating for a downdraft during landing, which resulted in the airplane touching down short of the runway on soft terrain and nosing over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21LA176
- Event ID
- 20210426102978
- Case number
- WPR21LA176
- 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: 269fbbc604b64133df00a60665053c4e6e5801582e474db37b57be040db1e114; retrieved 2026-09-16T13:59:04.935Z.