B737-300 crew had a VHF communication failure in ZDC class a airspace.

Attributes
ACN	601374
Time
Date	200312
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : ric.vortac
State Reference	VA
Altitude	msl single value : 33000
Environment
Flight Conditions	IMC
Weather Elements	Snow
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc.artcc tower : roc.tower
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	cruise : level descent : vacating altitude
Route In Use	enroute airway : j25.airway
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 150 flight time total : 9500 flight time type : 6500
ASRS Report	601374
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : critical other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance controller : provided flight assist
Consequence	other other
Supplementary
Problem Areas	Aircraft
Primary Problem	Aircraft

Narrative:

At FL330, approximately 100 NM south of richmond, va, first officer noticed loss of radio communication with ZDC (118.92). We initiated troubleshooting the problem by trying center frequency on communication #2 and heard there was a stuck microphone on center frequency. It was our aircraft causing the problem. We exhausted all possible ways to correct the problem and determined we could transmit on communication #2 (118.92) and receive on communication #1 (134.02). ZDC coordinated descent clearance, until we were out of range on 118.92 frequency. I chose to select 121.5 guard frequency in communication #2, to transmit and use communication #1 center frequency to receive. I elected to squawk 7600 in the transponder and identify when given clrncs on communication #1. This communication confign was used until we landed and parked at the gate. Once on the ground, we utilized the ACARS system to send a text message to dispatch for a gate assignment and to notify maintenance.

Original NASA ASRS Text

Title: B737-300 CREW HAD A VHF COM FAILURE IN ZDC CLASS A AIRSPACE.

Narrative: AT FL330, APPROX 100 NM S OF RICHMOND, VA, FO NOTICED LOSS OF RADIO COM WITH ZDC (118.92). WE INITIATED TROUBLESHOOTING THE PROB BY TRYING CTR FREQ ON COM #2 AND HEARD THERE WAS A STUCK MIKE ON CTR FREQ. IT WAS OUR ACFT CAUSING THE PROB. WE EXHAUSTED ALL POSSIBLE WAYS TO CORRECT THE PROB AND DETERMINED WE COULD XMIT ON COM #2 (118.92) AND RECEIVE ON COM #1 (134.02). ZDC COORDINATED DSCNT CLRNC, UNTIL WE WERE OUT OF RANGE ON 118.92 FREQ. I CHOSE TO SELECT 121.5 GUARD FREQ IN COM #2, TO XMIT AND USE COM #1 CTR FREQ TO RECEIVE. I ELECTED TO SQUAWK 7600 IN THE XPONDER AND IDENT WHEN GIVEN CLRNCS ON COM #1. THIS COM CONFIGN WAS USED UNTIL WE LANDED AND PARKED AT THE GATE. ONCE ON THE GND, WE UTILIZED THE ACARS SYS TO SEND A TEXT MESSAGE TO DISPATCH FOR A GATE ASSIGNMENT AND TO NOTIFY MAINT.

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.