ACR DEP FROM TUS EXPERIENCED GND CONFLICT WHEN GND CTLR FAILED TO ADVISE FLT CREW OF CONFLICTING TFC REQUIRING REPORTER TO INITIATE FIRM STOP.

Date: 2008-08 · Aircraft: B737-300 · Phase: taxi

Anomalies: conflict-ground-conflict|critical

Synopsis

ACR DEP FROM TUS EXPERIENCED GND CONFLICT WHEN GND CTLR FAILED TO ADVISE FLT CREW OF CONFLICTING TFC REQUIRING REPORTER TO INITIATE FIRM STOP.

Narrative

AFTER PUSHING STRAIGHT BACK FROM THE GATE AT TUS; THE FO CALLED FOR TAXI CLRNC. GND INSTRUCTED US; 'TAXI TO RWY 29R;' AFTER CLRING R AND L; I MADE A R TURN ON THE RAMP. I BEGAN TO TAXI AT A SLOW RATE ACROSS THE RAMP TO INTERCEPT TXWY A VIA A10. THE FO CALLED 'CLR R.' SEVERAL SECONDS LATER; PRIOR TO REACHING TXWY A; I SAW A PIPER WARRIOR TAXIING AT AN UNUSUALLY HIGH RATE OF SPD SEBOUND ON TXWY A. I IMMEDIATELY APPLIED BRAKES FIRMLY AND STOPPED THE ACFT. THE FO ASKED THE GND CTLR; 'WERE WE SUPPOSED TO FOLLOW THAT PIPER?' THE GND CTLR'S RESPONSE WAS; 'OH; THAT WAS MY MISTAKE.' I CALLED ON THE INTERPHONE TO CHK ON THE FLT ATTENDANTS. THE FLT ATTENDANTS RESPONDED THAT THEY WERE OK. THE FO CLRED HIS SIDE OF THE ACFT PROPERLY; HOWEVER; THE HIGH RATE OF SPD OF THE PIPER; AND THE LACK OF INSTRUCTION BY THE GND CTLR; BOTH CONTRIBUTED TO THIS INCIDENT. WITH SAFETY AS MY MAIN CONCERN; HAD I NOT APPLIED BRAKES FIRMLY; WE MAY HAVE IMPACTED THE PIPER. ALWAYS BE AWARE THAT EVEN IF OTHERS ARE NOT OPERATING WITH SAFETY AS THE MAIN PRIORITY; THIS DOES NOT RELIEVE US OF OUR RESPONSIBILITY.

More incidents for this aircraft family →

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