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.

Related reports:

Google
 

Original NASA ASRS Text

Title: 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.

Data retrieved from NASA's ASRS site as of April 2012 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.