# NTSB FTW02LA166: Piper PA-22-160, N9051D, Nageezi, NM, May 30, 2002

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: May 30, 2002, 16:45 local (22:45 UTC)
- Place: Nageezi, NM
- Coordinates: 36.268333, -107.746391
- Nearby events: https://openairdocs.org/map.md?lat=36.2683&lon=-107.7464&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 6, 2002
- Report: Approved by Office Director
- Parties: Federal Aviation Administration (FSDO)
- NTSB case key (mKey): 54815
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=FTW02LA166
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54815/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54815
- Page: https://openairdocs.org/ntsb/FTW02LA166

## Probable cause

the pilot's failure to select a suitable landing site, which resulted in a collision with a fence.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- On ground/water collision with object, landing - roll
  - became lost/disoriented, pilot in command
  - precautionary landing, pilot in command
  - unsuitable terrain or takeoff/landing/taxi area - selected, pilot in command (cause)
  - object - fence

## Analysis

The cross-country flight departed, made one fuel stop, and was en route to its second fuel stop when the pilot deviated from the planned route due to mountainous terrain.  The planned route followed an interstate highway.  The pilot thought he had rejoined his planned route of flight; however, he began following the wrong interstate highway.  The flight traveled 70 miles, and when the pilot did not arrive at his next planned fuel stop, he decided to execute a precautionary landing to a dirt strip due to low fuel.  The airplane landed, and the right wing contacted a barbed wire fence 3/4 of the way down the airstrip.  The pilot added that when he identified the fence it was too late to execute a go-around, and the dirt was too loose to stop prior to the fence.

## Factual narrative

On May 30, 2002, at 1645 mountain daylight time, a Piper PA-22-160 airplane, N9051D, was substantially damaged when it collided with a fence during a precautionary landing near Nageezi, New Mexico.  The airplane was registered to and operated by the pilot.  The commercial pilot, sole occupant of the airplane, was not injured.  Visual meteorological conditions prevailed, and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 personal flight.  The cross-country flight originated from the Guthrie Municipal Airport, Guthrie, Oklahoma, and was destined for the Page Municipal Airport, Page, Arizona.

On May 30, 2002, the pilot purchased the airplane in Guthrie and departed for a flight to his home base in Page.  The flight made its first fuel stop in Guymon, Oklahoma, and then departed with the next intended fuel stop at Gallup, New Mexico.  The pilot stated that he was following Interstate 40 (I-40), when he encountered mountainous terrain east of Albuquerque, New Mexico.  He elected to alter his route of flight to the north of the Class C airspace around Albuquerque, and planned on rejoining I-40 west of Albuquerque.  The pilot deviated and began following Interstate 550, which he believed to be I-40.  The pilot was navigating using a world aeronautical chart.  The flight traveled 70 miles and when the pilot did not reach Gallup, he began searching for a precautionary landing site due to low fuel.  He elected to land on what appeared to be a dirt airstrip.  The airplane landed, and the airplane's right wing contacted a barbed wire fence 3/4 of the way down the dirt strip.  The pilot added that when he identified the fence it was too late to execute a go-around, and the dirt was too loose to stop prior to the fence.  The right wing root and right wing strut were structurally damaged.

## Aircraft

- Registration: [N9051D](https://openairdocs.org/aircraft/N9051D), registered now, S/N 22-6191 (OpenAirDocs)
- Reported make and model: Piper PA-22-160
- Registry model: [Piper PA-22-160](https://openairdocs.org/model/piper-pa-22-160) (registry code 7102214) (OpenAirDocs)
- Category: Airplane
- Serial number: 22-6191
- Airframe hours: 2061.5
- Engines: Lycoming O-320-B2A 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Craig S. Humes
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, April 1, 2002, 8 hours before
- Departed: GUY, Guymon, OK
- Destination: GUP, Gallup, NM

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 52; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: helicopter, airplane; medical: class 2, valid medical--w/ waivers/lim; last flight review January 29, 2001; seat: left; flight hours: 10,082 total, 9 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 250° at 9 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 93 °F, dew point 30 °F
- Altimeter: 30.00 inHg
- Observed at: FMN, 38 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 20020530010219A](https://openairdocs.org/incident/20020530010219A), May 30, 2002: Piper PA22160, Nageezi, NM, Substantial damage. (.19) On may 30, 2002, at 1645 mountain daylight time, a Piper PA-22-160 airplane, N9051D, was substantially damaged when it landed hard at a private airstrip…

## Docket (1 files)

The files NTSB released with the investigation on October 24, 2002, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54815. 468 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 468 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40439389&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.
