Narrative:

At approximately XA45Z our flight was cleared direct to mgw and cleared to FL330. The first officer acknowledged FL330 and direct mgw. She then reset FL330 in the altitude alerter and I announced FL330. This was on frequency 127.62 (ZAU). As we proceeded RNAV direct mgw our frequency was changed to ZAU 126.32. During climb through FL300, the controller asked what altitude we were climbing to. The first officer replied FL330. This controller stated we were only cleared to FL290. All 3 crew members verified hearing clearance to FL330 on the previous frequency. The first officer transmitted she read back the clearance to FL330. The controller replied the computer had only cleared us to FL290 -- there was crossing (?) traffic at FL330, maintain FL310. We continued to climb to and maintain FL310. The controller later asked if we still requested FL330, and we replied in the affirmative. He later stated that traffic was no longer a factor, climb to and maintain FL330. The question about altitude we were climbing to from the second controller occurred at approximately XX51Z (or some 6 mins after we had acknowledged clearance to FL330 on the previous sector). I believe this emphasizes clearance readback, particularly at every chance (particularly changing frequencys). It is also very important for all crew members to monitor clrncs, especially in the 'wee' hours. I don't think all 3 crew members would have heard FL330 or expected a straight climb to requested altitude, if it had not been received. Although no conflict actually occurred, a busy sector or less alert controller could have resulted in an intrusion into another aircraft's protected airspace.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR B727 FLC CLBED ABOVE THEIR ASSIGNED ALT WHEN THEY RECEIVED AND READ BACK A CLRNC TO 33000 FT VERSUS THE NEXT SECTOR'S UNDERSTANDING THAT THE ASSIGNMENT WAS 29000 FT.

Narrative: AT APPROX XA45Z OUR FLT WAS CLRED DIRECT TO MGW AND CLRED TO FL330. THE FO ACKNOWLEDGED FL330 AND DIRECT MGW. SHE THEN RESET FL330 IN THE ALT ALERTER AND I ANNOUNCED FL330. THIS WAS ON FREQ 127.62 (ZAU). AS WE PROCEEDED RNAV DIRECT MGW OUR FREQ WAS CHANGED TO ZAU 126.32. DURING CLB THROUGH FL300, THE CTLR ASKED WHAT ALT WE WERE CLBING TO. THE FO REPLIED FL330. THIS CTLR STATED WE WERE ONLY CLRED TO FL290. ALL 3 CREW MEMBERS VERIFIED HEARING CLRNC TO FL330 ON THE PREVIOUS FREQ. THE FO XMITTED SHE READ BACK THE CLRNC TO FL330. THE CTLR REPLIED THE COMPUTER HAD ONLY CLRED US TO FL290 -- THERE WAS XING (?) TFC AT FL330, MAINTAIN FL310. WE CONTINUED TO CLB TO AND MAINTAIN FL310. THE CTLR LATER ASKED IF WE STILL REQUESTED FL330, AND WE REPLIED IN THE AFFIRMATIVE. HE LATER STATED THAT TFC WAS NO LONGER A FACTOR, CLB TO AND MAINTAIN FL330. THE QUESTION ABOUT ALT WE WERE CLBING TO FROM THE SECOND CTLR OCCURRED AT APPROX XX51Z (OR SOME 6 MINS AFTER WE HAD ACKNOWLEDGED CLRNC TO FL330 ON THE PREVIOUS SECTOR). I BELIEVE THIS EMPHASIZES CLRNC READBACK, PARTICULARLY AT EVERY CHANCE (PARTICULARLY CHANGING FREQS). IT IS ALSO VERY IMPORTANT FOR ALL CREW MEMBERS TO MONITOR CLRNCS, ESPECIALLY IN THE 'WEE' HRS. I DON'T THINK ALL 3 CREW MEMBERS WOULD HAVE HEARD FL330 OR EXPECTED A STRAIGHT CLB TO REQUESTED ALT, IF IT HAD NOT BEEN RECEIVED. ALTHOUGH NO CONFLICT ACTUALLY OCCURRED, A BUSY SECTOR OR LESS ALERT CTLR COULD HAVE RESULTED IN AN INTRUSION INTO ANOTHER ACFT'S PROTECTED AIRSPACE.

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.