37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 634600 |
Time | |
Date | 200410 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : dfw.airport |
State Reference | TX |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-500 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : holding |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : dfw.tower |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : takeoff roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 400 flight time total : 17947 flight time type : 2050 |
ASRS Report | 634600 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 210 flight time total : 10000 flight time type : 2000 |
ASRS Report | 634599 |
Events | |
Anomaly | conflict : ground critical non adherence : published procedure non adherence : required legal separation |
Independent Detector | atc equipment other atc equipment : twr brite radar aircraft equipment : tcas other controllera other flight crewa other flight crewb other other : 4 |
Resolutory Action | controller : issued new clearance flight crew : executed go around |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | ATC Human Performance |
Narrative:
After a lengthy ground delay we were #1 for takeoff holding short of runway 35L. An rj was holding in position on runway 35L. The first officer and I both noticed a jet on final approach a couple mi out, however, since it was nighttime it was difficult to tell if it was our runway (35L) or a parallel runway the jet was lined up for. After scanning my TCASII display and looking back out the window it then became obvious to both the first officer and I, the jet was lined up for runway 35L. About this time tower controller cleared the rj for takeoff. We were then cleared for position and hold on runway 35L with the jet on about a mi final. Without moving our aircraft or releasing the parking brake my first officer told dfw tower looks like a plane on short final runway 35L. The controller then immediately ordered air carrier Y to go around while stating they were lined up on the wrong runway. The spacing looked tight as the rj was just rotating while the MD80 started their go around. The controller never followed up with a hold short clearance for us although it may have been obvious at this point we weren't going to take the runway. After a while we were cleared for takeoff and had a routine flight to ord. The safety chain broke down significantly with this incident. Had we accepted the position and hold clearance without checking the final approach, a major hull loss with our B737 and the MD80 was very possible. It was clear to us the controller never knew the MD80 was lined up on the wrong runway until we intervened on the radio. Had the controller not cleared the rj for takeoff, or cleared the rj at a later point in time, a hull loss between the MD80 and the rj was also very possible. I also wondered why the PNF on the MD80 allowed the PF to line up and continue approach to the wrong runway. Also, why didn't dfw approach control notify the MD80 or the tower of the wrong line-up. Without our radio call breaking the error chain this could have turned out very bad indeed. This was simply cutting things much too fine for a safe operation.
Original NASA ASRS Text
Title: A B737 CREW INSTRUCTED POS AND HOLD BEHIND AN RJ DEPARTING, ADVISES DFW TWR OF AN MD80 ON A SHORT FINAL FOR THE SAME RWY.
Narrative: AFTER A LENGTHY GND DELAY WE WERE #1 FOR TKOF HOLDING SHORT OF RWY 35L. AN RJ WAS HOLDING IN POS ON RWY 35L. THE FO AND I BOTH NOTICED A JET ON FINAL APCH A COUPLE MI OUT, HOWEVER, SINCE IT WAS NIGHTTIME IT WAS DIFFICULT TO TELL IF IT WAS OUR RWY (35L) OR A PARALLEL RWY THE JET WAS LINED UP FOR. AFTER SCANNING MY TCASII DISPLAY AND LOOKING BACK OUT THE WINDOW IT THEN BECAME OBVIOUS TO BOTH THE FO AND I, THE JET WAS LINED UP FOR RWY 35L. ABOUT THIS TIME TWR CTLR CLRED THE RJ FOR TKOF. WE WERE THEN CLRED FOR POS AND HOLD ON RWY 35L WITH THE JET ON ABOUT A MI FINAL. WITHOUT MOVING OUR ACFT OR RELEASING THE PARKING BRAKE MY FO TOLD DFW TWR LOOKS LIKE A PLANE ON SHORT FINAL RWY 35L. THE CTLR THEN IMMEDIATELY ORDERED ACR Y TO GO AROUND WHILE STATING THEY WERE LINED UP ON THE WRONG RWY. THE SPACING LOOKED TIGHT AS THE RJ WAS JUST ROTATING WHILE THE MD80 STARTED THEIR GAR. THE CTLR NEVER FOLLOWED UP WITH A HOLD SHORT CLRNC FOR US ALTHOUGH IT MAY HAVE BEEN OBVIOUS AT THIS POINT WE WEREN'T GOING TO TAKE THE RWY. AFTER A WHILE WE WERE CLRED FOR TKOF AND HAD A ROUTINE FLT TO ORD. THE SAFETY CHAIN BROKE DOWN SIGNIFICANTLY WITH THIS INCIDENT. HAD WE ACCEPTED THE POS AND HOLD CLRNC WITHOUT CHKING THE FINAL APCH, A MAJOR HULL LOSS WITH OUR B737 AND THE MD80 WAS VERY POSSIBLE. IT WAS CLR TO US THE CTLR NEVER KNEW THE MD80 WAS LINED UP ON THE WRONG RWY UNTIL WE INTERVENED ON THE RADIO. HAD THE CTLR NOT CLRED THE RJ FOR TKOF, OR CLRED THE RJ AT A LATER POINT IN TIME, A HULL LOSS BTWN THE MD80 AND THE RJ WAS ALSO VERY POSSIBLE. I ALSO WONDERED WHY THE PNF ON THE MD80 ALLOWED THE PF TO LINE UP AND CONTINUE APCH TO THE WRONG RWY. ALSO, WHY DIDN'T DFW APCH CTL NOTIFY THE MD80 OR THE TWR OF THE WRONG LINE-UP. WITHOUT OUR RADIO CALL BREAKING THE ERROR CHAIN THIS COULD HAVE TURNED OUT VERY BAD INDEED. THIS WAS SIMPLY CUTTING THINGS MUCH TOO FINE FOR A SAFE OP.
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.