A319 FLT CREW HAS A RWY INCURSION AT BOS.

Date: 2006-03 · Aircraft: A319 · Phase: taxi

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

Synopsis

A319 FLT CREW HAS A RWY INCURSION AT BOS.

Narrative

I EXPERIENCED A RWY INCURSION AT RWY 22L AT BOS THIS MORNING. I WAS THE FO. WE TAXIED OUT TO RWY 22R FROM GATE. WE FOLLOWED A B737 TO THE RWY. B737 PROCEEDED TO TAKE OFF RWY 22R. WE THEN WERE CLRED TO CROSS RWY 22R AND WHAT I THOUGHT WAS A CLRNC TO TAXI INTO POS AND HOLD ON RWY 22L. WE TAXIED INTO POS AND HOLD ON RWY 22L AND WAITED FOR OUR TKOF CLRNC. ABOUT 10 SECONDS AFTER WE WERE CLRED INTO POS AND HOLD; A BE1900D VERIFIED IF THEY WERE CLRED TO LAND ON RWY 22L TWR THEN ASKED US WHO TOLD US TO GO INTO POS AND HOLD AND I SAID THAT WE THOUGHT THAT THEY DID. TWR PROCEEDED TO TELL 1900 TO GO AROUND AND ASKED US TO TURN R ONTO THE FIRST TXWY; EXIT THE RWY AND TO HOLD SHORT RWY 22L. AFTER 1900 LANDED; WE WERE CLRED TO TAKE OFF. LOOKING BACK ON THE EVENT IT APPEARED THAT WE WERE CLRED TO TAXI INTO POS AND HOLD ON RWY 22L. THE LAST CLRNC WE WERE GIVEN WAS TO CROSS RWY 22R AND MONITOR TWR ON 132.22. THE FIRST TWR CTLR NEVER TOLD US TO CONTACT TWR 132.22. THE FIRST CTLR ALSO NEVER TOLD US TO CROSS RWY 22L AND HOLD SHORT RWY 22R. THE PROC/LANGUAGE I HAVE ALWAYS BEEN USED IS TO CROSS ONE RWY FOR TAKING OFF FROM ANOTHER AND BEING TOLD TO HOLD SHORT OF THE RWY WE WERE GOING TO TAKE OFF FROM. AS WELL THE SECOND CTLR NEVER CONTACTED US AND WE MONITORED THE FREQ TO TELL US TO HOLD SHORT RWY 22L. I FEEL THAT THESE FACTORS WOULD HAVE HELPED PREVENT THIS INCURSION FROM HAPPENING. SUPPLEMENTAL INFO FROM ACN 690654: I EXPERIENCED A RWY INCURSION AT BOS; AN ARPT I HAVE ONLY FLOWN INTO 3 TIMES IN THE LAST 10+ YRS. I FEEL THAT THERE WERE SEVERAL MITIGATING FACTORS THAT CAUSED THIS EVENT. FIRST; I WAS VERY RUSHED JUST PRIOR TO PUSHBACK. I HAD SEVERAL MEL'S TO DEAL WITH. I HAD TRIED TO CONTACT MAINT CTL ON COMPANY RADIO ABOUT 30 MINS BEFORE PUSHBACK; BUT WAS UNABLE TO REACH THEM; SO I SENT 3 ACARS MESSAGES: 2 TO MAINT CTL AND 1 TO OPS. MAINT CTL CALLED BACK LESS THAN 10 MINS PRIOR TO PUSH. I COPIED ALL THE INFO FOR THE MEL'S; AND WAS ABLE TO PUSH BACK ON TIME. WE TAXIED TO A DIFFERENT RWY THAN I HAD EXPECTED TO GO TO; BECAUSE OF A CHANGE IN THE ATIS. IT HAD BEEN MANY YRS SINCE I HAD TAXIED TO THIS END OF THE ARPT. ANOTHER ACFT WAS DEPARTING RWY 22R; WHICH SURPRISED ME; BECAUSE I THOUGHT ALL THE DEPS WERE ON RWY 22L; SINCE IT WAS THE LONG RWY. TWR TOLD US TO CROSS RWY 22R; AND I THOUGHT; POS AND HOLD ON RWY 22L; SO THAT IS WHAT I DID. WHILE WE WERE ON THE RWY; TWR ASKED US WHO TOLD US TO TAXI INTO POS ON THE RWY. WE RESPONDED THAT WE THOUGHT HE DID. WE EXITED THE RWY FOR LNDG TFC; AND THEN WERE TOLD TO TAXI BACK INTO POS AND HOLD. THEN WE DEPARTED. AS I THINK BACK; THE FIRST TWR CTLR MUST HAVE JUST TOLD US TO CROSS RWY 22R AND MONITOR THE OTHER TWR FREQ. I FEEL THAT IF THE FIRST TWR CTLR HAD TOLD US TO CROSS RWY 22R; HOLD SHORT OF RWY 22L; AND MONITOR THE OTHER TWR FREQ; I NEVER WOULD HAVE TAXIED ON THE RWY. ALSO; IF HE WOULD HAVE TOLD US TO CROSS RWY 22R; AND CONTACT THE OTHER TWR FREQ; I WOULD NOT HAVE TAXIED ON THE RWY -- BECAUSE HE WOULD HAVE ACKNOWLEDGED US; AND HE WOULD HAVE TOLD US TO HOLD SHORT OF RWY 22L. IN THE END; NO ONE TOLD US TO HOLD SHORT OF RWY 22L. IN FACT; THE CTLR OF RWY 22L SEEMED UNAWARE OF OUR POS; UNTIL AN ARRIVING ACFT QUESTIONED HIS LNDG CLRNC TO HIM. IN RETROSPECT; I FEEL THAT CONCISE; CLR COM IS ESSENTIAL; AND THAT THE CTLRS SHOULD MAKE SURE THAT THE PLTS HAVE FULL UNDERSTANDING OF WHAT IS EXPECTED OF THEM -- INSTEAD OF GIVING JUST THE MINIMUM INFO REQUIRED PER THE CTLR HANDBOOK. IN ADDITION; CONSIDERATION MUST BE GIVEN TO THE FACTS THAT: THAT NIGHT'S LAYOVER HOTEL ROOM WAS INADEQUATE; IN THAT I HAD TO SWITCH ROOMS DUE TO CIGARETTE SMOKE ODOR; THEN EVEN THE SECOND ROOM HAD SOMEONE SMOKING RIGHT NEXT DOOR; WHICH MADE IT DIFFICULT TO GO TO SLEEP. SECONDLY; I HAD TO WAKE UP EARLY FOR AN EARLY SHOW. THIRDLY; THIS WAS THE FIFTH CONSECUTIVE DAY OF FLYING; PUTTING ME CLOSE TO MY MAX FLYING TIME IN 7 DAYS.

More incidents for this aircraft family →

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