Narrative:

We were receiving vectors from the final approach controller for the visual approach to runway 28 in atl. We had been given a turn to a heading of 360 degrees which was perpendicular to the final approach course to runway 28. We were asked if we had the traffic in sight that we would be following; in which we responded in the affirmative. As we got within about 3 miles of the final approach course for runway 28; the first officer and I both questioned each other whether they were going to turn us in time to intercept. I; the pilot not flying; queried ATC as soon as radio traffic allowed. We were close to the final approach course with a 90 degree intercept at that point and ATC immediately gave us a turn to the southwest. We complied with the instructions as we overshot the localizer course for runway 28 and encroached on the approach airspace for runway 27L. We were told that we were on the wrong frequency. We were given the correct frequency. After checking in with final approach control for runway 28; we were cleared for the visual approach. At some point while being vectored to final; the frequency got changed from the final approach controller to the initial approach controller. I do not know how the frequency got changed. I never heard a 'click' when a frequency is changed. I noticed the controller's voice sounded somewhat different; but assumed there had been a controller change. At all times during the event we had visual contact with the other aircraft in the area and we did not receive a TCAS alert. Inadvertently changing an approach frequency during a critical time is an error that occurred during this event. This error led to the aircraft not being at its expected location on final approach. Fortunately; we were able to maintain visual separation with other aircraft and continue the approach uneventfully. Being that I can't determine how the frequency got changed when it did; I'm not sure there is a solution to prevent this event from happening. It's an error that could happen to anyone.

Related reports:

Google
 

Original NASA ASRS Text

Title: CRJ700 flight crew reports an inadvertent frequency change during approach causing a localizer overshoot before communication can be reestablished. See ACN 1105166.

Narrative: We were receiving vectors from the final Approach Controller for the visual approach to Runway 28 in ATL. We had been given a turn to a heading of 360 degrees which was perpendicular to the final approach course to Runway 28. We were asked if we had the traffic in sight that we would be following; in which we responded in the affirmative. As we got within about 3 miles of the final approach course for Runway 28; the First Officer and I both questioned each other whether they were going to turn us in time to intercept. I; the pilot not flying; queried ATC as soon as radio traffic allowed. We were close to the final approach course with a 90 degree intercept at that point and ATC immediately gave us a turn to the southwest. We complied with the instructions as we overshot the localizer course for Runway 28 and encroached on the approach airspace for Runway 27L. We were told that we were on the wrong frequency. We were given the correct frequency. After checking in with final Approach Control for Runway 28; we were cleared for the visual approach. At some point while being vectored to final; the frequency got changed from the final Approach Controller to the initial Approach Controller. I do not know how the frequency got changed. I never heard a 'click' when a frequency is changed. I noticed the Controller's voice sounded somewhat different; but assumed there had been a controller change. At all times during the event we had visual contact with the other aircraft in the area and we did not receive a TCAS alert. Inadvertently changing an approach frequency during a critical time is an error that occurred during this event. This error led to the aircraft not being at its expected location on final approach. Fortunately; we were able to maintain visual separation with other aircraft and continue the approach uneventfully. Being that I can't determine how the frequency got changed when it did; I'm not sure there is a solution to prevent this event from happening. It's an error that could happen to anyone.

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