FLC OF A B737-800 PUSHBACK BACK WITHOUT CLRNC.

Date: 1999-09 · Aircraft: B737-800 · Phase: taxi

Anomalies: deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-other-unknown|ground-incursion-taxiway

Synopsis

FLC OF A B737-800 PUSHBACK BACK WITHOUT CLRNC.

Narrative

WE PUSHED BACK FROM GATE XA AT SEA INTO A MOVEMENT AREA WITHOUT CLRNC DUE TO A MISINTERP OF OUR ARPT PAGE. I'M NOT THAT FAMILIAR WITH SEA ARPT AND AT DEP TIME WE CHKED OUR ARPT DIAGRAM PAGES FOR SEA AND IT INDICATED THAT AN ADVISORY CALL FOR PUSHBACK WAS ALL THAT WAS REQUIRED TO GND CTL. AT THE TIME; GND CTL WAS QUITE BUSY AND WE COULDN'T GET A WORD IN; SO WE WENT AHEAD AND PUSHED THE ACFT FIGURING THAT WE'D LET GND KNOW AS SOON AS WE COULD! UNFORTUNATELY; THIS PARTICULAR GATE PUSHES BACK INTO A MOVEMENT AREA AND SEA GND WASN'T THRILLED THAT WE DID NOT CALL FOR PUSHBACK. I APOLOGIZED AND THE REST OF OUR TAXI WAS UNEVENTFUL. THIS COULD HAVE BEEN AVOIDED IF OUR ARPT DIAGRAM PAGE INDICATED THAT THERE ARE CERTAIN 'GATES' THAT REQUIRE A CLRNC FOR PUSHBACK. ALL IT STATES IS THAT AN ADVISORY CALL TO GND IS THE PROC. OTHER ARPTS SUCH AS LAX AND CLE INDICATE THAT A PUSHBACK ADVISORY CALL TO GND IS PROC EXCEPT GATES 'SUCH AND SUCH' WHICH REQUIRE A PUSHBACK CLRNC FROM GND CTL. FROM NOW ON; I WILL JUST GO AHEAD AND CALL GND CTL FOR PUSHBACK CLRNC -- PERIOD!

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.