WPR11FA005 · Cessna 172
Cessna 172 · Accident: low altitude operation/event while maneuvering
From Bryce Canyon Airport (BCE) to Page Municipal Airport (PGA)
Event
- NTSB case
- WPR11FA005
- 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
- 2 · 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
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
- N8437A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bryce Canyon Airport (BCE), Bryce Canyon, UTTo Page Municipal Airport (PGA), Page, AZ
- Aircraft age
- Not recorded
- 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
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The employer of the pilot and passenger reported to local authorities that they had not returned from a presumed elk-spotting flight for an upcoming hunting trip. The wreckage was subsequently located in a remote canyon area in rising mountainous terrain at an elevation of 9,600 feet. There were no witnesses to the accident; however, pilots flying in the area that afternoon noted that it was too windy to fly below the ridgeline and tree movement was visible; the sky was clear. The calculated density altitude for the area was 11,178 feet. Based on the final location and heading of the airplane, it is likely that the pilot may have attempted to maneuver at a low altitude in the canyon and was unable to maintain clearance from terrain in the windy conditions and high density altitude. Postaccident examination of the airframe and engine revealed no mechanical anomalies that would have precluded normal operation.
Probable cause
The pilot's decision to conduct a low-level flight into a canyon in windy conditions at a high density altitude, which resulted in a collision with trees and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11FA005
- Event ID
- 20101009X62708
- Case number
- WPR11FA005
- 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: dcaa2fd817275a2184428cb12a784e3391b1c95aedcb9f07fd31933a5c054440; retrieved 2026-09-13T21:04:54.438Z.