Crj-200 flight crew reported difficulty intercepting the ord runway 27R localizer due to a misprogra...

Attributes
ACN	1417880
Time
Date	201701
Local Time Of Day	0601-1200
Place
Locale Reference	ORD.Airport
State Reference	IL
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Vectors STAR PAITN4
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

We were on the PAITN4 arrival into ord and had just received a vector to intercept the localizer to 27R. I noticed that we did not have preview needles; so I knew that something wasn't right. So I started by checking to see how far away from the airport we were. We were within 30 miles; approximately 27NM from the runway. So I asked the first officer to switch to green needles after verifying we had the correct frequency 111.75 set as the active frequency in navigation 1 and 2. Once he switched to green needles it was too late. We had already gone through the localizer course and had entered the arrival corridor for 27L. At this point I checked to see which approach was loaded in the FMS. It was the ILS to 27L. We started to correct back to the 27R course at which point the ATC controller told us to turn to 290 degrees to reintercept the localizer. A few seconds later she informed us that the localizer was out of service. The first officer at this point claimed that he could not hear the morse code on NAV2 to identify the localizer. We got vectored back into sequence and flew the RNAV/GPS to 27R without any event or risk of conflicting with other traffic.

Original NASA ASRS Text

Title: CRJ-200 flight crew reported difficulty intercepting the ORD Runway 27R localizer due to a misprogrammed FMS. At the same moment; an issue with the airport's ILS system prevented them from reintercepting the localizer.

Narrative: We were on the PAITN4 arrival into ORD and had just received a vector to intercept the LOC to 27R. I noticed that we did not have preview needles; so I knew that something wasn't right. So I started by checking to see how far away from the airport we were. We were within 30 miles; approximately 27NM from the runway. So I asked the FO to switch to green needles after verifying we had the correct frequency 111.75 set as the active frequency in NAV 1 and 2. Once he switched to green needles it was too late. We had already gone through the localizer course and had entered the arrival corridor for 27L. At this point I checked to see which approach was loaded in the FMS. It was the ILS to 27L. We started to correct back to the 27R course at which point the ATC controller told us to turn to 290 degrees to reintercept the localizer. A few seconds later she informed us that the localizer was out of service. The FO at this point claimed that he could not hear the Morse code on NAV2 to identify the localizer. We got vectored back into sequence and flew the RNAV/GPS to 27R without any event or risk of conflicting with other traffic.

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.

Crj-200 flight crew reported difficulty intercepting the ord runway 27R localizer due to a misprogrammed FMS. At the same moment; an issue with the airport's ILS system prevented them from reintercepting the localizer.