Narrative:

Deviated from localizer on runway 25R ILS approach. During the before landing checklist on radios and displays check; both pilots noted that the identifier for runway 25R was wrong. It indicates iias and chart dated 2009 showed icfn. We were on runway 25R due to priority handling for a medical emergency and as we approached fogla; the aircraft made an uncommanded right turn. Approach was armed and at that time we should have captured the localizer; aircraft began a right turn. We immediately began a correction back to the localizer and were simultaneously called by lax approach and given a heading. We reported the faulty identify and opted to continue using LNAV guidance as we were beginning to pick up the airport visually. We both verified that 111.10 was dialed into the control heads and had previously confirmed the morse code signals were consistent with the incorrect identify displayed. This caused us to be a little high on the approach and did not stabilize until 500 ft. Picked up airport visually at approximately 2 miles and landed without incident. The ATIS Y had reported runway 25R as being closed and when we questioned ATC; they advised that it had just reopened and wanted us on runway 25R. Lax facilities need to verify operation of runway 25R localizer when ILS 25R approach is in use! We received an incorrect identify on approach and suspect that this caused an uncommanded turn. Once we were approaching the gate I noticed that icfn was back on the display. It appears that during the runway closure; runway 7L ILS was activated and not reverted to runway 25R. Iias is the identify for runway 7L.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737 pilot reported that they were cleared for an approach to LAX Runway 25R which had been shutdown but was reopened for their approach. However; the 7L ILS was still active and the aircraft deviated as it attempted to capture an incorrect final approach path.

Narrative: Deviated from localizer on Runway 25R ILS approach. During the Before Landing Checklist on radios and displays check; both pilots noted that the identifier for Runway 25R was wrong. It indicates IIAS and chart dated 2009 showed ICFN. We were on Runway 25R due to priority handling for a medical emergency and as we approached FOGLA; the aircraft made an uncommanded right turn. Approach was armed and at that time we should have captured the localizer; aircraft began a right turn. We immediately began a correction back to the localizer and were simultaneously called by LAX Approach and given a heading. We reported the faulty IDENT and opted to continue using LNAV guidance as we were beginning to pick up the airport visually. We both verified that 111.10 was dialed into the control heads and had previously confirmed the Morse code signals were consistent with the incorrect IDENT displayed. This caused us to be a little high on the approach and did not stabilize until 500 FT. Picked up airport visually at approximately 2 miles and landed without incident. The ATIS Y had reported Runway 25R as being closed and when we questioned ATC; they advised that it had just reopened and wanted us on Runway 25R. LAX facilities need to verify operation of Runway 25R localizer when ILS 25R approach is in use! We received an incorrect IDENT on approach and suspect that this caused an uncommanded turn. Once we were approaching the gate I noticed that ICFN was back on the display. It appears that during the runway closure; Runway 7L ILS was activated and not reverted to Runway 25R. IIAS is the IDENT for Runway 7L.

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.