FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13FA061 · Piper PA28 181

25 Nov 2012 · Aurora, UT, United States

Piper PA28 181 · Accident: loss of lift en route

From Fillmore Municipal Airport (FOM) to Northeast Wyoming Regional Airport (GCC)

Report a problem

Event

NTSB case
WPR13FA061
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
3 · 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

Piper PA28 181

Aircraft type
Piper PA28
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
N8314E
Operator
Matthew W Ahrens · private individual
Onboard fatalities
Unknown
Route
From Fillmore Municipal Airport (FOM), Fillmore, UTTo Northeast Wyoming Regional Airport (GCC), Gillette, WY
Aircraft age
About 30 years (built 1982)
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
En route · climb to cruise
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 lift
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 › Action/decision

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

NTSB narrative

Family members reported to the Federal Aviation Administration that the airplane was overdue on the cross-country flight. One week after the initial notification, the wreckage was located in the upper end of a canyon about 11 nautical miles west of the departure airport at an elevation of 8,992 feet mean sea level (msl) in a grove of trees. A ridge, which was located directly in front of and on the airplane's flightpath about 950 feet from the wreckage site, was measured at 9,186 feet msl. Evidence at the accident site indicated that the airplane initially impacted the trees on a southeasterly heading in a level attitude and that its left wing subsequently impacted a tree. The impact rotated the airplane counter-clockwise, and it subsequently came to rest upright on a northwesterly heading about 150 feet from the first point of impact. The airplane was found relatively intact except for the separation of the left wing. A postcrash fire consumed the cabin and cockpit areas; the pilot had refueled before departure. Postaccident examination of the airframe and engine revealed no mechanical anomalies that would have precluded normal operation. Although no hazardous weather conditions were reported in the area at the time of the accident, unexpected turbulent conditions can occur in mountain canyons. Further, the density altitude was calculated to be 9,663 feet, which would have adversely affected the airplane's performance. A family member, who was a pilot, reported that, before the accident pilot departed on the first leg of the three-leg flight, he assisted him in calculating the airplane's weight and balance for each leg. He reported that, for each calculation, he used the estimated weight of each passenger, the baggage, the two dogs, a rifle, and full fuel and that, although the airplane was right at its maximum gross takeoff weight for each leg, it was within its weight and balance limits. He stated that the accident pilot had made this same cross-country flight three or four times previously but that he did not know the extent of the pilot's mountain-flying experience. The pilot's decision to fly in a canyon in high-density altitude conditions near the airplane's maximum gross weight likely contributed to the accident.

The airplane was likely equipped with a 121.5/243-MHz emergency locator transmitter (ELT). Due to fire damage, it could not be determined whether the ELT switch was in the armed position or whether the ELT activated immediately after impact. Regardless, the 121.5-MHz signal would only have been detected by other aircraft flying in the remote area because satellite monitoring for 121.5-MHz ELT signals ceased in February 2009. Search and Rescue (SAR) operations, which commenced the day following the accident, took 7 days. During this time period, the Civil Air Patrol from three states flew a total of 86 missions, and local law enforcement agencies conducted additional SAR missions. SAR operations were protracted due to the lack of flight following services, ELT signal and radar data, and a digital emergency signal from a 406-MHz ELT or other satellite emergency notification device and the fact that the white airplane crashed and fragmented in a snowy, forested area, which made visual detection difficult.

Two passengers initially survived the accident. They were found at the accident site wearing t-shirts and jeans; however, they were observed with warm weather coats before their departure on the day of the accident. It could not be determined whether any survival equipment was on board the airplane, but none was observed at the accident site; any survival gear may have been consumed by the postcrash fire. No evidence indicated that the survivors attempted to make an overnight shelter. The temperatures at the accident site, which was in a snow-covered area, were reportedly in the high teens to low 20s the night of the accident. The autopsy for both passengers indicated that the cause of death included hypothermia. Therefore, the two passengers did not survive the first night after the accident due to exposure to the cold temperature and the generally inclement weather conditions. It is not known whether an immediate 406-MHz ELT signal would have allowed SAR responders to reach the scene of the accident before the deaths of the two passengers; however, such a signal detection would have initiated an immediate search and greatly enhanced the opportunity for the accident site to be located more quickly.

Probable cause

The pilot's failure to maintain clearance with terrain while maneuvering in a remote mountainous region. Contributing to the accident was the pilot's improper decision to traverse the remote mountainous area in high-density altitude conditions with the airplane near its maximum gross weight. Contributing to the delay in the search and rescue (SAR) was the lack of a 406-MHz ELT signal, which would have allowed SAR responders to initiate a more timely search and find the accident site more quickly.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13FA061
Event ID
20121202X23953
Case number
WPR13FA061
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: 81279cd6b9a2353d9165d69f8f26274efec5fc2ae0e562e54e3178fa40e6a846; retrieved 2026-09-14T15:49:47.061Z.