Narrative:

As a result of the mechanical, we were dispatched with a single pack operative and were limited to FL310 or lower. We were previously filed to FL350. On departure, we were distraction by thunderstorms in the area and accepted a clearance to FL350 and climbed to FL350. After about 20 mins at that altitude and when we were clear of the thunderstorms, then we realized we had climbed to FL350 when we had intended to go no higher than FL310 due to the system problem. We immediately requested and descended to FL310. The flight continued to mco with no further problems. I believe the exceedance was due to a combination of crew fatigue and the WX. I remember when we were cleared to FL350 thinking that would aid in our deviations around WX. I forgot about the existing aircraft system problem due to being tired as well as concerned about WX avoidance. In the future, I will plan on updating my clearance or have dispatch update it with ATC prior to departure. Supplemental information from acn 586887: maintenance called to defer the #1 pack inoperative at departure time. I had stepped away from my desk for a moment and another dispatcher answered the call for me. When I returned to my desk, the other dispatcher asked if I was agreeable to defer the pack inoperative and I said I was. He said he would send the release for me as he already had it set up on his computer. I checked and saw that the new release had been sent at FL310, but I failed to confirm if he had refiled the flight plan with ATC (he had not).

Related reports:

Google
 

Original NASA ASRS Text

Title: FLT CREW OF A320 CLBED TO FL350 DURING TSTM DEV CONTRARY TO DISPATCH MEL LIMITATION TO FL310 DUE TO AN INOP PACK.

Narrative: AS A RESULT OF THE MECHANICAL, WE WERE DISPATCHED WITH A SINGLE PACK OPERATIVE AND WERE LIMITED TO FL310 OR LOWER. WE WERE PREVIOUSLY FILED TO FL350. ON DEP, WE WERE DISTR BY TSTMS IN THE AREA AND ACCEPTED A CLRNC TO FL350 AND CLBED TO FL350. AFTER ABOUT 20 MINS AT THAT ALT AND WHEN WE WERE CLR OF THE TSTMS, THEN WE REALIZED WE HAD CLBED TO FL350 WHEN WE HAD INTENDED TO GO NO HIGHER THAN FL310 DUE TO THE SYS PROB. WE IMMEDIATELY REQUESTED AND DSNDED TO FL310. THE FLT CONTINUED TO MCO WITH NO FURTHER PROBS. I BELIEVE THE EXCEEDANCE WAS DUE TO A COMBINATION OF CREW FATIGUE AND THE WX. I REMEMBER WHEN WE WERE CLRED TO FL350 THINKING THAT WOULD AID IN OUR DEVS AROUND WX. I FORGOT ABOUT THE EXISTING ACFT SYS PROB DUE TO BEING TIRED AS WELL AS CONCERNED ABOUT WX AVOIDANCE. IN THE FUTURE, I WILL PLAN ON UPDATING MY CLRNC OR HAVE DISPATCH UPDATE IT WITH ATC PRIOR TO DEP. SUPPLEMENTAL INFO FROM ACN 586887: MAINT CALLED TO DEFER THE #1 PACK INOP AT DEP TIME. I HAD STEPPED AWAY FROM MY DESK FOR A MOMENT AND ANOTHER DISPATCHER ANSWERED THE CALL FOR ME. WHEN I RETURNED TO MY DESK, THE OTHER DISPATCHER ASKED IF I WAS AGREEABLE TO DEFER THE PACK INOP AND I SAID I WAS. HE SAID HE WOULD SEND THE RELEASE FOR ME AS HE ALREADY HAD IT SET UP ON HIS COMPUTER. I CHKED AND SAW THAT THE NEW RELEASE HAD BEEN SENT AT FL310, BUT I FAILED TO CONFIRM IF HE HAD REFILED THE FLT PLAN WITH ATC (HE HAD NOT).

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.