RWY INCURSION; RWY 26; BY A B737 CREW WHEN PIC MISSES A PART OF THE CLRNC FOR A HOLD SHORT AT ABQ; NM.

2003-12 · NASA ASRS report 603224

Date: 2003-12 · Aircraft: B737-300 · Phase: taxi

Anomalies: atc-issue-all-types|conflict-ground-conflict|less-severe|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|ground-incursion-runway

Synopsis

RWY INCURSION; RWY 26; BY A B737 CREW WHEN PIC MISSES A PART OF THE CLRNC FOR A HOLD SHORT AT ABQ; NM.

Narrative

NORMAL PUSHBACK FROM GATE; PERFORMANCE DATA COMPLETED FOR RWY 26. WE CALLED FOR TAXI WITH ATIS AND WERE GIVEN THE OPTION FOR RWY 26 OR RWY 21. AS RWY 21 WAS A MUCH SHORTER TAXI AND RWY ALIGNED CLOSER TO THE DESIRED DEP HEADING; WE REQUESTED RWY 21. WE WERE GIVEN TAXI INSTRUCTIONS; 'GIVE WAY TO REGIONAL JET ON YOUR R AND TAXI TO RWY 21 VIA TXWY C; TXWY E; HOLD SHORT RWY 26.' THIS CLRNC WAS READ BACK VERBATIM BY THE FO. UNFORTUNATELY; DURING BOTH XMISSIONS; I FAILED TO HEAR THE HOLD SHORT PORTION OF THE CLRNC. IN MY MIND; WE WERE CLRED TO CROSS ALL RWYS TO RWY 21. AFTER LOCATING THE RJ; I MADE A R TURN OUT TO MANEUVER BEHIND THE SLOW MOVING ACFT AND TAXIED PER MY PERCEIVED INSTRUCTIONS: TXWY C; TXWY E; RWY 21. MEANWHILE; THE FO WAS HEADS DOWN COMPUTING PERFORMANCE DATA FOR RWY 21. AS A NOTE; I REALIZE THE FOM PROHIBITS COMPUTING OPC DATA WHILE APCHING/XING A RWY; BUT DUE TO THE SLOW MOVING RJ AND THE MANEUVERING REQUIRED TO POS BEHIND SUCH ACFT; I FELT WE HAD SUFFICIENT TIME TO COMPLETE THE PERFORMANCE DATA AND COMPLY WITH THE FOM. THE RJ CONTINUED PAST INTXN C AND I PROCEEDED TO MAKE A R TURN ON TXWY C AND CROSS RWY 26 WITHOUT CLRNC. PRIOR TO XING RWY 26; I LOOKED L AND NOTED COMPANY TFC APPROX 3000-4000 FT AWAY AT TAXI SPD AND COMMENCING A R TURN OFF RWY 26. I THUS CONTINUED TO BE CONFIDENT IN MY PERCEIVED CLRNC TO CROSS THE RWY. APPROX 1/2 WAY ACROSS RWY 25; THE FO LOOKED UP AND TOLD ME WE WERE INSTRUCTED TO HOLD SHORT RWY 26. AT THIS POINT; I INCREASED PWR TO EXPEDITE XING AND ASKED THE FO TO CONFIRM OUR TAXI CLRNC. WE WERE INDEED INSTRUCTED TO HOLD SHORT. FORTUNATELY; NO CONFLICT WITH ANY ACFT OCCURRED. MY THOUGHTS ON HOW THIS SIT OCCURRED: MOST SIGNIFICANT WAS THE FO BEING HEADS DOWN AND COMPUTING PERFORMANCE FOR THE RWY CHANGE. I AM CONFIDENT THIS EVENT WOULD NOT HAVE OCCURRED IF WE WERE BOTH MONITORING THE TAXI RTE. THE OTHER SIGNIFICANT CAUSE WAS MY MISUNDERSTANDING OF THE CLRNC. I BELIEVE THE FACT THAT I WAS BUSY TRYING TO LOCATE AND AVOID HITTING THE RJ; TOGETHER WITH TRYING TO DETERMINE HOW TO NAV MY UNEXPECTED TAXI RTE WHILE THE CLRNC WAS BEING GIVEN CAUSED ME TO HEAR WHAT I WANTED TO HEAR -- TXWY C; TXWY E; TAXI TO RWY 21. ANOTHER ERROR I COMMITTED WAS NOT REPEATING THE TAXI CLRNC TO THE FO; WHICH IS MY USUAL HABIT. TASK OVERLOAD (RJ; NEW RTE) PRECIPITATED THIS LACK OF ACTION ON MY PART. LESSONS LEARNED: I WILL ALWAYS READ BACK TAXI CLRNC AS I UNDERSTAND IT TO THE FO. I WILL; IF POSSIBLE; DELAY MY TAXI UNTIL NEW PERFORMANCE IS CALCULATED GIVEN A RWY CHANGE. IF I HAD FOLLOWED THE ABOVE; I WOULD NOT BE WRITING THIS RPT. SUPPLEMENTAL INFO FROM ACN 603228: ABQ GND CTL ISSUED THE FOLLOWING CLRNC: 'TAXI TO RWY 21 VIA TXWY C AND TXWY E; HOLD SHORT RWY 26; GIVE WAY TO THE REGIONAL JET OFF YOUR R.' I RESPONDED WITH A FULL CLRNC READBACK. I ASKED THE CAPT (WHO WAS LOOKING AT HIS ARPT DIAGRAM) IF HE HAD THE RJ IN SIGHT AND HE SAID; 'I GOT HIM.' AS WE BEGAN THE SLOW TAXI; I STATED TO CAPT; 'I AM HEADS DOWN' AND HE ACKNOWLEDGED. AFTER STOWING THE OPC; I LOOKED UP AND WAS STARTLED TO SEE WE WERE TAXIING OUT ONTO ACTIVE RWY 26. I CALLED OUT; 'STOP; STOP; WE WERE TOLD TO HOLD SHORT OF RWY 26!' CAPT APPLIED THE BRAKES; THEN THE THROTTLES WHEN HE REALIZED WE WOULD BE STOPPED IN THE MIDDLE OF THE RWY; AS THERE WAS AN ACFT SEVERAL THOUSAND FT DOWN ON RWY 26. I ASKED HIM IF HE SAW THE ACFT ON THE RWY AND CAPT STATED; 'YES; BUT THE ACFT WAS AT TAXI SPD AND IT IS NOT UNUSUAL FOR GND CTL TO ISSUE XING CLRNCS UNDER THOSE CIRCUMSTANCES.' WE WORKED VERY WELL TOGETHER AS A TEAM; ADHERING TO COMPANY PROCS DURING OUR TRIP. IT IS VERY DISAPPOINTING TO ME THAT WHEN IT SEEMED WE WERE DOING EVERYTHING RIGHT; SOMETHING SO IMPORTANT WENT WRONG. TO PREVENT AN OCCURRENCE OF THIS NATURE FROM HAPPENING; AGAIN; I WILL INSIST ON COMPLETING OPC/FMC CALCULATIONS ONLY WHEN THE ACFT IS STOPPED. IT WAS A JUDGEMENT CALL; ONE MADE INCORRECTLY. THE DECISION TO MOVE THE ACFT WHILE ONE PERSON WAS HEADS DOWN; REMOVED THE VERY IMPORTANT SECOND SET OF EYES THAT EXISTSAS A SAFETY NET.

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.