Narrative:

Took off without new maintenance release and release 2 ECAM for forward 2 fault after engine start salute and release at XA28. We stayed abeam gate and sent ACARS to ask maintenance to call us several times. We finally received ACARS from maintenance after 10-15 minutes that they were working it. Close to 20 minutes later; they said we could defer and it would be worked in ZZZ if ok with us. This was followed by ACARS message with pilot actions and a deferral sticker number. I thought this was the release; captain sent back ACARS message to maintenance. While parked there; we did 2 engine run-ups for ice. We taxied soon after and were given runway change for runway 32L; taxiway 10. They had just switched from landing runway 14R. Taxiways were very slippery and several aircraft taxiing about. We got new runway data turning left on taxiway T. I saw message from dispatch about sending a release 2; and then printed runway 32L data. We were switched to tower frequency; input takeoff data; ran before takeoff checklist and forgot about release 2. I did not see that we had another ACARS message; we were cleared for immediate takeoff; did static run-up; and took off. During climb; captain noticed an ACARS message and called it up. Maintenance had changed their mind and asked us to return to gate. The message time was 1 minute after the runway data message. We need to make sure that we have coverage during shift changes for push crews and maintenance. I need to make sure to monitor ACARS message on ECAM screen. Wish it would show up a different color or a bell. Need to make sure that we recheck and release numbers after anything changes.

Related reports:

Google
 

Original NASA ASRS Text

Title: An A320 flight crew reported taking off without a current maintenance release. They cited distraction and time pressure as contributing causes.

Narrative: Took off without new Maintenance Release and Release 2 ECAM for Forward 2 fault after engine start salute and release at XA28. We stayed abeam gate and sent ACARS to ask maintenance to call us several times. We finally received ACARS from maintenance after 10-15 minutes that they were working it. Close to 20 minutes later; they said we could defer and it would be worked in ZZZ if OK with us. This was followed by ACARS message with pilot actions and a deferral sticker number. I thought this was the release; Captain sent back ACARS message to maintenance. While parked there; we did 2 engine run-ups for ice. We taxied soon after and were given runway change for Runway 32L; Taxiway 10. They had just switched from landing Runway 14R. Taxiways were very slippery and several aircraft taxiing about. We got new runway data turning left on Taxiway T. I saw message from Dispatch about sending a Release 2; and then printed Runway 32L data. We were switched to Tower frequency; input takeoff data; ran before takeoff checklist and forgot about Release 2. I did not see that we had another ACARS message; we were cleared for immediate takeoff; did static run-up; and took off. During climb; Captain noticed an ACARS message and called it up. Maintenance had changed their mind and asked us to return to gate. The message time was 1 minute after the runway data message. We need to make sure that we have coverage during shift changes for push crews and Maintenance. I need to make sure to monitor ACARS message on ECAM screen. Wish it would show up a different color or a bell. Need to make sure that we recheck and release numbers after anything changes.

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