WELL INTO THEIR TKOF ROLL AT BWI; AN A320 CREW HEARD THE TWR TALKING TO A B717 THAT HAD LANDED ON A XING RWY AND WAS BACK-TAXIING TOWARD THEIR RWY.
Synopsis
WELL INTO THEIR TKOF ROLL AT BWI; AN A320 CREW HEARD THE TWR TALKING TO A B717 THAT HAD LANDED ON A XING RWY AND WAS BACK-TAXIING TOWARD THEIR RWY.
Narrative
DEPARTING BWI AND CAPT'S LEG; PUSHBACK AND TAXI OUT TO RWY 28 AT INTXN B DEP ALL NORMAL. TWR GAVE US POS AND HOLD ON RWY 28 AS ACR Y; B717 WAS LNDG ON XING RWY 33L (APPROX 4700 FT FROM OUR POS ON THE RWY). AS ACR Y WAS XING OUR RWY THE TWR CLRED US FOR AN IMMEDIATE TKOF BECAUSE HE HAD ACR Z B737 ON A 2 MI FINAL FOR RWY 33L. AFTER READBACK OF THE CLRNC THE TWR THEN ISSUED A CLRNC TO ACR Y TO MAKE A 180 DEG TURN ON RWY 33L AND EXIT AT THE NEXT TXWY. AS I WAS MAKING THE 80 KTS CALLOUT THE TWR WAS INFORMING ACR Y THAT HE WAS RIGHT AT TXWY R THAT HE WAS TO EXIT RWY 33L FROM AND TO MAKE A HARD L TURNOFF THE RWY. AT THIS POINT THE CAPT AND I WERE BECOMING CONCERNED ABOUT THE B717 BECAUSE THERE SEEMED TO BE SOME CONFUSION ON THEIR PART AS TO WHERE THEY NEEDED TO EXIT AND THE NEXT L TURNOFF WAS OUR RWY. AS A MATTER OF FACT; THE CAPT WAS SO CONCERNED THAT SOME OF HIS ATTN WAS DIVERTED TO THIS SIT THAT HE EVEN FAILED TO RESPOND WITH HIS CALLOUT TO THE 80 KTS. I KNEW WHY AND LOOKED OVER TO CONFIRM HIS AIRSPD WAS COMPARABLE TO MINE; NOW AROUND 90 KTS AND MADE THE REMARK IT'S GOOD. ALL THE WHILE ACR Y IS STILL TAXIING S ON RWY 33L TOWARDS OUR RWY. THE NEXT XMISSION FROM THE TWR WAS FOR ACR Y TO STOP BECAUSE THEY ARE NOW APCHING AN ACTIVE RWY. THEY FAILED TO COMPLY WITH THIS ATC INSTRUCTION. A VERY SHORT PAUSE AND THE NEXT XMISSION FROM THE TWR WAS ACR Y STOP; STOP; JUST STOP WITH URGENCY IN THE CTLR'S VOICE. AT THIS TIME WE WERE AROUND 115 KTS AND ACCELERATING QUICKLY TOWARDS THE INTXN OF RWYS 28 AND 33L AND THE B717 WAS STILL MOVING IN OUR DIRECTION. I THEN YELLED OUT ABORT; ABORT; ABORT AT THE SAME TIME THE CAPT DECIDED TO GO TOGA AND ROTATE. WE ESTIMATE WE BROKE GND AROUND 120 KTS AND E OF THE INTERSECTING RWYS. BY THIS TIME ACR Y DID FINALLY STOP SOMEWHERE JUST SHORT OF OUR INTERSECTING RWY. WE CONTINUED ON TO LAS WITHOUT ANY OTHER INCIDENTS. AS WE CAN SEE WE WERE VERY COGNIZANT TO OUR SITUATIONAL AWARENESS AND DECIDED TO TAKE ACTION DUE TO THE IMPENDING COLLISION. THE TWR SEEMED TO DOWN PLAY THE EVENT SINCE ACR Y DID STOP BEFORE OUR RWY AND WE WERE ALREADY AIRBORNE. PREVENTATIVE ACTION WOULD HAVE BEEN FOR THE TWR TO HAVE ACR Y TAXI TO THE NEXT TXWY IN THE ACFT'S DIRECTION OF TRAVEL INSTEAD OF MAKING A 180 DEG TURN ON AN ACTIVE LNDG RWY. ALSO; BUT NOT SURE OF; MAYBE ACR Y WAS THINKING OUR RWY WAS THE TXWY THAT THE TWR WANTED THEM TO TURN ON TO. SUPPLEMENTAL INFO FROM ACN 632772: I DECIDED THAT WE COULD NEVER STOP IN TIME; AND IF ACR Y CONTINUED ONTO OUR RWY WE WOULD SPEAR HIM DIRECTLY. I REMEMBER THINKING IT WILL FLY. I IMMEDIATELY WENT TO TOGA; AND BEGAN A VERY CAREFUL; DELIBERATE ROTATION TO AROUND 8-10 DEGS PITCH (I'M ESTIMATING) TO ALLOW THE ACFT TO FLY ITSELF OFF IN GND EFFECT AND HOPEFULLY OVER ACR Y ACFT. THE ACFT FLEW OFF VERY SHORTLY THEREAFTER AND WAS ABOUT 200 FT AGL UPON PASSING RWY 33L. FROM A CRM STANDPOINT; I WISH I COULD HAVE TOLD THE FO WHAT I WAS THINKING; BUT THE TIME WAS WAY TOO SHORT; AND MY CONCENTRATION WAS TOTAL. THE FACT IS; HOWEVER; THAT AN EXPERIENCED FLT CREW FELT THEMSELVES IN IMMINENT DANGER. FROM OUR PERSPECTIVE IN THE HIGH SPD REGIME ON TKOF; THE TONE OF THE CTLR'S VOICE TO ACR Y WAS TRULY DISCONCERTING. WE DID NOT OVERREACT. A POTENTIAL ACCIDENT WAS AVERTED; AND I'M NOT SURE ANYONE ELSE INVOLVED EVEN KNEW HOW CLOSE IT WAS; FROM WHERE WE WERE SITTING. CALLBACK CONVERSATION WITH RPTR ON ACN 632772 REVEALED THE FOLLOWING INFO: THE RPTR STATED WHILE ROTATING HE COULD NOT SEE HOW CLOSE THE B717 WAS TO HIS RWY; BUT WAS TOLD BY THE OTHER PLT THAT THE B717 NOSE WAS SLIGHTLY STICKING OUT ONTO THE RWY. HE BELIEVES THE B717 CREW WAS NOT AWARE THAT THEY WERE DEPARTING RWY 28; BUT THINKS THE B717 CREW AT FIRST ONLY SAW THE B737 ON SHORT FINAL FOR RWY 33L AND WAS EXPEDITING TO GET OFF THE RWY. HE SAID THE B737 WENT AROUND.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.