Narrative:

Dulles approach cleared nxxxx direct fdk (approximately 10-15 NM out) descend to 4000 ft and contact bwi approach 126.75. En route to fdk, we attempted to contact bwi approach approximately 8-10 times, using both #1 and #2 communications, headset microphone and handheld microphone with both speaker and headset. Unable to contact. Loss of communication on IFR flight! We had received AWOS for fdk approximately 35 NM out. Our ETA ok, therefore at fdk VOR we elected to start the outbound leg for ILS runway 23 at fdk. We were outbound and at 3500 ft when radio contact was finally established with baltimore. Conditions were scattered to broken. Baltimore asked if we had canceled our IFR flight plan. We advised negative, we're starting approach to fdk municipal. ATC advised there was IFR traffic cleared 3000 and eastbound. We initiated an immediate climb (1500 FPM rate) back to 4000 and asked baltimore if they wanted us to return to the VOR. ATC responded 'yes.' back en route to the VOR, scattered conditions developed. We requested cancellation of our IFR flight plan and received same. ATC requested we call supervisor on the ground. We called and talked to supervisor. We advised we had lost radio contact with baltimore approach. All personal data was furnished at approximately xaam sep/sat/93. On our return flight, we also had difficulty establishing radio contact with baltimore approach. Tried 5-6 times prior to establishing contact. Heading 090 degrees and 3000 ft altitude. Small transport Y departed fdk approximately 15-20 mins prior to small transport X and reported they also encountered difficulty establishing radio contact with baltimore 126.75. It appears there may be a 'dead area' for radio communication in the bwi approach sector. Suggest this be reviewed. Also, have dulles approach alert aircraft of potential problem with communication prior to handoff. Dulles appears to be geographically closer to fdk. Perhaps they should handle the approach to fdk municipal? Callback conversation with reporter revealed the following information: the reporting pilot states that he was 'in and out' of IMC at the time of the radio failure. He was out of radio contact about 8 mins. He did not squawk 7600, and cannot find this requirement in far 91. The reporter could not find anything wrong with his radios while on the ground at fdk. The FAA has contacted him but has made no threatening movements towards his certificate.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN SMA TWIN PLT HAD A TEMPORARY RADIO FAILURE WHILE IN IMC ON AN IFR FLT PLAN.

Narrative: DULLES APCH CLRED NXXXX DIRECT FDK (APPROX 10-15 NM OUT) DSND TO 4000 FT AND CONTACT BWI APCH 126.75. ENRTE TO FDK, WE ATTEMPTED TO CONTACT BWI APCH APPROX 8-10 TIMES, USING BOTH #1 AND #2 COMS, HEADSET MIKE AND HANDHELD MIKE WITH BOTH SPEAKER AND HEADSET. UNABLE TO CONTACT. LOSS OF COM ON IFR FLT! WE HAD RECEIVED AWOS FOR FDK APPROX 35 NM OUT. OUR ETA OK, THEREFORE AT FDK VOR WE ELECTED TO START THE OUTBOUND LEG FOR ILS RWY 23 AT FDK. WE WERE OUTBOUND AND AT 3500 FT WHEN RADIO CONTACT WAS FINALLY ESTABLISHED WITH BALTIMORE. CONDITIONS WERE SCATTERED TO BROKEN. BALTIMORE ASKED IF WE HAD CANCELED OUR IFR FLT PLAN. WE ADVISED NEGATIVE, WE'RE STARTING APCH TO FDK MUNICIPAL. ATC ADVISED THERE WAS IFR TFC CLRED 3000 AND EBOUND. WE INITIATED AN IMMEDIATE CLB (1500 FPM RATE) BACK TO 4000 AND ASKED BALTIMORE IF THEY WANTED US TO RETURN TO THE VOR. ATC RESPONDED 'YES.' BACK ENRTE TO THE VOR, SCATTERED CONDITIONS DEVELOPED. WE REQUESTED CANCELLATION OF OUR IFR FLT PLAN AND RECEIVED SAME. ATC REQUESTED WE CALL SUPVR ON THE GND. WE CALLED AND TALKED TO SUPVR. WE ADVISED WE HAD LOST RADIO CONTACT WITH BALTIMORE APCH. ALL PERSONAL DATA WAS FURNISHED AT APPROX XAAM SEP/SAT/93. ON OUR RETURN FLT, WE ALSO HAD DIFFICULTY ESTABLISHING RADIO CONTACT WITH BALTIMORE APCH. TRIED 5-6 TIMES PRIOR TO ESTABLISHING CONTACT. HDG 090 DEGS AND 3000 FT ALT. SMT Y DEPARTED FDK APPROX 15-20 MINS PRIOR TO SMT X AND RPTED THEY ALSO ENCOUNTERED DIFFICULTY ESTABLISHING RADIO CONTACT WITH BALTIMORE 126.75. IT APPEARS THERE MAY BE A 'DEAD AREA' FOR RADIO COM IN THE BWI APCH SECTOR. SUGGEST THIS BE REVIEWED. ALSO, HAVE DULLES APCH ALERT ACFT OF POTENTIAL PROB WITH COM PRIOR TO HDOF. DULLES APPEARS TO BE GEOGRAPHICALLY CLOSER TO FDK. PERHAPS THEY SHOULD HANDLE THE APCH TO FDK MUNICIPAL? CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTING PLT STATES THAT HE WAS 'IN AND OUT' OF IMC AT THE TIME OF THE RADIO FAILURE. HE WAS OUT OF RADIO CONTACT ABOUT 8 MINS. HE DID NOT SQUAWK 7600, AND CANNOT FIND THIS REQUIREMENT IN FAR 91. THE RPTR COULD NOT FIND ANYTHING WRONG WITH HIS RADIOS WHILE ON THE GND AT FDK. THE FAA HAS CONTACTED HIM BUT HAS MADE NO THREATENING MOVEMENTS TOWARDS HIS CERTIFICATE.

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.