Narrative:

The purpose of this flight was to perform a required functional test of newly installed egpws, a newly installed magnastar flight phone system and to perform a post maintenance system check of the aircraft that had just came out of a majo inspection. Due to unexpected problems, the maintenance facility did not have the aircraft ready to fly until XA00, 7 hours after our arrival. By the time we departed for the flight we had been on duty for a little over 8 hours. We were handed off to ZMP and eventually cleared to our initial cruise altitude of 14000 ft MSL. The sic contacted minneapolis to brief them of our intentions, that is, after passing iwd we were going to need to descend to 2000 ft MSL over lake superior in order to perform the overfly of cuyahoga peak (TF3) required for our egpws functional test. Controller #1 handed us off to the next sector advising us to wait about 5 mins before making our request. We contacted ZMP on the new frequency and the new controller (controller #2) immediately asked us our intentions. We reiterated our intent to descend to 2000 ft over lake superior with controller #2. Controller #2 informed us that he could not clear us to 2000 ft over the lake on an IFR flight plan. We told him that in that case we would cancel IFR at ironwood and then contact him after completion of the test for an IFR clearance back to atw. He asked who was going to cancel the IFR, him or us, and we said we would. We believe he responded 'roger.' as we approached iwd, we requested a lower altitude in order to begin our way down to be at our planned 2000 ft altitude in time for our pass over cuyahoga peak. Controller #2 was very busy, it seemed, and he broadcast that he was getting several calls with the same request and was going to have to take them one at a time. We are not sure what his exact response was at that time to our request for a lower altitude. There were several aircraft calling and it is possible he was blocked or stepped on. En route to iwd we set up our FMS for a VNAV descent to reach our first egpws test waypoint at 2000 ft. We set the asel to 2000 ft as we were expecting a quick clearance and we were rapidly approaching our FMS calculated top of descent point. Realizing that we were going to make a hurried descent and that the controller was over tasked, we called again and told him we were canceling IFR. We wanted to expedite our descent and relieve the controller by going VFR. The controller responded saying again that several aircraft were requesting cancellations at the same time and the sic thought he said that he was unable to release us (or perhaps another aircraft he was talking to) at the time, the PIC thought he said, IFR canceled. Throughout the flight our maintenance crew members would periodically engage us in conversation about various aspects of the functional checks they were performing. Coincident with the current communication problem we were having with ATC, one of the technicians, unaware of the situation, asked us a question. Simultaneously, the VNAV engaged and began our descent for 2000 ft MSL. The PF, distraction by the maintenance crew, was not aware that we were not cleared yet to descend, he thought he heard the controller say 'IFR canceled.' meanwhile, the sic, along with being distraction momentarily by the maintenance crew's questions, was also busy trying to get a confirmation from the controller that we had canceled IFR. When the sic realized that the aircraft was descending, he advised the PIC that we had better get back up to 14000 ft. The PIC immediately realized our error and began returning to our clearance altitude of 14000 ft. Because we had passenger moving about the cabin, it was necessary to make a smooth leveloff and transition rather than an abrupt pitch up maneuver to return to the assigned altitude without upsetting the passenger and causing them possible injury. As we began our climb to 14000 ft, we got a TCASII TA showing a target 3 mi at our 7-8 O'clock position indicating 300 ft below our altitude. At the same time the controller asked for our altitude and the sic responded that we were at 13500 ft and returning to 14000 ft. We were back at 14000 ft in about 15 seconds. The controller asked what we were doing down there and, as we were trying to figure that our ourselves, the sic told him that we had an equipment malfunction (because at first that is what the sic thought it was) that we didn't catch in time, and that we were sorry. It was in hindsight, an automation surprise perhaps caused by prematurely setting the asel to 2000 ft. The controller said there was probably going to be some paperwork involved because there was other IFR traffic in the area and to stand by for a phone number.

Google
 

Original NASA ASRS Text

Title: F900 CREW ON TEST FLT AND ON IFR FLT PLAN WITH ZMP LEAVE ASSIGNED ALT WITHOUT ATC APPROVAL.

Narrative: THE PURPOSE OF THIS FLT WAS TO PERFORM A REQUIRED FUNCTIONAL TEST OF NEWLY INSTALLED EGPWS, A NEWLY INSTALLED MAGNASTAR FLT PHONE SYS AND TO PERFORM A POST MAINT SYS CHK OF THE ACFT THAT HAD JUST CAME OUT OF A MAJO INSPECTION. DUE TO UNEXPECTED PROBS, THE MAINT FACILITY DID NOT HAVE THE ACFT READY TO FLY UNTIL XA00, 7 HRS AFTER OUR ARR. BY THE TIME WE DEPARTED FOR THE FLT WE HAD BEEN ON DUTY FOR A LITTLE OVER 8 HRS. WE WERE HANDED OFF TO ZMP AND EVENTUALLY CLRED TO OUR INITIAL CRUISE ALT OF 14000 FT MSL. THE SIC CONTACTED MINNEAPOLIS TO BRIEF THEM OF OUR INTENTIONS, THAT IS, AFTER PASSING IWD WE WERE GOING TO NEED TO DSND TO 2000 FT MSL OVER LAKE SUPERIOR IN ORDER TO PERFORM THE OVERFLY OF CUYAHOGA PEAK (TF3) REQUIRED FOR OUR EGPWS FUNCTIONAL TEST. CTLR #1 HANDED US OFF TO THE NEXT SECTOR ADVISING US TO WAIT ABOUT 5 MINS BEFORE MAKING OUR REQUEST. WE CONTACTED ZMP ON THE NEW FREQ AND THE NEW CTLR (CTLR #2) IMMEDIATELY ASKED US OUR INTENTIONS. WE REITERATED OUR INTENT TO DSND TO 2000 FT OVER LAKE SUPERIOR WITH CTLR #2. CTLR #2 INFORMED US THAT HE COULD NOT CLR US TO 2000 FT OVER THE LAKE ON AN IFR FLT PLAN. WE TOLD HIM THAT IN THAT CASE WE WOULD CANCEL IFR AT IRONWOOD AND THEN CONTACT HIM AFTER COMPLETION OF THE TEST FOR AN IFR CLRNC BACK TO ATW. HE ASKED WHO WAS GOING TO CANCEL THE IFR, HIM OR US, AND WE SAID WE WOULD. WE BELIEVE HE RESPONDED 'ROGER.' AS WE APCHED IWD, WE REQUESTED A LOWER ALT IN ORDER TO BEGIN OUR WAY DOWN TO BE AT OUR PLANNED 2000 FT ALT IN TIME FOR OUR PASS OVER CUYAHOGA PEAK. CTLR #2 WAS VERY BUSY, IT SEEMED, AND HE BROADCAST THAT HE WAS GETTING SEVERAL CALLS WITH THE SAME REQUEST AND WAS GOING TO HAVE TO TAKE THEM ONE AT A TIME. WE ARE NOT SURE WHAT HIS EXACT RESPONSE WAS AT THAT TIME TO OUR REQUEST FOR A LOWER ALT. THERE WERE SEVERAL ACFT CALLING AND IT IS POSSIBLE HE WAS BLOCKED OR STEPPED ON. ENRTE TO IWD WE SET UP OUR FMS FOR A VNAV DSCNT TO REACH OUR FIRST EGPWS TEST WAYPOINT AT 2000 FT. WE SET THE ASEL TO 2000 FT AS WE WERE EXPECTING A QUICK CLRNC AND WE WERE RAPIDLY APCHING OUR FMS CALCULATED TOP OF DSCNT POINT. REALIZING THAT WE WERE GOING TO MAKE A HURRIED DSCNT AND THAT THE CTLR WAS OVER TASKED, WE CALLED AGAIN AND TOLD HIM WE WERE CANCELING IFR. WE WANTED TO EXPEDITE OUR DSCNT AND RELIEVE THE CTLR BY GOING VFR. THE CTLR RESPONDED SAYING AGAIN THAT SEVERAL ACFT WERE REQUESTING CANCELLATIONS AT THE SAME TIME AND THE SIC THOUGHT HE SAID THAT HE WAS UNABLE TO RELEASE US (OR PERHAPS ANOTHER ACFT HE WAS TALKING TO) AT THE TIME, THE PIC THOUGHT HE SAID, IFR CANCELED. THROUGHOUT THE FLT OUR MAINT CREW MEMBERS WOULD PERIODICALLY ENGAGE US IN CONVERSATION ABOUT VARIOUS ASPECTS OF THE FUNCTIONAL CHKS THEY WERE PERFORMING. COINCIDENT WITH THE CURRENT COM PROB WE WERE HAVING WITH ATC, ONE OF THE TECHNICIANS, UNAWARE OF THE SIT, ASKED US A QUESTION. SIMULTANEOUSLY, THE VNAV ENGAGED AND BEGAN OUR DSCNT FOR 2000 FT MSL. THE PF, DISTR BY THE MAINT CREW, WAS NOT AWARE THAT WE WERE NOT CLRED YET TO DSND, HE THOUGHT HE HEARD THE CTLR SAY 'IFR CANCELED.' MEANWHILE, THE SIC, ALONG WITH BEING DISTR MOMENTARILY BY THE MAINT CREW'S QUESTIONS, WAS ALSO BUSY TRYING TO GET A CONFIRMATION FROM THE CTLR THAT WE HAD CANCELED IFR. WHEN THE SIC REALIZED THAT THE ACFT WAS DSNDING, HE ADVISED THE PIC THAT WE HAD BETTER GET BACK UP TO 14000 FT. THE PIC IMMEDIATELY REALIZED OUR ERROR AND BEGAN RETURNING TO OUR CLRNC ALT OF 14000 FT. BECAUSE WE HAD PAX MOVING ABOUT THE CABIN, IT WAS NECESSARY TO MAKE A SMOOTH LEVELOFF AND TRANSITION RATHER THAN AN ABRUPT PITCH UP MANEUVER TO RETURN TO THE ASSIGNED ALT WITHOUT UPSETTING THE PAX AND CAUSING THEM POSSIBLE INJURY. AS WE BEGAN OUR CLB TO 14000 FT, WE GOT A TCASII TA SHOWING A TARGET 3 MI AT OUR 7-8 O'CLOCK POS INDICATING 300 FT BELOW OUR ALT. AT THE SAME TIME THE CTLR ASKED FOR OUR ALT AND THE SIC RESPONDED THAT WE WERE AT 13500 FT AND RETURNING TO 14000 FT. WE WERE BACK AT 14000 FT IN ABOUT 15 SECONDS. THE CTLR ASKED WHAT WE WERE DOING DOWN THERE AND, AS WE WERE TRYING TO FIGURE THAT OUR OURSELVES, THE SIC TOLD HIM THAT WE HAD AN EQUIP MALFUNCTION (BECAUSE AT FIRST THAT IS WHAT THE SIC THOUGHT IT WAS) THAT WE DIDN'T CATCH IN TIME, AND THAT WE WERE SORRY. IT WAS IN HINDSIGHT, AN AUTOMATION SURPRISE PERHAPS CAUSED BY PREMATURELY SETTING THE ASEL TO 2000 FT. THE CTLR SAID THERE WAS PROBABLY GOING TO BE SOME PAPERWORK INVOLVED BECAUSE THERE WAS OTHER IFR TFC IN THE AREA AND TO STAND BY FOR A PHONE NUMBER.

Data retrieved from NASA's ASRS site as of July 2007 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.