Narrative:

While on descent to gsh VOR, ZAU (132.05) handed off to ZAU (120.35) who cleared us to 5000 ft. On reaching 5000 ft, communication became erratic then lost. We tried several other frequency including the sbn approach south frequency 132.05. While trying other frequency monitored 120.35. Contact was reestablished and received clearance to 3000 ft. Communication lost again and was unable to acknowledge receipt. At 3200 ft MSL we broke out of the cloud deck and proceeded to ekm and landed in compliance with far 91.185 paragraph B. Contact with terre haute FSS was established and he advised that center would like a phone call. A call was placed approximately XA55 am and center indicated that they were unaware of the fact we were on frequency 120.35 and that they used the sbn approach frequency (north sector) 118.55 at night. Also, the controller was in the process of being relieved at the time. There was no conflict and the flight was completed 'by the book.' we subsequently learned from the airport manager that he had been aroused by a call from center and asked to check the airport for the aircraft. The actions taken by center after loss of communication are to be commended. The issue of incorrect frequency seems to be getting worse. In the day or evening it is a minor matter. At night, however, it can be a real problem. In this case, had not VFR conditions been encountered, we would have had to comply with far 91.185 paragraph C. This would have been costly and would have been a tie-up for center. I have no solution except to recommend a little more precision when issuing frequency changes.

Related reports:

Google
 

Original NASA ASRS Text

Title: WRONG FREQ ASSIGNMENT LEADS TO LOST COM.

Narrative: WHILE ON DSCNT TO GSH VOR, ZAU (132.05) HANDED OFF TO ZAU (120.35) WHO CLRED US TO 5000 FT. ON REACHING 5000 FT, COM BECAME ERRATIC THEN LOST. WE TRIED SEVERAL OTHER FREQ INCLUDING THE SBN APCH S FREQ 132.05. WHILE TRYING OTHER FREQ MONITORED 120.35. CONTACT WAS REESTABLISHED AND RECEIVED CLRNC TO 3000 FT. COM LOST AGAIN AND WAS UNABLE TO ACKNOWLEDGE RECEIPT. AT 3200 FT MSL WE BROKE OUT OF THE CLOUD DECK AND PROCEEDED TO EKM AND LANDED IN COMPLIANCE WITH FAR 91.185 PARAGRAPH B. CONTACT WITH TERRE HAUTE FSS WAS ESTABLISHED AND HE ADVISED THAT CTR WOULD LIKE A PHONE CALL. A CALL WAS PLACED APPROX XA55 AM AND CTR INDICATED THAT THEY WERE UNAWARE OF THE FACT WE WERE ON FREQ 120.35 AND THAT THEY USED THE SBN APCH FREQ (N SECTOR) 118.55 AT NIGHT. ALSO, THE CTLR WAS IN THE PROCESS OF BEING RELIEVED AT THE TIME. THERE WAS NO CONFLICT AND THE FLT WAS COMPLETED 'BY THE BOOK.' WE SUBSEQUENTLY LEARNED FROM THE ARPT MGR THAT HE HAD BEEN AROUSED BY A CALL FROM CTR AND ASKED TO CHK THE ARPT FOR THE ACFT. THE ACTIONS TAKEN BY CTR AFTER LOSS OF COM ARE TO BE COMMENDED. THE ISSUE OF INCORRECT FREQ SEEMS TO BE GETTING WORSE. IN THE DAY OR EVENING IT IS A MINOR MATTER. AT NIGHT, HOWEVER, IT CAN BE A REAL PROB. IN THIS CASE, HAD NOT VFR CONDITIONS BEEN ENCOUNTERED, WE WOULD HAVE HAD TO COMPLY WITH FAR 91.185 PARAGRAPH C. THIS WOULD HAVE BEEN COSTLY AND WOULD HAVE BEEN A TIE-UP FOR CTR. I HAVE NO SOLUTION EXCEPT TO RECOMMEND A LITTLE MORE PRECISION WHEN ISSUING FREQ CHANGES.

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.