FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR26LA180 · Cessna 172

10 May 2026 · Marysvale, UT, United States

Cessna 172 · Accident: low altitude operation/event while maneuvering

From Richfield Municipal Airport (RIF) to an unrecorded destination

Report a problem

Event

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

Cessna 172

Aircraft type
Cessna 172
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
N6643A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Richfield Municipal Airport (RIF), Richfield, UTTo not recorded
Aircraft age
About 70 years (built 1956)
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
Maneuvering · low-altitude flying
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
Low altitude operation/event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological

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

NTSB narrative

The pilot reported that while flying along the west side of Monroe Mountain about 1,000 ft above ground level, the airplane encountered a downdraft near a river drainage at the southern end of the valley. The pilot applied full engine power, maneuvered to avoid a tree near the right wingtip, and attempted to maintain airspeed. During the maneuver, the airplane collided with another tree that the pilot had not seen. The airplane subsequently impacted terrain and was consumed by a postimpact fire. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's failure to maintain clearance from trees while maneuvering in mountainous terrain prior to encountering a downdraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR26LA180
Event ID
20260512202970
Case number
WPR26LA180
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, 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: 0eaa09cb9fa4ac6e313bdc72f4331b0cab9c43b430979e065291d76716dbf385; retrieved 2026-09-16T21:26:29.865Z.