37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 632943 |
Time | |
Date | 200410 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : bwi.airport |
State Reference | MD |
Altitude | agl bound lower : 0 agl bound upper : 500 |
Environment | |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : bwi.tower |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | climbout : takeoff ground : takeoff roll |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : bwi.tower |
Operator | common carrier : air carrier |
Make Model Name | B717 (Formerly MD-95) |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time total : 12000 flight time type : 1300 |
ASRS Report | 632943 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
ASRS Report | 632772 |
Events | |
Anomaly | conflict : ground critical non adherence : published procedure non adherence : required legal separation |
Independent Detector | other controllera other flight crewa other flight crewb |
Resolutory Action | controller : issued advisory controller : issued new clearance flight crew : took evasive action |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Departing bwi and captain's leg, pushback and taxi out to runway 28 at intersection B departure all normal. Tower gave us position and hold on runway 28 as air carrier Y, B717 was landing on crossing runway 33L (approximately 4700 ft from our position on the runway). As air carrier Y was crossing our runway the tower cleared us for an immediate takeoff because he had air carrier Z B737 on a 2 mi final for runway 33L. After readback of the clearance the tower then issued a clearance to air carrier Y to make a 180 degree turn on runway 33L and exit at the next taxiway. As I was making the 80 KTS callout the tower was informing air carrier Y that he was right at taxiway right that he was to exit runway 33L from and to make a hard left turnoff the runway. At this point the captain 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 left turnoff was our runway. As a matter of fact, the captain was so concerned that some of his attention was diverted to this situation that he even failed to respond with his callout to the 80 KTS. I knew why and looked over to confirm his airspeed was comparable to mine, now around 90 KTS and made the remark it's good. All the while air carrier Y is still taxiing south on runway 33L towards our runway. The next transmission from the tower was for air carrier Y to stop because they are now approaching an active runway. They failed to comply with this ATC instruction. A very short pause and the next transmission from the tower was air carrier Y stop, stop, just stop with urgency in the controller's voice. At this time we were around 115 KTS and accelerating quickly towards the intersection of runways 28 and 33L and the B717 was still moving in our direction. I then yelled out abort, abort, abort at the sam time the captain decided to go toga and rotate. We estimate we broke ground around 120 KTS and east of the intersecting runways. By this time air carrier Y did finally stop somewhere just short of our intersecting runway. 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 tower seemed to down play the event since air carrier Y did stop before our runway and we were already airborne. Preventative action would have been for the tower to have air carrier Y taxi to the next taxiway in the aircraft's direction of travel instead of making a 180 degree turn on an active landing runway. Also, but not sure of, maybe air carrier Y was thinking our runway was the taxiway that the tower wanted them to turn on to. Supplemental information from acn 632772: I decided that we could never stop in time, and if air carrier Y continued onto our runway 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 degrees pitch (I'm estimating) to allow the aircraft to fly itself off in ground effect and hopefully over air carrier Y aircraft. The aircraft flew off very shortly thereafter and was about 200 ft AGL upon passing runway 33L. From a CRM standpoint, I wish I could have told the first officer what I was thinking, but the time was way too short, and my concentration was total. The fact is, however, that an experienced flight crew felt themselves in imminent danger. From our perspective in the high speed regime on takeoff, the tone of the controller's voice to air carrier 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 reporter on acn 632772 revealed the following information: the reporter stated while rotating he could not see how close the B717 was to his runway, but was told by the other pilot that the B717 nose was slightly sticking out onto the runway. He believes the B717 crew was not aware that they were departing runway 28, but thinks the B717 crew at first only saw the B737 on short final for runway 33L and was expediting to get off the runway. He said the B737 went around.
Original NASA ASRS Text
Title: 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 SAM 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.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.