Narrative:

We were southeast of ind on a radar vector to okk (109.8). ZID issued a clearance to cross 40 south of okk at FL280. At our position, okk (109.8) conflicts with cct (109.8) central city to the south. My first VOR lock on pointed to cct. By the time we had a good lock on okk, we were too close to make the restriction 40 south of okk at FL280. We told the controller and she reissued the clearance to FL280 without the 40 NM restriction. As a pilot, if I do not have a strong NAVAID, or conflict exists, I will immediately ask my DME from referenced VOR. Improving the strength of okk or change okk or cct if they are both 109.8 and too close together. No conflict existed on TCASII or from ATC.

Google
 

Original NASA ASRS Text

Title: AN ACR MLG AT FL350 HAD A FREQ PROBLEM WITH OKK AND CCT, BOTH 109 PT 8. A XING ALT WAS MISSED BECAUSE OF THIS.

Narrative: WE WERE SE OF IND ON A RADAR VECTOR TO OKK (109.8). ZID ISSUED A CLRNC TO CROSS 40 S OF OKK AT FL280. AT OUR POS, OKK (109.8) CONFLICTS WITH CCT (109.8) CENTRAL CITY TO THE S. MY FIRST VOR LOCK ON POINTED TO CCT. BY THE TIME WE HAD A GOOD LOCK ON OKK, WE WERE TOO CLOSE TO MAKE THE RESTRICTION 40 S OF OKK AT FL280. WE TOLD THE CTLR AND SHE REISSUED THE CLRNC TO FL280 WITHOUT THE 40 NM RESTRICTION. AS A PLT, IF I DO NOT HAVE A STRONG NAVAID, OR CONFLICT EXISTS, I WILL IMMEDIATELY ASK MY DME FROM REFED VOR. IMPROVING THE STRENGTH OF OKK OR CHANGE OKK OR CCT IF THEY ARE BOTH 109.8 AND TOO CLOSE TOGETHER. NO CONFLICT EXISTED ON TCASII OR FROM ATC.

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.