Narrative:

Upon arrival into ZZZ; we got the current ATIS. The ATIS was indicating that ZZZ was landing south and to expect visual approach to runway xx. There was no NOTAM or indication on ATIS that the localizer for runway xx was not in service. As pilot flying; I briefed a visual approach to runway xx with ILS back up for course and vertical guidance. ILS for runway xx was selected and checked. We were cleared for the visual and asked to keep within 5 miles if able. I configured the aircraft on a base leg and planned to intercept the visual final over zzzzz; which is 5.0 miles on the final. On the base to final turn; I noticed that the glide slope did not look correct as it was showing I was well below. I immediately looked at the identification (identifier) and noticed it was indicating ifbs and should have been ixna. I instructed the first officer to turn off the flight directors and bring up fpv (flight path vector). We intercepted a visual final and landed normally; however; the glide slope warning was sounding throughout the approach as it was the incorrect glide slope. After parking at the gate; I asked tower if the localizer for runway xx was not in service. I was told that they had not got around to switching it; as they were using runway xy earlier in the day. The identifier for ILS xy is ifbs.the localizer frequency was broadcasting for the non-landing runway without any notification on ATIS or advisory from ATC. It might be worth informing ATC at ZZZ that many airlines use ILS as a backup to visual approaches and this causes incorrect indications that can cause confusion. Also; broadcasting a localizer frequency and course on the same runway in the opposite direction of landing traffic is concerning from a safety aspect in my opinion.

Google
 

Original NASA ASRS Text

Title: A319 flight crew reported airport broadcast incorrect Instrument Landing System identifier.

Narrative: Upon arrival into ZZZ; we got the current ATIS. The ATIS was indicating that ZZZ was landing south and to expect visual approach to Runway XX. There was no NOTAM or indication on ATIS that the localizer for Runway XX was not in service. As Pilot Flying; I briefed a visual approach to Runway XX with ILS back up for course and vertical guidance. ILS for Runway XX was selected and checked. We were cleared for the visual and asked to keep within 5 miles if able. I configured the aircraft on a base leg and planned to intercept the visual final over ZZZZZ; which is 5.0 miles on the final. On the base to final turn; I noticed that the glide slope did not look correct as it was showing I was well below. I immediately looked at the ID (Identifier) and noticed it was indicating IFBS and should have been IXNA. I instructed the First Officer to turn off the flight directors and bring up FPV (Flight Path Vector). We intercepted a visual final and landed normally; however; the glide slope warning was sounding throughout the approach as it was the incorrect glide slope. After parking at the gate; I asked Tower if the localizer for Runway XX was not in service. I was told that they had not got around to switching it; as they were using Runway XY earlier in the day. The Identifier for ILS XY is IFBS.The localizer frequency was broadcasting for the non-landing runway without any notification on ATIS or advisory from ATC. It might be worth informing ATC at ZZZ that many airlines use ILS as a backup to visual approaches and this causes incorrect indications that can cause confusion. Also; broadcasting a localizer frequency and course on the same runway in the opposite direction of landing traffic is concerning from a safety aspect in my opinion.

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