Narrative:

Just west of armel we were working with ZDC when there was interference on the frequency. It appeared that somebody had a stuck microphone. The controller asked all on the frequency to come up on another frequency, which we did. After several mins the scenario repeated itself. After switching to several frequencys with the same results we realized that we must be causing the problem. We checked all of our microphone switches for the second time and tried our best to understand ATC. After being switched to cleveland center the problem again repeated itself. We were able to copy new routing: ewc radial 050 roc radial 220 to maintain FL260. Shortly after this we were unable to communicate with cle at all, nor could we receive from any frequency or either of our 3 communication radios. At this point we squawked 7700 for 1 min followed by 7600. We continued along the last assigned route at 260 and attempted contact on each frequency listed for cle center. Finally approximately 55 mi south of roc (our destination) I attempted to contact roc approach north 119.55. This attempt was successful and the controller was able to coordinate our descent and approach into roc up until now, approximately 36 hours after the incident, the reason for the failure has not been discovered and the aircraft remains on the ground. During this whole incident we realized how inadequate the lost communication procedures are. Had we not been able to contact roc approach we would have had to descend and maneuver for our approach through cle center's and roc approach's airspace with them apparently unaware of our presence, as roc and cle were quite surprised at our location. In any case it would be nice to know just how much danger we were in.

Related reports:

Google
 

Original NASA ASRS Text

Title: AIR CARRIER EXPERIENCES COM PROBLEMS IN CRUISE.

Narrative: JUST WEST OF ARMEL WE WERE WORKING WITH ZDC WHEN THERE WAS INTERFERENCE ON THE FREQ. IT APPEARED THAT SOMEBODY HAD A STUCK MIKE. THE CTLR ASKED ALL ON THE FREQ TO COME UP ON ANOTHER FREQ, WHICH WE DID. AFTER SEVERAL MINS THE SCENARIO REPEATED ITSELF. AFTER SWITCHING TO SEVERAL FREQS WITH THE SAME RESULTS WE REALIZED THAT WE MUST BE CAUSING THE PROBLEM. WE CHECKED ALL OF OUR MIKE SWITCHES FOR THE SECOND TIME AND TRIED OUR BEST TO UNDERSTAND ATC. AFTER BEING SWITCHED TO CLEVELAND CENTER THE PROBLEM AGAIN REPEATED ITSELF. WE WERE ABLE TO COPY NEW ROUTING: EWC RADIAL 050 ROC RADIAL 220 TO MAINTAIN FL260. SHORTLY AFTER THIS WE WERE UNABLE TO COMMUNICATE WITH CLE AT ALL, NOR COULD WE RECEIVE FROM ANY FREQ OR EITHER OF OUR 3 COMMUNICATION RADIOS. AT THIS POINT WE SQUAWKED 7700 FOR 1 MIN FOLLOWED BY 7600. WE CONTINUED ALONG THE LAST ASSIGNED ROUTE AT 260 AND ATTEMPTED CONTACT ON EACH FREQ LISTED FOR CLE CENTER. FINALLY APPROX 55 MI S OF ROC (OUR DEST) I ATTEMPTED TO CONTACT ROC APCH N 119.55. THIS ATTEMPT WAS SUCCESSFUL AND THE CTLR WAS ABLE TO COORDINATE OUR DSCNT AND APCH INTO ROC UP UNTIL NOW, APPROX 36 HRS AFTER THE INCIDENT, THE REASON FOR THE FAILURE HAS NOT BEEN DISCOVERED AND THE ACFT REMAINS ON THE GND. DURING THIS WHOLE INCIDENT WE REALIZED HOW INADEQUATE THE LOST COMMUNICATION PROCS ARE. HAD WE NOT BEEN ABLE TO CONTACT ROC APCH WE WOULD HAVE HAD TO DSND AND MANEUVER FOR OUR APCH THROUGH CLE CENTER'S AND ROC APCH'S AIRSPACE WITH THEM APPARENTLY UNAWARE OF OUR PRESENCE, AS ROC AND CLE WERE QUITE SURPRISED AT OUR LOCATION. IN ANY CASE IT WOULD BE NICE TO KNOW JUST HOW MUCH DANGER WE WERE IN.

Data retrieved from NASA's ASRS site as of August 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.