Narrative:

Air carrier X from yyz to phl, with ZOB who had assigned FL270, and were climbing out. Both PF and PNF called out 'FL270.' flight attendant came to flight deck to report on sick passenger (bumpy). Center changed frequency while I was off and first officer checked in. Controller asked assigned altitude. First officer answered 'FL270.' controller then said 'fl 250' was assigned altitude. First officer stopped climb at FL258. Controller asked if we wanted FL270. First officer answered 'yes' and controller issued climb to FL270. No traffic in area. Continued normal operations. Contributing factors: 1) last trip of 4-DAY schedule. 2) late night flight out of unfamiliar city (canada). 3) numerous problems with controllers and crew members on new flight numbers (series). Prevention: 1) current operation procedures should prevent altitude excursions. After PNF reads back assigned altitude to ATC, PF sets altitude in flight control panel and verifies it. PNF re-verifies the displayed (assigned) altitude. 2) numerous multi-numbered flts with similar call signs are a detriment to readback/hearback problems. Supplemental information from acn 598862: captain took radio call from ZOB to climb to FL270. I read back FL270 and asked what altitude we were climbing to. I answered the call and stated FL270. Controller stated that we were assigned FL250, then asked if we wanted to continue on to FL270. I said yes. He said 'climb to FL270,' and continued normal operation. The captain was also talking to the flight attendant about a sick passenger. It was the last leg of a 4-DAY trip at night. As PF, I understood the PNF repeat FL270. I stated FL270 and selected it in the autoplt and was climbing to FL270. If FL250 was what we were actually assigned, somewhere there was a misunderstanding. We should be more alert for ATC instructions, and re-verify them with each pilot.

Google
 

Original NASA ASRS Text

Title: MDT CREW WAS CLBING TO FL270 WHEN THEIR CLRED ALT WAS FL250.

Narrative: ACR X FROM YYZ TO PHL, WITH ZOB WHO HAD ASSIGNED FL270, AND WERE CLBING OUT. BOTH PF AND PNF CALLED OUT 'FL270.' FLT ATTENDANT CAME TO FLT DECK TO RPT ON SICK PAX (BUMPY). CTR CHANGED FREQ WHILE I WAS OFF AND FO CHKED IN. CTLR ASKED ASSIGNED ALT. FO ANSWERED 'FL270.' CTLR THEN SAID 'FL 250' WAS ASSIGNED ALT. FO STOPPED CLB AT FL258. CTLR ASKED IF WE WANTED FL270. FO ANSWERED 'YES' AND CTLR ISSUED CLB TO FL270. NO TFC IN AREA. CONTINUED NORMAL OPS. CONTRIBUTING FACTORS: 1) LAST TRIP OF 4-DAY SCHEDULE. 2) LATE NIGHT FLT OUT OF UNFAMILIAR CITY (CANADA). 3) NUMEROUS PROBS WITH CTLRS AND CREW MEMBERS ON NEW FLT NUMBERS (SERIES). PREVENTION: 1) CURRENT OP PROCS SHOULD PREVENT ALT EXCURSIONS. AFTER PNF READS BACK ASSIGNED ALT TO ATC, PF SETS ALT IN FLT CTL PANEL AND VERIFIES IT. PNF RE-VERIFIES THE DISPLAYED (ASSIGNED) ALT. 2) NUMEROUS MULTI-NUMBERED FLTS WITH SIMILAR CALL SIGNS ARE A DETRIMENT TO READBACK/HEARBACK PROBS. SUPPLEMENTAL INFO FROM ACN 598862: CAPT TOOK RADIO CALL FROM ZOB TO CLB TO FL270. I READ BACK FL270 AND ASKED WHAT ALT WE WERE CLBING TO. I ANSWERED THE CALL AND STATED FL270. CTLR STATED THAT WE WERE ASSIGNED FL250, THEN ASKED IF WE WANTED TO CONTINUE ON TO FL270. I SAID YES. HE SAID 'CLB TO FL270,' AND CONTINUED NORMAL OP. THE CAPT WAS ALSO TALKING TO THE FLT ATTENDANT ABOUT A SICK PAX. IT WAS THE LAST LEG OF A 4-DAY TRIP AT NIGHT. AS PF, I UNDERSTOOD THE PNF REPEAT FL270. I STATED FL270 AND SELECTED IT IN THE AUTOPLT AND WAS CLBING TO FL270. IF FL250 WAS WHAT WE WERE ACTUALLY ASSIGNED, SOMEWHERE THERE WAS A MISUNDERSTANDING. WE SHOULD BE MORE ALERT FOR ATC INSTRUCTIONS, AND RE-VERIFY THEM WITH EACH PLT.

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.