Narrative:

I just took over the position and the previous controller took a pointout on an airplane wbound at 4000 ft. He failed to inform me of this during the position briefing. I cleared airplane X for the ILS approach to maintain 2600 ft until established on the localizer. Aircraft Y was supposed to be over kedzi OM on a wbound heading but was at cadon OM on a 250 degree heading. Aircraft X did not descend to 2600 ft and flew the GS and was at cadon at 4000 ft. I noticed the traffic conflict and called traffic and tried to descend aircraft X. I could not turn aircraft X because of another aircraft on base leg for runway 4R. Aircraft X did not see aircraft Y when traffic was pointed out and separation was lost.

Google
 

Original NASA ASRS Text

Title: C90 CTLR DOES NOT RECOGNIZE POTENTIAL CONFLICT BTWN AND ENRTE BE58 AND A JS31 ON APCH TO MDW UNTIL CONFLICT ALERT ACTIVATES.

Narrative: I JUST TOOK OVER THE POS AND THE PREVIOUS CTLR TOOK A POINTOUT ON AN AIRPLANE WBOUND AT 4000 FT. HE FAILED TO INFORM ME OF THIS DURING THE POS BRIEFING. I CLRED AIRPLANE X FOR THE ILS APCH TO MAINTAIN 2600 FT UNTIL ESTABLISHED ON THE LOC. ACFT Y WAS SUPPOSED TO BE OVER KEDZI OM ON A WBOUND HDG BUT WAS AT CADON OM ON A 250 DEG HDG. ACFT X DID NOT DSND TO 2600 FT AND FLEW THE GS AND WAS AT CADON AT 4000 FT. I NOTICED THE TFC CONFLICT AND CALLED TFC AND TRIED TO DSND ACFT X. I COULD NOT TURN ACFT X BECAUSE OF ANOTHER ACFT ON BASE LEG FOR RWY 4R. ACFT X DID NOT SEE ACFT Y WHEN TFC WAS POINTED OUT AND SEPARATION WAS LOST.

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.