Narrative:

I was captain (PNF). We were tracking inbound on runway 27L localizer to ord. Had been on localizer for 50 mi out coming from azo. Approximately 15 NM from the field TCASII issued TA. We immediately saw the traffic. When we initially saw the beech, it was out the right front of our windscreen (2 O'clock position), coming from the north and in a right turn, which would be normal for them to join runway 27R localizer. We both assumed the other aircraft was joining runway 27R localizer. Our aircraft was established on the course, centered. TCASII then issued RA to reduce descent. We had good visual on the traffic and continued the normal descent profile. TCASII then issued climb RA. At this point we realized the beech 1900 was joining (apparently) runway 27L localizer. I suggested the first officer come left to give room to other aircraft. As we moved left, we also passed the beech and at that time they saw us and moved back to the runway 27R localizer. After we landed, my first officer walked over to talk with the other crew. They told him they thought they were cleared on the runway 27L localizer. They also told him their TCASII was MEL'ed OTS. There is no substitute for the old axiom 'see and avoid.' supplemental information from acn 396719: approach said to expect runway 27L when we checked on. The next approach controller then gave us a descent and to call the field in sight if able. We called the field in sight and were given a visual approach clearance. While lining up on runway 27L we noticed a saab 340 off our left wingtip. Approach then questioned if we had runway 27R in sight and if we were lined up for it. When we responded that we were lining up on runway 27L he told us to turn right to 310 degrees and line up for the visual to runway 27R. The saab had to take corrective action to the left and then reline up on runway 27L for the visual landing. At the time our TCASII was MEL'ed and we kept looking for traffic only to our right while keeping the airport in sight.

Google
 

Original NASA ASRS Text

Title: AN SF340 AND A BE02 COME CLOSE TOGETHER DURING AN APCH TO ORD, IL. THE SF340 IS FLYING ILS TO RWY 27L AND THE BE02 OVERSHOT THE ILS TO RWY 27R AND CONVERGES CLOSE TO THE SF340.

Narrative: I WAS CAPT (PNF). WE WERE TRACKING INBOUND ON RWY 27L LOC TO ORD. HAD BEEN ON LOC FOR 50 MI OUT COMING FROM AZO. APPROX 15 NM FROM THE FIELD TCASII ISSUED TA. WE IMMEDIATELY SAW THE TFC. WHEN WE INITIALLY SAW THE BEECH, IT WAS OUT THE R FRONT OF OUR WINDSCREEN (2 O'CLOCK POS), COMING FROM THE N AND IN A R TURN, WHICH WOULD BE NORMAL FOR THEM TO JOIN RWY 27R LOC. WE BOTH ASSUMED THE OTHER ACFT WAS JOINING RWY 27R LOC. OUR ACFT WAS ESTABLISHED ON THE COURSE, CTRED. TCASII THEN ISSUED RA TO REDUCE DSCNT. WE HAD GOOD VISUAL ON THE TFC AND CONTINUED THE NORMAL DSCNT PROFILE. TCASII THEN ISSUED CLB RA. AT THIS POINT WE REALIZED THE BEECH 1900 WAS JOINING (APPARENTLY) RWY 27L LOC. I SUGGESTED THE FO COME L TO GIVE ROOM TO OTHER ACFT. AS WE MOVED L, WE ALSO PASSED THE BEECH AND AT THAT TIME THEY SAW US AND MOVED BACK TO THE RWY 27R LOC. AFTER WE LANDED, MY FO WALKED OVER TO TALK WITH THE OTHER CREW. THEY TOLD HIM THEY THOUGHT THEY WERE CLRED ON THE RWY 27L LOC. THEY ALSO TOLD HIM THEIR TCASII WAS MEL'ED OTS. THERE IS NO SUBSTITUTE FOR THE OLD AXIOM 'SEE AND AVOID.' SUPPLEMENTAL INFO FROM ACN 396719: APCH SAID TO EXPECT RWY 27L WHEN WE CHKED ON. THE NEXT APCH CTLR THEN GAVE US A DSCNT AND TO CALL THE FIELD IN SIGHT IF ABLE. WE CALLED THE FIELD IN SIGHT AND WERE GIVEN A VISUAL APCH CLRNC. WHILE LINING UP ON RWY 27L WE NOTICED A SAAB 340 OFF OUR L WINGTIP. APCH THEN QUESTIONED IF WE HAD RWY 27R IN SIGHT AND IF WE WERE LINED UP FOR IT. WHEN WE RESPONDED THAT WE WERE LINING UP ON RWY 27L HE TOLD US TO TURN R TO 310 DEGS AND LINE UP FOR THE VISUAL TO RWY 27R. THE SAAB HAD TO TAKE CORRECTIVE ACTION TO THE L AND THEN RELINE UP ON RWY 27L FOR THE VISUAL LNDG. AT THE TIME OUR TCASII WAS MEL'ED AND WE KEPT LOOKING FOR TFC ONLY TO OUR R WHILE KEEPING THE ARPT IN SIGHT.

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.