# Incident 20111104026259I: Cessna 172I, Fort Sumner, NM, November 4, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 4, 2011, 16:48 local time
- Place: Fort Sumner, NM
- Damage: Minor damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 34.4868° N, 104.2178° W: Placed by OpenAirDocs: center of Fort Sumner, NM, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=34.4868&lon=-104.2178&mi=10
- Aircraft: N35668, registered now (https://openairdocs.org/aircraft/N35668) (OpenAirDocs)
- Registry model: Cessna 172I (registry code 2072426, https://openairdocs.org/model/cessna-172i) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172I
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 211 total, 211 in this make and model, 21 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20111104026259I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

PILOT WAS LANDING AT QUAY COUNTY, NEW MEXICO ON A PRIVATE RANCH. THE PILOT WAS ON FINAL WHEN HE HEARD A LOUD NOISE AND HIS SON TOLD HIM HE HAD JUST HIT A POWER LINE. THE POWER LINE THEY HIT WAS A SMALL SINGLE PHASE LINE.  THE AIRCRAFT WAS BEING OPERATED ON A PRIVATE FLIGHT WHEN THE INCIDENT OCCCURRED.  THERE WERE NO INJURIES.

## Other reports on N35668 (1)

Matched to the same aircraft by N-number and date.

- [Incident 20101030049279I](https://openairdocs.org/incident/20101030049279I), Oct 30, 2010: Cessna 172I (N35668), Clovis, NM, Minor damage. N35668, a CE-172I, during landing roll out the pilot stated "a gust of wind was encountered", changing the pitch of the aircaft causing the propeller to strike…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.