A CL65 FLT CREW COMES IN CONFLICT WITH AN MD80 WHILE UNDER TOW. THEY HAD NO COM WITH TUG DRIVER; AND NO ATC CLRNC.

2004-09 · NASA ASRS report 629705

Date: 2004-09 · Aircraft: Regional Jet CL65; Undifferentiated or Other Model · Phase: ground

Anomalies: conflict-ground-conflict|less-severe|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|ground-incursion-taxiway

Synopsis

A CL65 FLT CREW COMES IN CONFLICT WITH AN MD80 WHILE UNDER TOW. THEY HAD NO COM WITH TUG DRIVER; AND NO ATC CLRNC.

Narrative

ABOUT 40 MINS PRIOR TO DEP; THE GATE AGENT (MTY) APCHED ME TO INFORM OUR CREW THAT THE ACFT HAD TO BE MOVED FROM THE GA RAMP TO GATE X. I ASKED THE GATE AGENT IF WE WERE TO TAXI OURSELVES OR TO BE TOWED. WE WERE ALREADY HOOKED UP. HE SPOKE SOME ENGLISH AND RESPONDED 'TOWED.' I THEN TRIED TO COORD WITH THE TUG DRIVER WHO SPOKE NO ENGLISH. I THOUGHT 1 OF 2 THINGS WAS HAPPENING REGARDING THIS TOW: 1) THE RAMP CREW AND GND CTL HAD AN ARRANGEMENT FOR THE MOVEMENT OF THE ACFT. 2) THE RAMP AGENT (TUG DRIVER) WOULD USE AND UNDERSTAND HAND SIGNALS. I ENTERED ACFT AND JUST FINISHED THE FLT COMPARTMENT'S SAFETY INSPECTION AND SECURITY CHKS. AT THIS POINT THE ACFT'S PARKING BRAKES WERE NOT ENGAGED. WE CLOSED THE DOOR (PAX) AND THE TUG DRIVER DROVE OFF WITH US IN TOW. WE TRIED TO CONTACT GND CTL IN TIME BUT THE TUG DRIVER HAD ENTERED AN ACTIVE TXWY. THE GND FREQ WAS ALSO BUSY. THE FIRST TXWY WAS TXWY D. THE TUG DRIVER SEEMED TO PLAN A TURN ONTO TXWY B; ANOTHER INTO THE GATE AREA. THERE WAS AN ACR Y MD80 THAT HAD TO GIVE WAY TO OUR TUG AND ACFT ON TXWY B. WE LATER TALKED TO GND CTL AND HE TOLD US THERE WAS NO PRE-ARRANGEMENT FOR THE ACFT MOVEMENT. HE ALSO THOUGHT THE ACR Y PLT WOULD FILE A COMPLAINT. THE ONLY PERSON AROUND WHO SPOKE ENGLISH WAS THE GATE AGENT. I INFORMED HIM OF THE ENTIRE SIT. HE SAID HE WOULD TALK TO THE TUG DRIVER. THE TUG DRIVER HAD HIS BACK TURNED TO US DURING TOWING. HE COULD NOT SEE THE LNDG LIGHT FLASH EVEN IF HE KNEW WHAT IT MEANT. HE DID POINT TO THE ACR Y MD80 JUST BEFORE OUR TURN ONTO TXWY B AND JUST AFTER TXWY B. WE WERE TOWING THE ACFT WITHOUT A BRAKE RELEASE SIGNAL AND PARKED WITHOUT A BRAKE SET SIGNAL. I SHOULD HAVE COORD BETTER WITH THE DRIVER THROUGH THE RAMP AGENT ALTHOUGH THE LANGUAGE BARRIER WAS STILL SUBSTANTIAL. THE TUG DRIVER MUST REALIZE THAT HE MUST COORD WITH THE PERSON RIDING THE BRAKES AND NOT ENTER AN ACTIVE TXWY WITHOUT CLRNC. THERE WAS NO HEADSET AROUND. WE COULD HAVE AN ENGLISH SPEAKING OPERATOR ON A HEADSET FOR BETTER COM. IF ALL ELSE FAILED; WE COULD HAVE TAXIED OURSELVES WHICH IN THIS CASE WOULD HAVE BEEN EASIER AND SAFER. SUPPLEMENTAL INFO FROM ACN 629706: WE ATTEMPTED TO CONTACT GND CTL AT THAT TIME; BUT WERE UNABLE TO REACH THE CTLR DUE TO FREQ CONGESTION. ADDITIONALLY; WE WERE NOT ABLE TO UNDERSTAND ANYTHING BEING COMMUNICATED ON THE FREQ SINCE ALL CONVERSATION WITH OTHER ACFT WAS IN SPANISH. WHEN THE TUG DRIVER FAILED TO STOP PRIOR TO TRANSITIONING TXWY B; WE ASSUMED THAT A PROC EXISTED LOCALLY AT MONTEREY IN WHICH ACFT COULD BE REPOSITIONED IN THIS MANNER WITHOUT A SPECIFIC ATC CLRNC. OUR TUG DRIVER HAD EFFECTIVELY 'CUT HIM OFF' AND THE MD80 HAD TO STOP IN ORDER TO AVOID TAXIING INTO US. WE IMMEDIATELY CONTACTED GND CTL TO LET HIM KNOW THAT WE WERE NOT IN COM WITH OUR TUG DRIVER AND THAT WE WOULD BE OUT OF THE WAY MOMENTARILY. WHEN I CONTACTED GND CTL APPROX 10 MINS LATER TO PICK UP A CLRNC; HE INFORMED US THAT IN THE FUTURE WE NEEDED A CLRNC PRIOR TO TRANSITIONING OF TXWY B. MY RECOMMENDATIONS TO PREVENT ANOTHER SUCH INCIDENT ARE AS FOLLOWS: 1) HAVE CREWS REPOS ACFT UNDER ITS OWN PWR FROM REMOTE PULLING TO THE TERMINAL AREA. 2) ENSURE THAT ALL PERSONNEL INVOLVED IN HANDING ACFT ARE FAMILIAR WITH PROPER INTERNATIONALLY ACCEPTED STANDARDS FOR HANDLING SUCH AN ACFT; SUCH AS RWY SIGNS AND MARKINGS; ATC PROCS; AND STANDARD HAND SIGNALS.

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

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.