# Incident 20111218030129I: Cessna 177RG, Washington Coun, PA, December 18, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 18, 2011, 16:08 local time
- Place: Washington Coun, PA
- Airport: Washington County
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 40.1365° N, 80.2902° W: Placed by OpenAirDocs at WASHINGTON COUNTY (AFJ), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.1365&lon=-80.2902&mi=10
- Aircraft: N2058Q, registered now (https://openairdocs.org/aircraft/N2058Q) (OpenAirDocs)
- Registry model: Cessna 177RG (registry code 2073709, https://openairdocs.org/model/cessna-177rg) (OpenAirDocs)
- Registry engine: Lycoming IO-360-A1B6D (registry code 41593, https://openairdocs.org/engine/lycoming-io-360-a1b6d) (OpenAirDocs)
- Reported make and model: CESSNA 177RG
- Reported engine: LYCOMING IO-360-A1B6D
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 170 total, 12 in this make and model, 19 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20111218030129I

## Narrative

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

PILOT INDICATED THAT SHE HAD BEEN DOING TOUCH AND GO LANDINGS AT THE WASHINGTON COUNTY AIRPORT (AFJ), AS SOLE OCCUPANT OF THE AIRPLANE, FOR APPROXIMATELY TWO HOURS PRIOR TO THE INCIDENT. ^PRIVACY DATA OMITTED^ INDICATED SHE HAD DEPARTED THE TRAFFIC PATTERN TO DO SOME ADDITIONAL AIR WORK AND AS SHE WAS RETURNING FOR A FINAL LANDING, AHELICOPTER REPORTED ON THE UNICOM FREQUENCY THAT IT WAS ON THE DOWN-WIND IN FRONT OF HER, AND THEN REPORTEDTHAT HE WAS NUMBER TWO, BEHIND HER, FOR THE LANDING AT THE AIRPORT. ^PRIVACY DATA OMITTED^ EXTENDED HER DOWNWIND TO ALLOW THE HELICOPTER TO LAND BEFORE HER. ^PRIVACY DATA OMITTED^ INDICATED SHE WAS DISTRACTED AND NEVER SAW THE HELICOPTER ENTER THE TRAFFIC PATTERN, AND AS A RESULT FAILED TO EXTEND THE LANDING GEAR. FURTHER INVESTIGATION BY AIRWORTHINESS INSPECTOR JEFF HALLIDAY REVEALED THAT A WIRE CONNECTED TO THE LANDING GEAR HORN ON THE THROTTLE LINKAGE WAS BROKEN, THEREFORE ^PRIVACY DATA OMITTED^ DID NOT RECEIVE THE AURAL WARNING THAT THE LANDING GEAR WAS NOT DOWN AND LOCKED. ^PRIVACY DATA OMITTED^ STATED SHE HAD DONE APPROXIMATELY 20 TOUCH AND GO LANDINGS IN THAT TWO HOUR PERIODAND THOUGHT SHE HAD EXTENDED THE LANDING GEAR ON HER FINAL APPROACH AND AS A RESULT LANDED THE AIRPLANE WITH THE LANDING GEAR UP.

## Other reports on N2058Q (2)

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

- [Incident 20160827017389I](https://openairdocs.org/incident/20160827017389I), Aug 27, 2016: Cessna 177RG (N2058Q), Atlanta, GA, No damage. During approach in to fulton cnty airport, pilot noticed no landing gear down and lock indication. Pilot radioed tower for visual check. Gear appeared down.…
- [Incident 20000926024919I](https://openairdocs.org/incident/20000926024919I), Sep 26, 2000: Cessna 177RG (N2058Q), Oakland, CA. (-23) PIC taxied toward active runway, upon reaching run-up area PIC positioned a/c close to edge of taxiway to avoid traffic conjection and conducted engine…

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.