Narrative:

I was PF at 2700 ft and 8-10 NM southeast of msp cleared for ILS runway 29L approach. Land was selected on flight mode panel and I acquired a visual on an autoland system of a runway but allowed the autoplt to fly and capture localizer since we were in rain and trying to verify the correct runway visually. Autoplt did not capture localizer and we went through localizer into area north of final approach path. Hand flew back to runway 29L final visually. PNF did not get identify on runway 29L localizer after numerous attempts and we reported no identify. Tower said they had just reset the runway 29L localizer and we were then getting good raw data. No other traffic conflicts observed during overshoot.

Google
 

Original NASA ASRS Text

Title: AN F100 FLYING INTO MSP, MN, OVERSHOT THE ILS. ILS IS IN THE PROCESS OF BEING RESET AND POSITIVE IDENT OF THE ILS COULD NOT BE MADE.

Narrative: I WAS PF AT 2700 FT AND 8-10 NM SE OF MSP CLRED FOR ILS RWY 29L APCH. LAND WAS SELECTED ON FLT MODE PANEL AND I ACQUIRED A VISUAL ON AN AUTOLAND SYS OF A RWY BUT ALLOWED THE AUTOPLT TO FLY AND CAPTURE LOC SINCE WE WERE IN RAIN AND TRYING TO VERIFY THE CORRECT RWY VISUALLY. AUTOPLT DID NOT CAPTURE LOC AND WE WENT THROUGH LOC INTO AREA N OF FINAL APCH PATH. HAND FLEW BACK TO RWY 29L FINAL VISUALLY. PNF DID NOT GET IDENT ON RWY 29L LOC AFTER NUMEROUS ATTEMPTS AND WE RPTED NO IDENT. TWR SAID THEY HAD JUST RESET THE RWY 29L LOC AND WE WERE THEN GETTING GOOD RAW DATA. NO OTHER TFC CONFLICTS OBSERVED DURING OVERSHOOT.

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