37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 605841 |
Time | |
Date | 200401 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : atl.airport |
State Reference | GA |
Altitude | msl bound lower : 1426 msl bound upper : 3500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : atl.tower |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | landing : missed approach |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : atl.tower |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 60 flight time total : 10500 flight time type : 300 |
ASRS Report | 605841 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : airborne critical |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : took precautionary avoidance action |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airport ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
After being cleared to land on runway 26R in atl, it became clear that landing traffic (cpr king air) ahead of me would not clear runway 27R. Over the landing threshold for runway 26R, atl tower advised us to 'go around, landing traffic ahead still on your runway...climb to 3500 ft and fly runway heading.' we complied and read back the go around clearance as issued. An air carrier B737 had simultaneously been cleared for takeoff on runway 26L (the parallel runway) as we did the go around. I overheard his departure clearance to be 'climb 10000 ft, fly heading 330 degrees.' this registered in my mind as an immediate and dangerous conflict. I looked left to see the B737 turn towards our flight path. I started an immediate right turn to a 330 degree heading to avoid the approaching aircraft. Atl tower saw and realized the conflict and immediately issued B737 a 'fly runway heading.' the conflict was resolved by our own action and by the quick intervention by atl tower. After landing in atl, I called the tower supervisor and we agreed that by not issuing a takeoff clearance with a right turn until landing is assured on the parallel runway, would prevent this from recurring. There was 'some confusion' as 'to whom' the original 330 degree heading was issued. I'm certain that it was issued to the departing B737, as that was the heading required to accidentally point him directly towards me. In our busy ATC system, it is important to know your own clearance, and listen and know what your traffic is doing or about to do.
Original NASA ASRS Text
Title: FLT CREW OF CL65 INCUR LOSS OF SEPARATION WITH DEPARTING ACFT AFTER MAKING A GAR ON PARALLEL RWY.
Narrative: AFTER BEING CLRED TO LAND ON RWY 26R IN ATL, IT BECAME CLR THAT LNDG TFC (CPR KING AIR) AHEAD OF ME WOULD NOT CLR RWY 27R. OVER THE LNDG THRESHOLD FOR RWY 26R, ATL TWR ADVISED US TO 'GO AROUND, LNDG TFC AHEAD STILL ON YOUR RWY...CLB TO 3500 FT AND FLY RWY HDG.' WE COMPLIED AND READ BACK THE GAR CLRNC AS ISSUED. AN ACR B737 HAD SIMULTANEOUSLY BEEN CLRED FOR TKOF ON RWY 26L (THE PARALLEL RWY) AS WE DID THE GAR. I OVERHEARD HIS DEP CLRNC TO BE 'CLB 10000 FT, FLY HDG 330 DEGS.' THIS REGISTERED IN MY MIND AS AN IMMEDIATE AND DANGEROUS CONFLICT. I LOOKED L TO SEE THE B737 TURN TOWARDS OUR FLT PATH. I STARTED AN IMMEDIATE R TURN TO A 330 DEG HDG TO AVOID THE APCHING ACFT. ATL TWR SAW AND REALIZED THE CONFLICT AND IMMEDIATELY ISSUED B737 A 'FLY RWY HDG.' THE CONFLICT WAS RESOLVED BY OUR OWN ACTION AND BY THE QUICK INTERVENTION BY ATL TWR. AFTER LNDG IN ATL, I CALLED THE TWR SUPVR AND WE AGREED THAT BY NOT ISSUING A TKOF CLRNC WITH A R TURN UNTIL LNDG IS ASSURED ON THE PARALLEL RWY, WOULD PREVENT THIS FROM RECURRING. THERE WAS 'SOME CONFUSION' AS 'TO WHOM' THE ORIGINAL 330 DEG HDG WAS ISSUED. I'M CERTAIN THAT IT WAS ISSUED TO THE DEPARTING B737, AS THAT WAS THE HDG REQUIRED TO ACCIDENTALLY POINT HIM DIRECTLY TOWARDS ME. IN OUR BUSY ATC SYS, IT IS IMPORTANT TO KNOW YOUR OWN CLRNC, AND LISTEN AND KNOW WHAT YOUR TFC IS DOING OR ABOUT TO DO.
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.