# Incident 20160514006469I: Cessna 170B, Glacier View, AK, May 14, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 14, 2016, 18:22 local time
- Place: Glacier View, AK
- Airport: Glacier View
- Damage: No damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 61.8701° N, 147.8819° W: Placed by OpenAirDocs: center of Glacier View, AK, within about 9 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=61.8701&lon=-147.8819&mi=10
- Aircraft: N2885C, registered now (https://openairdocs.org/aircraft/N2885C) (OpenAirDocs)
- Registry model: Cessna 170B (registry code 2072306, https://openairdocs.org/model/cessna-170b) (OpenAirDocs)
- Registry engine: Continental C145 series (registry code 17012, https://openairdocs.org/engine/continental-c145-series) (OpenAirDocs)
- Reported make and model: CESSNA 170B
- Reported engine: CONT MOTOR C145 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, private pilot
- Pilot flight hours: 2,864 total, 1,790 in this make and model, 82 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160514006469I

## Narrative

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

05/14/2016-- AT APPROXIMATELY 1822 HOURS AIRCRAFT N2885C HAD AN ENGINE PROBLEM. THE INCIDENT WAS CALLED INTO THE ROC BY AN AIRCRAFT OVERHEAD. N2885C LEFT 9AK5 ON 05/14/2016 HEADED TO TALKEETNA FOR THE FLY IN. THE AIRCRAFT DEPARTED PATK TO PARTICIPATE IN THE AERIAL SCAVENGER HUNT EVENT. DURING THE EVENT THE AIRCRAFT ^PRIVACY DATA OMITTED^PIC AND 1 PASSENGER LANDED AT 28AK AS PART OF THE EVENT. WHEN THEY DEPARTED 28AK ENROUTE TO PATK THE PIC NOTICED A LOSS OF POWER, HE SAID HE COULD ONLY GET 900 RPM AND LOOKED FOR A PLACE TO LAND. HE LANDED WITHOUT INCIDENT IN A CLEARING APPROXIMATELY ½ MILE FROM 28AK AND CALLED ONE OF THE OTHER AIRPLANES OVERHEAD TO EXPLAIN WHAT HAPPENED (WHO INFORMED THE ROC). AT THAT POINT HE REALIZED HE HAD CELL PHONE COVERAGE SO HE CALLED A FRIEND IN TALKEETNA THAT HAS AN A & P CERTIFICATE. THE A & P HAD THE PIC CHECK NUMEROUS THINGS UNTIL HE OPENED THE ENGINE COWLING AND DISCOVERED THE CONTROL ROD TO THE PROP GOVERNOR WAS DISCONNECTED. THE PIC RECONNECTED THE CONTROL ROD WHILE TALKING TO THE A & P AND DID SEVERAL ENGINE CHECKS TO ENSURE THE ENGINE WAS OPERATING NORMALLY. THE PIC/PASSENGER TOOK OFF AND FLEW TO PATK WHERE THE A & P SAW HIM AND WELCOMED HIM BACK TO TOWN. THE NEXT DAY 05/15/2016 THE PIC/PASSENGER DEPARTED PAKT ENROUTE TO 9AK5. 05/19/2016 I CONTACTED THE PIC AND GOT THIS INFORMATION, I ALSO ASKED IF ANYONE HAD LOOKED AT THE AIRCRAFT AT ANY TIME OR IF ANY MAINTENANCE LOGBOOK ENTRIES HAD BEEN MADE SINCE THE INCIDENT ON 05/14/2016? HE SAID NO, HE SAID HE HAD CALLED HIS A & P AND ASKED HIM TO LOOK AT THE AIRPLANE WHEN HE GOT TIME.

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.