# NTSB DEN02LA049: Piper PA-28R-201, N171M, Beaver, UT, June 1, 2002 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: June 1, 2002, 14:20 local (20:20 UTC) - Place: Beaver, UT - Coordinates: 38.208332, -112.658332 - Nearby events: https://openairdocs.org/map.md?lat=38.2083&lon=-112.6583&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor, 1 uninjured - Status: Completed, report January 16, 2003 - Report: Approved by Office Director - Parties: FAA Flight Standards District Office - NTSB case key (mKey): 54885 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DEN02LA049 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54885/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54885 - Page: https://openairdocs.org/ntsb/DEN02LA049 ## Probable cause the pilot's selection of unsuitable terrain on which to make a forced landing. Contributing factors were mountain waves (wind shear) and crosswind. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight encounter with weather, cruise - normal - weather condition - mountain wave (contributing factor) - weather condition - windshear (contributing factor) - In flight encounter with weather, approach - vfr pattern - final approach - weather condition - crosswind (contributing factor) - go-around - attempted, pilot in command - On ground/water encounter with terrain/water, landing - roll - unsuitable terrain or takeoff/landing/taxi area - selected, pilot in command (cause) - terrain condition - rough/uneven (contributing factor) ## Analysis The stall warning was activating 15 knots higher than it was supposed to while the airplane was in a climb. The pilot advised ARTCC that he was experiencing wind shear. He was told there was no reported wind shear in the area and to maintain 13,000 feet. The pilot was unable to maintain 13,000 feet, and descended to 12,000 feet, then to the minimum en route altitude of 11,000 feet. Unable to maintain this altitude, the pilot descended to 10,500 feet, cancelled his IFR flight plan, and descended further to 9,500 feet, at which point radio communications with ARTCC were lost. The airplane was yawing and "the ball (turn coordinator) was in the right side." The pilot held "full right aileron deflection to keep the [air]plane from turning." He attempted to make a precautionary landing at an airport. A left crosswind aided in keeping the airplane on track, but he was "unable to use the rudder to straighten out the [air]plane to land." At 100 feet above the ground, the pilot attempted a go-around. With flaps up, landing gear down, and full power applied, the airplane would not climb but descended slowly instead. The pilot made a forced landing in an open field 1 mile south of the airport. In the ensuing landing, both wings were damaged, the aft portion of the fuselage was wrinkled, and the main gear was torn off. An inspection of the aircraft after the accident disclosed no anomalies with the flight control system or the engine. Flight control continuity was confirmed. ## Factual narrative On June 1, 2002, approximately 1420 mountain daylight time, a Piper PA-28R-201, N171M, was substantially damaged when it struck terrain during a precautionary landing at Beaver, Utah. The private pilot received no injuries, but his passenger received minor injuries. Day visual meteorological conditions prevailed, and an IFR flight plan had been filed for the cross-country flight being conducted under Title 14 CFR Part 91. The flight originated in San Diego, California, at 0930 Pacific daylight time, and was en route to Logan, Utah. In an unsigned statement written in third person and submitted along with the accident report, the writer said the stall warning was activating 15 knots higher than it was supposed to while the airplane was in a climb. The pilot advised Los Angeles Air Route Traffic Control Center (ARTCC) that he was experiencing wind shear. ARTCC said there was no reported wind shear in the area and to maintain 13,000 feet. The pilot was unable to maintain 13,000 feet, and descended to 12,000 feet, then to the minimum en route altitude of 11,000 feet. Unable to maintain this altitude, the pilot descended to 10,500 feet, cancelled his IFR flight plan, and descended further to 9,500 feet, at which point radio communications with ARTCC were lost. A United Air Lines flight relayed communications between N171M and ARTCC. The writer said the airplane was yawing and "the ball (turn coordinator) was in the right side." The pilot held "full right aileron deflection to keep the [air]plane from turning." He attempted to make a precautionary landing on runway 13 at Beaver Municipal Airport. A left crosswind aided in keeping the airplane on track, but the pilot was "unable to use the rudder to straighten out the [air]plane to land." At 100 feet above the ground, the pilot attempted a go-around. With flaps up, landing gear down, and full power applied, the airplane would not climb but descended slowly instead. The pilot made a forced landing in an open field 1 mile south of the airport. In the ensuing landing, both wings were damaged, the aft portion of the fuselage was wrinkled, and the main gear was torn off. A statement given to the Beaver County Sheriff's Office was similar to the one submitted with the accident report. An inspection of the aircraft after the accident disclosed no anomalies with the flight control system or the engine. Flight control continuity was confirmed. Calm winds were recorded at Milford, Utah, located 21 miles west-northwest of the accident site, 26 minutes before the accident. ## Aircraft - Registration: [N171M](https://openairdocs.org/deregistered/N171M-2014-09-09), registration cancelled 2014-09-09, S/N 28R-7837051 (OpenAirDocs) - Reported make and model: Piper PA-28R-201 - Registry model: [Piper PA-28R-201](https://openairdocs.org/model/piper-pa-28r-201) (registry code 7102816) (OpenAirDocs) - Category: Airplane - Serial number: 28R-7837051 - Engines: Lycoming IO-360-C1C6 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Simon D. Bowles - Registered owner: David S. Bowles - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, May 28, 2002, 5 hours before - Departed: SEE, San Diego, CA - Destination: LGU, Logan, UT - Flight plan: IFR - Airport: U52, Beaver Municipal ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 24; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; last flight review April 9, 2002; seat: left; flight hours: 327 total, 239 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 41 °F - Altimeter: 29.88 inHg - Observed at: MLF, 21 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20020601012999A](https://openairdocs.org/incident/20020601012999A), Jun 1, 2002: Piper PA28R201, Beaver, UT, Substantial damage. (-23) The pilot states he was on an IFR flight plan from an airport near san diego, CA to logan, UT. He stated he had decided to stop at Beaver, UT to wait out… ## Docket (3 files) The files NTSB released with the investigation on November 7, 2002, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54885. 616 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 570 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40170736&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Supplement S (item 2, .PDF, 35 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40170738&FileExtension=.PDF&FileName=Supplement%20S-Master.PDF - Weather Reports and Records (item 3, .PDF, 11 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40170740&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.