ASN Wikibase Occurrence # 210285
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: | Saturday 25 February 2017 |
| Time: | 20:40 |
| Type: |  Cessna 172H |
| Owner/operator: | Private |
| Registration: | N3712F |
| MSN: | 17255207 |
| Year of manufacture: | 1966 |
| Total airframe hrs: | 7372 hours |
| Engine model: | Continental O-300-D |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Panguitch, UT -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Page, AZ (PGA) |
| Salt Lake City, UT (U42) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The noninstrument-rated private pilot was making a 220-nautical mile (nm) cross-country flight under visual flight rules over mountainous terrain in dark night instrument meteorological conditions. Radar data revealed that the airplane was flying in a northwest direction, proceeding en route between 9,100 ft and 9,900 ft mean sea level (msl). The last radar return, which occurred about 1 hour after takeoff, showed that the airplane was about 80 nm northwest of the departure airport and about 3 nm southeast of the accident site. A short time later the airplane impacted remote, snow-covered, mountainous terrain on a southwest heading at an elevation of 7,350 ft. The changes in heading and altitude between the end of the radar data and the impact suggest that the pilot began maneuvering the airplane after radar contact was lost. A survey of the accident site revealed that the damage to the airplane and the linear debris path was consistent with controlled flight into terrain. All airplane components necessary for flight were accounted for at the accident site. Additionally, a post-accident examination of the airframe and engine did not reveal evidence of any mechanical anomalies that would have precluded normal operation.
Weather surveillance radar revealed an area of snow showers over the accident site, and an infrared satellite image depicted a band of low stratiform clouds over the accident site with tops near 14,000 ft msl. The cloud bases were estimated at 8,700 ft msl. A meteorological impact statement for the area warned of marginal visual flight rules to instrument flight rules conditions in snow showers. Dark nighttime conditions existed with no illumination of the moon at the time of the accident. The area surrounding the accident site was uninhabited, and there would have been no ground lighting visible to the pilot. It is likely that the airplane encountered instrument meteorological conditions (the band of clouds), and the pilot descended and turned to exit the cloud layer but was unable to establish visual contact with the ground before impacting terrain in the dark nighttime conditions.
There was no record of the pilot getting an official weather briefing. If he had gotten a briefing, he would have been told "VFR not recommended" and this may have prevented the accident.
Probable Cause: The pilot's continued visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain. Contributing to the accident were the pilot's inadequate preflight weather planning and his poor decision-making.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 01-May-2018 13:43 | ASN Update Bot | Added |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation