37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 414308 |
Time | |
Date | 199809 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : atl |
State Reference | GA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zse |
Operator | common carrier : air carrier |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | climbout : takeoff |
Route In Use | departure other |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | ATR 72 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | ground other : taxi |
Route In Use | arrival other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 210 flight time total : 12000 flight time type : 1700 |
ASRS Report | 414308 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 90 flight time total : 6600 flight time type : 90 |
ASRS Report | 414405 |
Events | |
Anomaly | conflict : airborne less severe incursion : runway non adherence : published procedure non adherence : required legal separation |
Independent Detector | other flight crewa |
Resolutory Action | other other |
Consequence | faa : investigated faa : reviewed incident with flight crew |
Miss Distance | horizontal : 3000 vertical : 0 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Intra Facility Coordination Failure Operational Error |
Narrative:
Per ATIS information at XA53Z, aircraft #1 was planned for takeoff on runway 9R in atl. This was due to runway 9L being notamed closed nightly. However at XD55Z, aircraft #1 was cleared to taxi to reopened runway 9L and runway 9L was entered in the FMS. After short taxi and while on taxiway M, approaching the end of runway 9L, tower cleared us 'position and hold' on runway 9L. While still turning into position, we were issued 'aircraft #1, heavy, fly heading 095 degrees, cleared for takeoff runway 9L.' I xferred control of the aircraft to the first officer and we started takeoff roll. I made '80 KTS throttle hold/engine instruments checked' call and was observing engine temperatures when first officer noted 'what's that?' looking downfield, our airspeed was between 105-120 KTS when I saw an ATR crossing and clearing our runway, apparently down at taxiway south. He was obviously concerned about us as he queried the tower immediately to confirm he had been cleared to cross runway 9L and told them that there was a B767 bearing down on them. I judged by his speed clearing the runway that we would have separation by that point and our current high speed would have caused a risky abort, so I continued takeoff, estimating our horizontal clearance at about 75 ft. Tower confirmed the ATR crossing clearance, but sounded somewhat confused and asked the ATR to confirm he was clear of the runway. It is only our guess but we feel he may have received his crossing clearance before our takeoff clearance because we hadn't heard it. We feel that the controller's mind set was still on the previous runway 9R only operation and possibly the ATR had been given crossing clearance as he exited runway 9R. We were, if not the first, among the first takeoffs on newly opened runway 9L. Contributing factors: change of ATIS and runway operation. Night, 4 mi visibility. Our left wing landing light inoperative on maintenance carry-over. Slight uphill slope runway 9L followed by slight downhill slope further down. Supplemental information from acn 414402: after landing on runway 9R we were cleared to cross runway 9L at taxiway south and contact ground on the other side. As we began to cross runway 9L, I noticed what I thought was an aircraft in position on runway 9L. The aircraft was in fact in a takeoff roll. As we cleared runway 9L the aircraft was approximately 3000 ft from our position. After crossing, we asked tower to verify we were cleared to cross runway 9L. His response was 'affirmative, you are across aren't you?' our response was 'affirmative, we are now, but there was a B767 in a takeoff roll as we crossed.' taxiing in, we were instructed to contact the tower via telephone. I called the tower by phone and they wanted to know what happened. I explained the above incident and they said they would look into it. They did verify again that we were 'cleared to cross runway 9L.' since we were looking at the aircraft on takeoff roll the entire time we were crossing runway 9L, I do not feel safety was compromised. However, this situation may have had a different outcome if the RVR was 1800 ft. This situation was apparently caused by the air traffic controller issuing us a crossing clearance after he had cleared another aircraft for takeoff. The controller did seem to be preoccupied with another aircraft on the ground who was blocking a high speed taxiway. We need to continue to be diligent in guarding against the human error to avoid possible disasters.
Original NASA ASRS Text
Title: ACR B767 FLC OBSERVED AN ATR72 ACFT XING RWY WHEN ON TKOF ROLL. B767 FLC DETERMINE THEY WERE AT A SPD TOO FAST FOR SAFE ABORT, AND CONTINUED TKOF. ATR72 PIC DISCUSSED INCIDENT WITH TWR CONFIRMING THEY HAD XING CLRNC. ATR72 PIC DETERMINED CTLR DISTR BY OTHER TASKS, NOT REALIZING THE CONFLICT.
Narrative: PER ATIS INFO AT XA53Z, ACFT #1 WAS PLANNED FOR TKOF ON RWY 9R IN ATL. THIS WAS DUE TO RWY 9L BEING NOTAMED CLOSED NIGHTLY. HOWEVER AT XD55Z, ACFT #1 WAS CLRED TO TAXI TO REOPENED RWY 9L AND RWY 9L WAS ENTERED IN THE FMS. AFTER SHORT TAXI AND WHILE ON TXWY M, APCHING THE END OF RWY 9L, TWR CLRED US 'POS AND HOLD' ON RWY 9L. WHILE STILL TURNING INTO POS, WE WERE ISSUED 'ACFT #1, HVY, FLY HDG 095 DEGS, CLRED FOR TKOF RWY 9L.' I XFERRED CTL OF THE ACFT TO THE FO AND WE STARTED TKOF ROLL. I MADE '80 KTS THROTTLE HOLD/ENG INSTS CHKED' CALL AND WAS OBSERVING ENG TEMPS WHEN FO NOTED 'WHAT'S THAT?' LOOKING DOWNFIELD, OUR AIRSPD WAS BTWN 105-120 KTS WHEN I SAW AN ATR XING AND CLRING OUR RWY, APPARENTLY DOWN AT TXWY S. HE WAS OBVIOUSLY CONCERNED ABOUT US AS HE QUERIED THE TWR IMMEDIATELY TO CONFIRM HE HAD BEEN CLRED TO CROSS RWY 9L AND TOLD THEM THAT THERE WAS A B767 BEARING DOWN ON THEM. I JUDGED BY HIS SPD CLRING THE RWY THAT WE WOULD HAVE SEPARATION BY THAT POINT AND OUR CURRENT HIGH SPD WOULD HAVE CAUSED A RISKY ABORT, SO I CONTINUED TKOF, ESTIMATING OUR HORIZ CLRNC AT ABOUT 75 FT. TWR CONFIRMED THE ATR XING CLRNC, BUT SOUNDED SOMEWHAT CONFUSED AND ASKED THE ATR TO CONFIRM HE WAS CLR OF THE RWY. IT IS ONLY OUR GUESS BUT WE FEEL HE MAY HAVE RECEIVED HIS XING CLRNC BEFORE OUR TKOF CLRNC BECAUSE WE HADN'T HEARD IT. WE FEEL THAT THE CTLR'S MIND SET WAS STILL ON THE PREVIOUS RWY 9R ONLY OP AND POSSIBLY THE ATR HAD BEEN GIVEN XING CLRNC AS HE EXITED RWY 9R. WE WERE, IF NOT THE FIRST, AMONG THE FIRST TKOFS ON NEWLY OPENED RWY 9L. CONTRIBUTING FACTORS: CHANGE OF ATIS AND RWY OP. NIGHT, 4 MI VISIBILITY. OUR L WING LNDG LIGHT INOP ON MAINT CARRY-OVER. SLIGHT UPHILL SLOPE RWY 9L FOLLOWED BY SLIGHT DOWNHILL SLOPE FURTHER DOWN. SUPPLEMENTAL INFO FROM ACN 414402: AFTER LNDG ON RWY 9R WE WERE CLRED TO CROSS RWY 9L AT TXWY S AND CONTACT GND ON THE OTHER SIDE. AS WE BEGAN TO CROSS RWY 9L, I NOTICED WHAT I THOUGHT WAS AN ACFT IN POS ON RWY 9L. THE ACFT WAS IN FACT IN A TKOF ROLL. AS WE CLRED RWY 9L THE ACFT WAS APPROX 3000 FT FROM OUR POS. AFTER XING, WE ASKED TWR TO VERIFY WE WERE CLRED TO CROSS RWY 9L. HIS RESPONSE WAS 'AFFIRMATIVE, YOU ARE ACROSS AREN'T YOU?' OUR RESPONSE WAS 'AFFIRMATIVE, WE ARE NOW, BUT THERE WAS A B767 IN A TKOF ROLL AS WE CROSSED.' TAXIING IN, WE WERE INSTRUCTED TO CONTACT THE TWR VIA TELEPHONE. I CALLED THE TWR BY PHONE AND THEY WANTED TO KNOW WHAT HAPPENED. I EXPLAINED THE ABOVE INCIDENT AND THEY SAID THEY WOULD LOOK INTO IT. THEY DID VERIFY AGAIN THAT WE WERE 'CLRED TO CROSS RWY 9L.' SINCE WE WERE LOOKING AT THE ACFT ON TKOF ROLL THE ENTIRE TIME WE WERE XING RWY 9L, I DO NOT FEEL SAFETY WAS COMPROMISED. HOWEVER, THIS SIT MAY HAVE HAD A DIFFERENT OUTCOME IF THE RVR WAS 1800 FT. THIS SIT WAS APPARENTLY CAUSED BY THE AIR TFC CTLR ISSUING US A XING CLRNC AFTER HE HAD CLRED ANOTHER ACFT FOR TKOF. THE CTLR DID SEEM TO BE PREOCCUPIED WITH ANOTHER ACFT ON THE GND WHO WAS BLOCKING A HIGH SPD TXWY. WE NEED TO CONTINUE TO BE DILIGENT IN GUARDING AGAINST THE HUMAN ERROR TO AVOID POSSIBLE DISASTERS.
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.