Narrative:

We were cleared for the ILS runway 36R at cvg and told to contact tower on 118.97 over troyf. Passing troyf (5.6 mi from runway) I switched to tower and attempted contact. No answer and no other traffic was heard. Two additional attempts were made with same results. After checking volume I went back to approach frequency. One transmission was made but got no answer. I could hear approach controller loud and clear but he must have been too busy and missed my call. I switched back to tower frequency, made one more call. Still no answer. Tried tower frequency for other runway 118.3. Again, no answer and could not hear any xmissions to other aircraft. At about 2 mi, we saw another aircraft taxi into position and begin its takeoff roll. We then began a missed approach and went back to approach control frequency and advised him of the missed approach. He instructed us to fly runway heading. We notified him of the other aircraft and that we would need a right turn as soon as possible to avoid a traffic conflict. The TCASII never set off an RA. Vectors for a second approach and landing were uneventful using communication #2, radio #2. Why the tower cleared another aircraft into position when we were inside 2 NM to runway and then cleared him for takeoff with essentially a 'no radio' aircraft rapidly closing is unbelievable! Fortunately there was adequate visibility for see and avoid. Supplemental information from acn 411784: we told the controller again of the conflict and that we were turning to 020 degrees to avoid the conflict. The controller cleared us to that heading and gave us vectors for another approach.

Google
 

Original NASA ASRS Text

Title: A B727 FLT WAS UNABLE TO COMMUNICATE WITH CVG TWR ON A 2- 5 MI FINAL. DURING THE MISSED APCH CREATED BY ANOTHER ACFT DEP ON SAME RWY, THE FLT CAME IN PROX OF THE TFC. FLC X TURNED FLT AND ESTABLISHED THE SEPARATION CRITERION.

Narrative: WE WERE CLRED FOR THE ILS RWY 36R AT CVG AND TOLD TO CONTACT TWR ON 118.97 OVER TROYF. PASSING TROYF (5.6 MI FROM RWY) I SWITCHED TO TWR AND ATTEMPTED CONTACT. NO ANSWER AND NO OTHER TFC WAS HEARD. TWO ADDITIONAL ATTEMPTS WERE MADE WITH SAME RESULTS. AFTER CHKING VOLUME I WENT BACK TO APCH FREQ. ONE XMISSION WAS MADE BUT GOT NO ANSWER. I COULD HEAR APCH CTLR LOUD AND CLR BUT HE MUST HAVE BEEN TOO BUSY AND MISSED MY CALL. I SWITCHED BACK TO TWR FREQ, MADE ONE MORE CALL. STILL NO ANSWER. TRIED TWR FREQ FOR OTHER RWY 118.3. AGAIN, NO ANSWER AND COULD NOT HEAR ANY XMISSIONS TO OTHER ACFT. AT ABOUT 2 MI, WE SAW ANOTHER ACFT TAXI INTO POS AND BEGIN ITS TKOF ROLL. WE THEN BEGAN A MISSED APCH AND WENT BACK TO APCH CTL FREQ AND ADVISED HIM OF THE MISSED APCH. HE INSTRUCTED US TO FLY RWY HEADING. WE NOTIFIED HIM OF THE OTHER ACFT AND THAT WE WOULD NEED A R TURN ASAP TO AVOID A TFC CONFLICT. THE TCASII NEVER SET OFF AN RA. VECTORS FOR A SECOND APCH AND LNDG WERE UNEVENTFUL USING COM #2, RADIO #2. WHY THE TWR CLRED ANOTHER ACFT INTO POS WHEN WE WERE INSIDE 2 NM TO RWY AND THEN CLRED HIM FOR TKOF WITH ESSENTIALLY A 'NO RADIO' ACFT RAPIDLY CLOSING IS UNBELIEVABLE! FORTUNATELY THERE WAS ADEQUATE VISIBILITY FOR SEE AND AVOID. SUPPLEMENTAL INFO FROM ACN 411784: WE TOLD THE CTLR AGAIN OF THE CONFLICT AND THAT WE WERE TURNING TO 020 DEGS TO AVOID THE CONFLICT. THE CTLR CLRED US TO THAT HEADING AND GAVE US VECTORS FOR ANOTHER APCH.

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.