A TAXIING PA31-350 PLT CROSSES RWY 6R WITHOUT CLRNC WHEN HE HAD READ BACK CLRED TO RWY 6L WITHOUT ANY CORRECTION BY CONTRACT CTLR AT PGUM; GU.

Date: 1999-09 · Aircraft: PA-31 Navajo/Chieftan/Mojave/T1040 · Phase: taxi

Anomalies: deviation-discrepancy-procedural-clearance|ground-incursion-runway

Synopsis

A TAXIING PA31-350 PLT CROSSES RWY 6R WITHOUT CLRNC WHEN HE HAD READ BACK CLRED TO RWY 6L WITHOUT ANY CORRECTION BY CONTRACT CTLR AT PGUM; GU.

Narrative

I AM VERY WARY OF TAXI CLRNCS THAT CLR YOU TO ONE RWY THAT REQUIRES THE XING OF ANOTHER ENRTE. IN THIS INSTANCE; THE CLRNC I RECEIVED WAS 'TAXI TO RWY 6L VIA TXWY D.' THIS REQUIRED ME TO CROSS RWY 6R IN THE PROCESS AND IS NOT AN UNCOMMON CLRNC FOR ME TO RECEIVE. I READ BACK THE CLRNC AS I HEARD IT AND SET OFF. AS I WAS CLRING RWY 6R AND TXWY D ENRTE TO RWY 6L; GND/TWR (THE CTLR WAS WORKING BOTH POS) CAME ON AND SAID THAT I HAD ONLY BEEN CLRED TO RWY 6R AT TXWY D. I AM POSITIVE HEARD RWY 6L IN THE INITIAL CLRNC. MY CONCERN IS THAT; IF I WAS INCORRECT IN MY READBACK; WHY WAS IT NOT NOTICED? IS THAT NOT THE REASON WE READ CLRNCS BACK? BY MY RECOLLECTION; I WAS THE ONLY TFC THEY WERE WORKING AT THAT MOMENT; BUT MAYBE WORKLOAD WAS A FACTOR IN THE CAB. ON SEVERAL PREVIOUS OCCASIONS; WHEN CLRED TO RWY 6L; THEY CORRECTED THEMSELVES AFTER MY READBACK. IN THE FUTURE; I WILL QUERY THEM HARDER IF I AM SUSPICIOUS AND NOT JUST COUNT ON A READBACK TO KEEP THINGS CLR. I WILL HATE TO CONTINUALLY QUESTION THE INTENTIONS OF CTLRS; BUT IF PLTS ARE HELD RESPONSIBLE FOR BAD CLRNCS AND UNCAUGHT BAD READBACKS; THEN WE HAVE TO DO IT TO PROTECT OURSELVES. IN ADDITION; IT WOULD BE WISE FOR ME TO WRITE DOWN EVEN THE SIMPLEST TAXI CLRNC; AS AFTER SEVERAL DAYS ON DUTY; IT BECOMES DIFFICULT TO REMEMBER WHAT YOU HAVE HEARD.

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