Narrative:

During visual approach to the runway as pilot not flying; received an amber 'flaps fail' cas message while extending flaps to 15 degrees. Crew immediately discontinued approach; determined the aircraft was controllable and requested vectors from tower for time to complete checklist. Tower controller handed us off to approach and again requested vectors for time to complete checklist. Approach told us to proceed to outer marker for ILS and hold as published at 3;100 ft. Since the ILS approach was already programmed into the FMS; pilot flying started proceeding to FAF and climbing to assigned altitude to begin holding. The pilot flying was working the radios and controlling the aircraft while I was completing the 'flaps fail' emergency checklist. Pilot flying was having difficulty determining what ATC had intended as none of approach plates depicted holding at the FAF. It was then noticed that the aircraft had climbed through the assigned altitude of 3;100 ft and was approaching 3;500 ft. The pilot flying immediately notified ATC and they then assigned a holding altitude of 4;000 ft. Further clarification was then received from ATC to hold inbound at the outer marker using standard turns. The emergency checklist was then completed and the flight proceeded to an uneventful partial flap landing. ATC made no further comment concerning the altitude deviation. No emergency was declared with ATC. However; it was discovered after landing that the tower had declared some type of emergency for us. A local sheriff's deputy greeted us at the FBO and requested a statement. Statements were provided by both crew members and the deputy informed us this was nothing more than a paperwork drill. Since the tower had declared some type of emergency event which activated crash/fire/rescue personnel; an administrative report was required. In the confusion of the moment; ensuring the auto pilot was capturing the assigned altitude would have eliminated this deviation.

Google
 

Original NASA ASRS Text

Title: CE680 First Officer reports Flaps Fail CAS message during approach while flaps are moving to 15 degrees. Approach assigns a hold at the FAF as published; which does not appear on the approach chart During the confusion the assigned altitude is exceeded. An uneventful partial flap landing ensues.

Narrative: During visual approach to the runway as pilot not flying; received an amber 'flaps fail' CAS message while extending flaps to 15 degrees. Crew immediately discontinued approach; determined the aircraft was controllable and requested vectors from Tower for time to complete checklist. Tower Controller handed us off to Approach and again requested vectors for time to complete checklist. Approach told us to proceed to outer marker for ILS and hold as published at 3;100 FT. Since the ILS approach was already programmed into the FMS; pilot flying started proceeding to FAF and climbing to assigned altitude to begin holding. The pilot flying was working the radios and controlling the aircraft while I was completing the 'flaps fail' emergency checklist. Pilot flying was having difficulty determining what ATC had intended as none of approach plates depicted holding at the FAF. It was then noticed that the aircraft had climbed through the assigned altitude of 3;100 FT and was approaching 3;500 FT. The pilot flying immediately notified ATC and they then assigned a holding altitude of 4;000 FT. Further clarification was then received from ATC to hold inbound at the outer marker using standard turns. The emergency checklist was then completed and the flight proceeded to an uneventful partial flap landing. ATC made no further comment concerning the altitude deviation. No emergency was declared with ATC. However; it was discovered after landing that the Tower had declared some type of emergency for us. A local sheriff's deputy greeted us at the FBO and requested a statement. Statements were provided by both crew members and the deputy informed us this was nothing more than a paperwork drill. Since the Tower had declared some type of emergency event which activated crash/fire/rescue personnel; an administrative report was required. In the confusion of the moment; ensuring the auto pilot was capturing the assigned altitude would have eliminated this deviation.

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.