ASN Wikibase Occurrence # 385271
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 5 November 2000 |
Time: | 15:55 LT |
Type: | Piper PA-28R-200 |
Owner/operator: | Air West Flying Club |
Registration: | N3032R |
MSN: | 28R-35657 |
Total airframe hrs: | 4045 hours |
Engine model: | Avco Lycoming iO-360 |
Fatalities: | Fatalities: / Occupants: 2 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | TEEC NOS POS, AZ -
United States of America
|
Phase: | Unknown |
Nature: | Private |
Departure airport: | PAGE, AZ (KPGA) |
Destination airport: | BROOMFIELD, CO (KBJC) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:A Safety Board staff meteorologist performed a weather analysis for the flight. Airmet's for instrument flight rules, mountain obscuration, turbulence, and icing were valid for all portions of the airplane's flight route. The airplane brokeup in flight. The pilot contacted the FAA Prescott Automated Flight Service Station (AFSS) by telephone from Page, Arizona, at 1306, and requested a forecast for Pueblo, Colorado. The forecast was for winds gusting to 30 knots; showers in the vicinity; scattered clouds at 4,000 agl; broken clouds at 7,000 agl; lowering clouds after 1700; and an increase in occasional rain and snow showers. The pilot was issued an Airmet for icing in Colorado mountain obscuration, and from Phoenix to Denver, turbulence from the surface to 39,000 feet. During the briefing the pilot told the briefer that he was "trapped in Page, trying to get back the Denver; when does it look like the system is going to clear out a little, do you have any information on that?" At 1420, the pilot contacted the Prescott AFSS by radio over Kayenta, Arizona, about 60 miles west of the accident site. He requested, and was given, the current weather conditions at Grand Junction and Farmington, New Mexico. He requested three other locations in Colorado; all were marginal for visual flight. At 1425, the pilot told the briefer "we'll be heading the southern route." The pilot did not file a flight plan. On November 6, at 1155, the Air Force Rescue Coordination Center (AFRCC) provided notification of an emergency crash locator beacon signal. Subsequently the wreckage was located at 1845, in the Carrizo Mountains, at an elevation of about 8,610 feet msl, approximately 51 nautical miles on the 260-degree radial from the Farmington VOR navigational facility. According to accident flight reconstruction information, the airplane departed Broomfield, Colorado, on November 3, and was returning the day of the accident. The pilot had not told the flying club operator of his intended destination, only that he would be back with the plane on the 5th about 1800. The airplane was refueled at North Las Vegas, on November 4, and at Page on November 5. According to fuel service witness information at Page, the airplane made a fuel stop and departed. The fuel invoice was paid at 1338. According to the flying club, it is their written and member signed policy to require all members to file flight plans for flights over 50 nautical miles or more, and all cross-country flight destinations are to be given to the operator. Information recovered from a notepad found in the wreckage documented a flight route from Broomfield (Jeffco), Monarch Pass, Blue Mesa, Dove Creek, Page, and Las Vegas, for a total distance of 545 miles.
Probable Cause: In-flight loss of control resulting in airframe structural failure. Contributing to the accident was the pilot's inadvertant visual flight into instrument meteorological conditions.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | LAX01FA036 |
Status: | Investigation completed |
Duration: | 1 year and 3 months |
Download report: | Final report |
|
Sources:
NTSB LAX01FA036
History of this aircraft
Other occurrences involving this aircraft Location
Revision history:
Date/time | Contributor | Updates |
04-Apr-2024 16:44 |
ASN Update Bot |
Added |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation