A B727 CREW PUSHED BACK WITHOUT A CLRNC ONTO AN ACTIVE TXWY AT ORF.
Synopsis
A B727 CREW PUSHED BACK WITHOUT A CLRNC ONTO AN ACTIVE TXWY AT ORF.
Narrative
I HAD FLOWN MEM-ORF-MEM; FLT XXX TAIL SWAP AT ORF; FLT YYYY RETURN -- AN AM OUT AND BACK -- ALL MONTH. ALSO THE COMPANY X COLOR PAGE FOR ORF; MY FO HAD CALLED GND FOR PUSHBACK CLRNC. GND'S RESPONSE HAD BEEN ANYTHING FROM 'CLRED TO PUSHBACK;' TO 'CALL WHEN READY TO TAXI' TO 'THAT IS A NON-MOVEMENT AREA; PUSH AT YOUR OWN DISCRETION.' SATURDAY WAS THE LAST TRIP OF OUR SCHEDULED MONTH. WE WERE 1 HR 55 MINS LATE IN GETTING AIRBORNE FROM MEM DUE TO WX. I FLEW WITH A DIFFERENT FO AND AT PUSHBACK TOLD HIM WE DIDN'T HAVE TO CALL FOR CLRNC (IN ACCORDANCE WITH GND'S PREVIOUS STATEMENT). NOTHING WAS SAID BY ATC UNTIL MY FO CALLED FOR TAXI. WE WERE THEN ADVISED WE HAD PUSHED BACK ONTO ACTIVE TXWY X. I THEN TALKED ON THE RADIO TELLING GND WHAT HAD HAPPENED WHEN WE HAD LAST CALLED FOR PUSHBACK CLRNC. AFTER A SHORT DISCUSSION; GND ADVISED I SHOULD HAVE KNOWN X WAS AN ACTIVE TXWY AND SHOULD NOT HAVE PUSHED ONTO IT WITHOUT CLRNC. BOTH TRUE STATEMENTS. WHILE GND WAS CORRECT; I FEEL SOMEWHAT SET UP. THE X COLOR PAGE DISCUSSES PUSHBACK ONTO TXWY X; WELL; JUST WHERE ELSE WOULD WE/COULD BE PUSHED? THE GND CTLR A TIME OR TWO BEFORE HAD NO PROB WITH US PUSHING WITHOUT CLRNC. BUT THIS ONE DID. IN AN EFFORT TO PREVENT THIS FROM REOCCURRING; I FORESEE CALLING EACH AND EVERY GND FOR PUSHBACK CLRNC; REGARDLESS OF NON-MOVEMENT AREA STATUS AND/OR WHAT THE CTLR SAID THE DAY BEFORE. AN EXTRA (READ WASTED) RADIO CALL BEATS FILLING OUT PAPERWORK! MY FO WAS TRYING TO DO THE CORRECT PROC (BY CALLING) BUT; IN AN ATTEMPT TO STREAMLINE OPS; I TOLD HIM IT WASN'T REQUIRED. I GUESS JUDGEMENT IS THE FIRST THING TO GO WHEN YOU'RE TIRED.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.