# Incident 20160409024529I: Cessna 510, April 9, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 9, 2016, 13:58 local time
- Airport: Phoenix-Mesa Gateway
- Damage: No damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Operator: 71AA
- Aircraft: N885RS, registered now (https://openairdocs.org/aircraft/N885RS) (OpenAirDocs)
- Registry model: Cessna 510 (registry code 2076617, https://openairdocs.org/model/cessna-510) (OpenAirDocs)
- Registry engine: Pratt & Whitney Canada PW615F-A (registry code 52282, https://openairdocs.org/engine/pratt-whitney-canada-pw615f-a) (OpenAirDocs)
- Reported make and model: CESSNA 510
- Reported engine: P&W CANADA PW615F-A
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,699 total, 125 in this make and model, 30 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160409024529I

## Narrative

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

AIRCRAFT WAS BEING FLOWN ON A PART 91 TRAINING FLIGHT. INITIAL FLIGHT WAS TO BE CONDUCTED FROM SDL TO FLG FOR INSTRUMENT PROFICIENCY. WHILE APPROACHING FLG PILOT ASKED FOR INSTRUMENT APPROACH TO RWY 21. THEY RECEIVED DELAY VECTOR AND SLOWED AIRCRAFT TO BELOW 185 KTS AND DROPPED THE FLAPS. AT THAT POINT THEY RECEIVED A "FAILED FLAPS" INDICATOR ON THE ANNUNCIATOR PANEL. THE PILOT ASKED FOR A HOLD WHILE THEY TRIED TO WORK OUT THE FLAP MALFUNCTION ISSUE. THE PILOT AND CO-PILOT ATTEMPTED TO CYCLE FLAPS AND FLAP CIRCUIT BREAKER TO CLEAR THE FLAP FAILURE. WHEN THEY DETERMINED THEY COULD NOT CHANGE FLAP SETTINGS THE CO-PILOT WENT AFT AND VERIFIED BOTH FLAPS WERE IN TAKE-OFF POSITION AND WERE NOT ASYMMETRICAL. PILOT DETERMINED HE COULD FLY IN FLAP EXTENDED CONDITION. HE REQUESTED TO DEVIATE TO WILLIAMS GATEWAY AIRPORT WHERE A MAINTENANCE FACILITY COULD LOOK AT THE FLAP ISSUE. THE PILOT ADVISED ATC HE COULD NOT EXCEED 185 KTS DURING THE FLIGHT AND WAS CLEARED TO IWA. UPON ARRIVAL TO IWA THE CO-PILOT CALLED THE TOWER AND EXPLAINED THEY WERE LANDING WITH FLAP ISSUE. THE AIRCRAFT WAS CLEARED TO LAND ON RWY 21. FIRE TRUCKS WERE DEPLOYED AND THE AIRCRAFT LANDED WITH A LONG ROLLOUT, BUT WAS ABLE TO TAXI TO MAINTENANCE WITHOUT FURTHER PROBLEMS.

MAINTENANCE FACILITY AT IWA INSPECTED THE AIRCRAFT AND VERIFIED THE FLAPS WERE STUCK IN T.O. POSITION. TROUBLESHOOTING WAS PERFORMED BUT NO CLEAR INDICATION OF THE REASON FOR THE FAILURE WAS FOUND. MAINTENANCE REPLACED SEVERAL FLAP SYSTEM COMPONENTS AND TESTED FLAP OPERATION. THE FLAPS FUNCTIONED SATISFACTORILY. AIRCRAFT WAS RETURNED TO SERVICE.

DURING THE NEXT FLIGHT (ANOTHER TRAINING FLIGHT) WHICH WAS CONDUCTED FROM IWA TO FLG THE SAME SITUATION HAPPENED WITH THE FLAPS FAILING WHILE BEING DEPLOYED FOR LANDING AGAIN. AFTER VERIFICATION OF THE FLAP POSITION THE PILOT RETURNED TO IWA WITHOUT LANDING AT FLG.

MAINTENANCE TROUBLESHOT THE FLAP SYSTEM AGAIN AND FOUND THE LH PROXIMITY SWITCH FAILED WHEN IT WAS COLD SOAKED WHICH CAUSED THE FLAPS TO GET STUCK IN THE TO POSITION. THE PROXIMITY SWITCH WAS REPLACED AND RE-TESTED. FLAP SYSTEM FUNCTIONED AS EXPECTED.

THE AIRCRAFT WAS RETURNED TO SERVICE AND HAS CONDUCTED SEVERAL FLIGHTS TO OTHER AIRPORTS AND HAS HAD NO FURTHER OCCURRENCE OF FLAP FAILURE.

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.