ASN Wikibase Occurrence # 150903
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Sunday 25 November 2012 |
Time: | 13:00 |
Type: | Piper PA-28-181 Archer II |
Owner/operator: | Private |
Registration: | N8314E |
MSN: | 28-8390016 |
Year of manufacture: | 1982 |
Total airframe hrs: | 3916 hours |
Engine model: | Lycoming O-360-A4M |
Fatalities: | Fatalities: 3 / Occupants: 3 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | Near the Fillmoore, Utah, airport -
United States of America
|
Phase: | En route |
Nature: | Private |
Departure airport: | Fillmore, UT (FOM) |
Destination airport: | Gillette, WY (GCC) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
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
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.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | WPR13FA061 |
Status: | Investigation completed |
Duration: | 1 year and 8 months |
Download report: | Final report |
|
Sources:
NTSB
FAA register:
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=8314E https://flightaware.com/photos/view/563408-9f7294f8744e8cb6d0443f01bb18a6e5afc45779/aircrafttype/P28A/size/xga Location
Revision history:
Date/time | Contributor | Updates |
28-Nov-2012 01:24 |
gerard57 |
Added |
28-Nov-2012 10:22 |
Geno |
Updated [Time, Aircraft type, Registration, Cn, Location, Departure airport, Destination airport, Source, Narrative] |
28-Nov-2012 10:52 |
Geno |
Updated [Time, Aircraft type, Registration, Cn, Location, Departure airport, Destination airport, Source, Narrative] |
03-Dec-2012 04:17 |
gerard57 |
Updated [Location, Source, Damage, Narrative] |
21-Dec-2016 19:28 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
28-Nov-2017 13:53 |
ASN Update Bot |
Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
02-Jul-2022 17:16 |
rvargast17 |
Updated [Source, Damage] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation