Narrative:

Aircraft X checked on my frequency, saying, '11000 for 7'. ZSE should have assigned him 10000 ft. I was working with a GA aircraft Y that had filed an IFR flight from an airport in our airspace. He filed his flight plan using latitude/longitudes for the departure airport. This caused the ARTS to not accept the aircraft as a departure. I was trying to force the data block to the ARTS computer (so I would have a data tag) when aircraft X checked on. I verified his altitude and the correct ATIS information but failed to hear 'descending to 70.' why should he be? The center is supposed to assign 10000 ft. I first noticed the problem when I saw the altitude readout go from 100 to 097. At that point I asked the aircraft what altitude the center had assigned him. He replied, 'seven thousand.' I immediately told aircraft to maintain 10000 ft. When I saw his descent rate (it was fast) I then told the aircraft to expedite his climb to 10000 ft. He climbed back up to 10000 ft and the remainder of his flight was routine. Aircraft X lowest altitude I saw on the helns arrival was 90, 28 mi north of btg. Should be 10000 ft until 22 mi north btg, then 7000 ft is ok. Supplemental information from acn 563145: the possible altitude deviation in question occurred on oct/sun/02, on a flight from seattle-tacoma to portland international airport. I was the PF when the PNF responded to ZSE instructions to descend at pilot's discretion from 11000 ft to cross kratr intersection at 7000 ft on the hlns four arrival. The PNF dialed 7000 ft in the altitude alerter and verified with me if that was correct. I concurred. I postponed my descent until I was closer to kratr intersection. We were handed off shortly after the previously mentioned ATC transmission (currently a few mi outside hlns intersection). The PNF contacted portland approach control and advised them that we had begun our descent from 11000 ft to 7000 ft. Then, the PNF went off frequency to call company operations on communication #2, in which case, I would monitor ATC on communication #1. Once I had descended through 9700 ft at a rate of 1800 FPM, approach control queried what altitude did ZSE had given us. I replied 7000 ft. He, in return, instructed me to climb and maintain 10000 ft. By that time I stopped my descent and initiated my climb to 10000 ft, I noticed the altitude of 8900 ft. The remainder of our flight went uneventfully. However, I believe with the PNF that we were instructed to 7000 ft. If we were wrong with that altitude, it would've been corrected once we had checked in with portland approach. Nonetheless, I will be more assertive in initiating my climb rate should a similar incident occur in the future. Supplemental information from acn 562993: approaching helns on helns 4 arrival, ZSE directed us to cross kratr at 7000 ft. At least that is what we thought we heard. As PNF, I responded to their instruction and set 7000 ft in our altitude alerter/pre-selector. I paused at that time because we usually receive instructions to cross kratr at 10000 ft. I queried the first officer (PNF) 'was that 7 or 10000?' he responded 'seven' without hesitation. About that time center switched us to pdx approach. I checked in '...11000 ft descending to 7000 ft with (ATIS).' approach acknowledged without comment. I then turned the ATC radio over to the first officer so I could talk to company on the other communication in order to report in-range. While I was talking to company, I heard ATC ask what ZSE center assigned us. We were descending through about 9500 ft at 1800 FPM at this time. The first officer responded '7000 ft.' ATC then told us to climb back to 10000 ft. The first officer did this. The lowest altitude I observed was 8900 ft. If indeed we were assigned 10000 ft by center (not proven at this point but to be investigated) it was my fault for not querying ATC about what I knew to be an unusual instruction. Failure of pdx approach to catch the error when I checked on was a contributor.

Google
 

Original NASA ASRS Text

Title: ZSE RADAR CTLR FAILS TO HEAR DH8 CREW READBACK RESULTING IN AN OPERROR.

Narrative: ACFT X CHKED ON MY FREQ, SAYING, '11000 FOR 7'. ZSE SHOULD HAVE ASSIGNED HIM 10000 FT. I WAS WORKING WITH A GA ACFT Y THAT HAD FILED AN IFR FLT FROM AN ARPT IN OUR AIRSPACE. HE FILED HIS FLT PLAN USING LAT/LONGITUDES FOR THE DEP ARPT. THIS CAUSED THE ARTS TO NOT ACCEPT THE ACFT AS A DEP. I WAS TRYING TO FORCE THE DATA BLOCK TO THE ARTS COMPUTER (SO I WOULD HAVE A DATA TAG) WHEN ACFT X CHKED ON. I VERIFIED HIS ALT AND THE CORRECT ATIS INFO BUT FAILED TO HEAR 'DSNDING TO 70.' WHY SHOULD HE BE? THE CTR IS SUPPOSED TO ASSIGN 10000 FT. I FIRST NOTICED THE PROB WHEN I SAW THE ALT READOUT GO FROM 100 TO 097. AT THAT POINT I ASKED THE ACFT WHAT ALT THE CTR HAD ASSIGNED HIM. HE REPLIED, 'SEVEN THOUSAND.' I IMMEDIATELY TOLD ACFT TO MAINTAIN 10000 FT. WHEN I SAW HIS DSCNT RATE (IT WAS FAST) I THEN TOLD THE ACFT TO EXPEDITE HIS CLB TO 10000 FT. HE CLBED BACK UP TO 10000 FT AND THE REMAINDER OF HIS FLT WAS ROUTINE. ACFT X LOWEST ALT I SAW ON THE HELNS ARR WAS 90, 28 MI N OF BTG. SHOULD BE 10000 FT UNTIL 22 MI N BTG, THEN 7000 FT IS OK. SUPPLEMENTAL INFO FROM ACN 563145: THE POSSIBLE ALTDEV IN QUESTION OCCURRED ON OCT/SUN/02, ON A FLT FROM SEATTLE-TACOMA TO PORTLAND INTL ARPT. I WAS THE PF WHEN THE PNF RESPONDED TO ZSE INSTRUCTIONS TO DSND AT PLT'S DISCRETION FROM 11000 FT TO CROSS KRATR INTXN AT 7000 FT ON THE HLNS FOUR ARR. THE PNF DIALED 7000 FT IN THE ALT ALERTER AND VERIFIED WITH ME IF THAT WAS CORRECT. I CONCURRED. I POSTPONED MY DSCNT UNTIL I WAS CLOSER TO KRATR INTXN. WE WERE HANDED OFF SHORTLY AFTER THE PREVIOUSLY MENTIONED ATC XMISSION (CURRENTLY A FEW MI OUTSIDE HLNS INTXN). THE PNF CONTACTED PORTLAND APCH CTL AND ADVISED THEM THAT WE HAD BEGUN OUR DSCNT FROM 11000 FT TO 7000 FT. THEN, THE PNF WENT OFF FREQ TO CALL COMPANY OPS ON COM #2, IN WHICH CASE, I WOULD MONITOR ATC ON COM #1. ONCE I HAD DSNDED THROUGH 9700 FT AT A RATE OF 1800 FPM, APCH CTL QUERIED WHAT ALT DID ZSE HAD GIVEN US. I REPLIED 7000 FT. HE, IN RETURN, INSTRUCTED ME TO CLB AND MAINTAIN 10000 FT. BY THAT TIME I STOPPED MY DSCNT AND INITIATED MY CLB TO 10000 FT, I NOTICED THE ALT OF 8900 FT. THE REMAINDER OF OUR FLT WENT UNEVENTFULLY. HOWEVER, I BELIEVE WITH THE PNF THAT WE WERE INSTRUCTED TO 7000 FT. IF WE WERE WRONG WITH THAT ALT, IT WOULD'VE BEEN CORRECTED ONCE WE HAD CHKED IN WITH PORTLAND APCH. NONETHELESS, I WILL BE MORE ASSERTIVE IN INITIATING MY CLB RATE SHOULD A SIMILAR INCIDENT OCCUR IN THE FUTURE. SUPPLEMENTAL INFO FROM ACN 562993: APCHING HELNS ON HELNS 4 ARR, ZSE DIRECTED US TO CROSS KRATR AT 7000 FT. AT LEAST THAT IS WHAT WE THOUGHT WE HEARD. AS PNF, I RESPONDED TO THEIR INSTRUCTION AND SET 7000 FT IN OUR ALT ALERTER/PRE-SELECTOR. I PAUSED AT THAT TIME BECAUSE WE USUALLY RECEIVE INSTRUCTIONS TO CROSS KRATR AT 10000 FT. I QUERIED THE FO (PNF) 'WAS THAT 7 OR 10000?' HE RESPONDED 'SEVEN' WITHOUT HESITATION. ABOUT THAT TIME CTR SWITCHED US TO PDX APCH. I CHKED IN '...11000 FT DSNDING TO 7000 FT WITH (ATIS).' APCH ACKNOWLEDGED WITHOUT COMMENT. I THEN TURNED THE ATC RADIO OVER TO THE FO SO I COULD TALK TO COMPANY ON THE OTHER COM IN ORDER TO RPT IN-RANGE. WHILE I WAS TALKING TO COMPANY, I HEARD ATC ASK WHAT ZSE CTR ASSIGNED US. WE WERE DSNDING THROUGH ABOUT 9500 FT AT 1800 FPM AT THIS TIME. THE FO RESPONDED '7000 FT.' ATC THEN TOLD US TO CLB BACK TO 10000 FT. THE FO DID THIS. THE LOWEST ALT I OBSERVED WAS 8900 FT. IF INDEED WE WERE ASSIGNED 10000 FT BY CTR (NOT PROVEN AT THIS POINT BUT TO BE INVESTIGATED) IT WAS MY FAULT FOR NOT QUERYING ATC ABOUT WHAT I KNEW TO BE AN UNUSUAL INSTRUCTION. FAILURE OF PDX APCH TO CATCH THE ERROR WHEN I CHKED ON WAS A CONTRIBUTOR.

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.