Radio communication problem - GA pilots were experiencing radio difficulties during the flight.

Attributes
ACN	298070
Time
Date	199503
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : vla airport : stl
State Reference	MO
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : stl
Operator	general aviation : instructional
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Route In Use	arrival other arrival star : star
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : instrument pilot : commercial
Experience	flight time last 90 days : 150 flight time total : 12000 flight time type : 2000
ASRS Report	298070
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	aircraft equipment problem : less severe non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : overcame equipment problem
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

During our flight from dupage to st louis, we were experiencing radio problems. Both receivers were weak (short range) and scratchy. After becoming established on the vandalia arrival for landing on runway 12R at st louis, we realized that the radios had been rather quiet. Pressing the 'test' button, we heard approach control calling our aircraft #. From the tone in the controller's voice, it was apparent that he had been trying to reach us. We were told to turn 20 degrees left to rejoin the transition. Both of our navigation radios, which had a current VOR check and appeared to be working properly, indicated we were within 1 degree of course centerline. Because of our poor radios and the high workload, both for the controller and in the cockpit, we did not determine exactly how far off course the controller thought we were, or if he had to move other traffic to avoid a conflict because of our temporary loss of communication. After landing, we had avionics check the radios and it was determined that the cause of our problem was a poor ground connection on our lower rotating beacon.

Original NASA ASRS Text

Title: RADIO COM PROB - GA PLTS WERE EXPERIENCING RADIO DIFFICULTIES DURING THE FLT.

Narrative: DURING OUR FLT FROM DUPAGE TO ST LOUIS, WE WERE EXPERIENCING RADIO PROBS. BOTH RECEIVERS WERE WEAK (SHORT RANGE) AND SCRATCHY. AFTER BECOMING ESTABLISHED ON THE VANDALIA ARR FOR LNDG ON RWY 12R AT ST LOUIS, WE REALIZED THAT THE RADIOS HAD BEEN RATHER QUIET. PRESSING THE 'TEST' BUTTON, WE HEARD APCH CTL CALLING OUR ACFT #. FROM THE TONE IN THE CTLR'S VOICE, IT WAS APPARENT THAT HE HAD BEEN TRYING TO REACH US. WE WERE TOLD TO TURN 20 DEGS L TO REJOIN THE TRANSITION. BOTH OF OUR NAV RADIOS, WHICH HAD A CURRENT VOR CHK AND APPEARED TO BE WORKING PROPERLY, INDICATED WE WERE WITHIN 1 DEG OF COURSE CTRLINE. BECAUSE OF OUR POOR RADIOS AND THE HIGH WORKLOAD, BOTH FOR THE CTLR AND IN THE COCKPIT, WE DID NOT DETERMINE EXACTLY HOW FAR OFF COURSE THE CTLR THOUGHT WE WERE, OR IF HE HAD TO MOVE OTHER TFC TO AVOID A CONFLICT BECAUSE OF OUR TEMPORARY LOSS OF COM. AFTER LNDG, WE HAD AVIONICS CHK THE RADIOS AND IT WAS DETERMINED THAT THE CAUSE OF OUR PROB WAS A POOR GND CONNECTION ON OUR LOWER ROTATING BEACON.

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.