Narrative:

Our scheduled departure time was XA40 local. After discovering a mechanical discrepancy and having the problem attended to, we left the gate at XB32 local. Since our release was good for 1 hour after scheduled departure, we did not obtain an amended release from flight control to update our release time. Upon arriving in reno and checking my mailbox, I received flight operations bulletin X. In this bulletin, it stated that, all release times would be listed 10 mins prior to scheduled departure time. Therefore, our release would have been listed as XA30 local, not XA40, and we left the gate at XB32 local, exceeding the release validity by 2 mins.

Google
 

Original NASA ASRS Text

Title: FLC DEPARTS ORD AFTER COMPANY RELEASE TIME EXPIRED.

Narrative: OUR SCHEDULED DEP TIME WAS XA40 LCL. AFTER DISCOVERING A MECHANICAL DISCREPANCY AND HAVING THE PROB ATTENDED TO, WE LEFT THE GATE AT XB32 LCL. SINCE OUR RELEASE WAS GOOD FOR 1 HR AFTER SCHEDULED DEP, WE DID NOT OBTAIN AN AMENDED RELEASE FROM FLT CTL TO UPDATE OUR RELEASE TIME. UPON ARRIVING IN RENO AND CHKING MY MAILBOX, I RECEIVED FLT OPS BULLETIN X. IN THIS BULLETIN, IT STATED THAT, ALL RELEASE TIMES WOULD BE LISTED 10 MINS PRIOR TO SCHEDULED DEP TIME. THEREFORE, OUR RELEASE WOULD HAVE BEEN LISTED AS XA30 LCL, NOT XA40, AND WE LEFT THE GATE AT XB32 LCL, EXCEEDING THE RELEASE VALIDITY BY 2 MINS.

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.