Air Carrier Flight Crew reports inadvertently changing VHF frequency after a runway change during arrival to ATL. After the error is discovered the crew is vectored around for another approach.
Synopsis
Air Carrier Flight Crew reports inadvertently changing VHF frequency after a runway change during arrival to ATL. After the error is discovered the crew is vectored around for another approach.
Narrative
While descending into ATL on the ERLIN5 Arrival; we were approaching ERLIN and ATL Approach had told us to expect Runway 9R. We had already set up the FMGC for that approach. At about 1.5 miles from ERLIN Intersection we were given a runway change and told to expect Runway 8L and descend to 6000 FT and turn to heading 170 and maintain 210 KTS. We did all as instructed. This runway/approach change 1.5 miles from the fix close in to the airport created a fairly high workload at a very inopportune time. I went heads down and reprogrammed the box for Runway 8L and then cleared out all intervening arrival points. I also set the Tower freq in the #1 VHF communication standby window (as is normal). Unfortunately; as we were descending to 6000 FT and turning and slowing; I noticed a 747 on approach at our 1 o'clock position. The 170 heading appeared to be a course that would take us very near the 747. I then noticed the 747 initiating a climb and our TCAS gave us a TCAS Traffic advisory 'Traffic' (this possibility of getting a TCAS TA was something we had been discussing). I was hearing a variety of headings assignments being given over the #1 VHF frequency (which I assumed was due to a very busy arrival bank). After checking the VHF #1 freq selected I realized that Tower was in the active window. I quickly called and Tower said approach was looking for us. I called and they indicated that they had been trying to reach us and then provided vectors to resequence us for a normal visual approach and landing to Runway 8L. I think that flying on 5 of the last seven days with 4 days having report times ranging from 4am-6am and nearly 29 hours of flight time had an impact on the my level of fatigue and alertness.
Second reporter narrative
I believe this incident's genesis began as the aircraft approached the ERLIN intersection. We were initially assigned runway 9R upon initial check-in with ATL approach. We proceeded to level at 12;000 at ERLIN as assigned and completed the remainder of the FMGC reprogramming (removal of the points north of runway 8L to accommodate landing on 9R); as 8L was initially briefed. Approximately 1.5-2 miles prior to ERLIN we were assigned runway 8L. As we proceeded to STUTZ; speed 210k and 6;000 feet were subsequently assigned. In this descent we were also assigned a heading of 170 degrees. I was hand flying the aircraft; with the autothrottle and autothrust off. Conditions at ATL were VFR. With the runway change approximately 20 miles from the field the Captain was very busy with the reprogramming of the FMGC for 8L and cleaning up the remaining points preparing to land. At some point in this sequence apparently; the frequency had changed on VHF 1. I did not recognize the fact that the frequency was on tower as I continued to hear headings and speeds assigned to other aircraft. With discussions between us wondering if the turn onto final was to come soon; we then noticed TCAS traffic approaching from the 2 o'clock position heading towards us in a climb; with less than 1;000ft and 4 miles separation. We both discussed the possibility of a TCAS RA starting; but this did not occur. Soon after this the Captain was able to reestablish contact with Approach and they stated they were trying to contact us for some time. We were then vectored back around for the approach and uneventful landing on 8L.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.