Narrative:

As we (aircraft X) pushed back from our ramp at rno, we heard another aircraft (aircraft Y) advise ground control that an aircraft was blocking his movement on the taxiway. After realizing our aircraft might be the one who was in his way, we checked our charts to find out that an ATC clearance was required prior to pushback from our gate. We apologized to the controller for our oversight to call him and received a taxi clearance to runway 16R. The remainder of the flight was uneventful. What I believe contributed to this error of not contacting ATC for clearance, was the fact that we were in a hurry and not following SOP. This caused us to miss reviewing some pertinent information on the charts. Also, before we pushed back, we had just briefed the highly complex departure procedure out of this airport. All of these factors put together created an environment of not following our set habit patterns in ensuring we were properly backing each other up. To prevent a recurrence of this error, I believe crews should allow themselves the extra time to brief highly complex procedures and to always follow SOP's. This will ensure that crews establish set habit patterns to prevent errors of omission and are not rushed so they can back each other up. Supplemental information from acn 425593: at the completion of the pushback from the gate at rno, we were in position to taxi north on taxiway a for departure on runway 16R. All was normal except that we forgot to get ground control clearance to push back onto an active taxiway.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR B727 FLC PUSH BACK FROM PARKING WITHOUT TWR GND CTLR CLRNC AND BLOCK ANOTHER TAXIING ACFT.

Narrative: AS WE (ACFT X) PUSHED BACK FROM OUR RAMP AT RNO, WE HEARD ANOTHER ACFT (ACFT Y) ADVISE GND CTL THAT AN ACFT WAS BLOCKING HIS MOVEMENT ON THE TXWY. AFTER REALIZING OUR ACFT MIGHT BE THE ONE WHO WAS IN HIS WAY, WE CHKED OUR CHARTS TO FIND OUT THAT AN ATC CLRNC WAS REQUIRED PRIOR TO PUSHBACK FROM OUR GATE. WE APOLOGIZED TO THE CTLR FOR OUR OVERSIGHT TO CALL HIM AND RECEIVED A TAXI CLRNC TO RWY 16R. THE REMAINDER OF THE FLT WAS UNEVENTFUL. WHAT I BELIEVE CONTRIBUTED TO THIS ERROR OF NOT CONTACTING ATC FOR CLRNC, WAS THE FACT THAT WE WERE IN A HURRY AND NOT FOLLOWING SOP. THIS CAUSED US TO MISS REVIEWING SOME PERTINENT INFO ON THE CHARTS. ALSO, BEFORE WE PUSHED BACK, WE HAD JUST BRIEFED THE HIGHLY COMPLEX DEP PROC OUT OF THIS ARPT. ALL OF THESE FACTORS PUT TOGETHER CREATED AN ENVIRONMENT OF NOT FOLLOWING OUR SET HABIT PATTERNS IN ENSURING WE WERE PROPERLY BACKING EACH OTHER UP. TO PREVENT A RECURRENCE OF THIS ERROR, I BELIEVE CREWS SHOULD ALLOW THEMSELVES THE EXTRA TIME TO BRIEF HIGHLY COMPLEX PROCS AND TO ALWAYS FOLLOW SOP'S. THIS WILL ENSURE THAT CREWS ESTABLISH SET HABIT PATTERNS TO PREVENT ERRORS OF OMISSION AND ARE NOT RUSHED SO THEY CAN BACK EACH OTHER UP. SUPPLEMENTAL INFO FROM ACN 425593: AT THE COMPLETION OF THE PUSHBACK FROM THE GATE AT RNO, WE WERE IN POS TO TAXI N ON TXWY A FOR DEP ON RWY 16R. ALL WAS NORMAL EXCEPT THAT WE FORGOT TO GET GND CTL CLRNC TO PUSH BACK ONTO AN ACTIVE TXWY.

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.