Light twin pilot reports inability to communicate with huron FSS on the ground at ykn after initiall...

Narrative:

I had filed an IFR clearance from ykn to sux using duats. When ready for departure I contacted huron FSS and requested my clearance to depart runway 13. A minute or 2 later; FSS responded 'aircraft X clearance.' I responded several times using both transmitters 'aircraft X ready to copy' but received no response from FSS. While the AWOS was reporting visibility less than 1 mi; the fog that morning was very spotty. The departure end of runway 13 was completely clear and I had more than 1 mi visibility down the runway. I elected to depart VFR and was able to complete the flight from ykn to sux in VFR conditions. Nearing the sux airspace I had listened to ATIS and was tuned to sux approach when I heard sux approach contact me with 'aircraft X identify.' it was then I wondered if the airspace was being held open for me even though I had not received an IFR clearance. While no rules were violated; and no safety of flight issues were encountered; poor communication capabilities with FSS potentially caused some confusion. There have been several instances when I have been unable to contact FSS at the ykn airport on the appropriate frequency 122.55. I do not know if the new FSS arrangement is at fault of if it is an equipment problem at ykn. Adequate communication facilities need to be in place and maintained to provide for the necessary communication with control facilities.

Original NASA ASRS Text

Title: LIGHT TWIN PILOT REPORTS INABILITY TO COMMUNICATE WITH HURON FSS ON THE GROUND AT YKN AFTER INITIALLY MAKING CONTACT.

Narrative: I HAD FILED AN IFR CLRNC FROM YKN TO SUX USING DUATS. WHEN READY FOR DEP I CONTACTED HURON FSS AND REQUESTED MY CLRNC TO DEPART RWY 13. A MINUTE OR 2 LATER; FSS RESPONDED 'ACFT X CLRNC.' I RESPONDED SEVERAL TIMES USING BOTH XMITTERS 'ACFT X READY TO COPY' BUT RECEIVED NO RESPONSE FROM FSS. WHILE THE AWOS WAS RPTING VISIBILITY LESS THAN 1 MI; THE FOG THAT MORNING WAS VERY SPOTTY. THE DEP END OF RWY 13 WAS COMPLETELY CLR AND I HAD MORE THAN 1 MI VISIBILITY DOWN THE RWY. I ELECTED TO DEPART VFR AND WAS ABLE TO COMPLETE THE FLT FROM YKN TO SUX IN VFR CONDITIONS. NEARING THE SUX AIRSPACE I HAD LISTENED TO ATIS AND WAS TUNED TO SUX APCH WHEN I HEARD SUX APCH CONTACT ME WITH 'ACFT X IDENT.' IT WAS THEN I WONDERED IF THE AIRSPACE WAS BEING HELD OPEN FOR ME EVEN THOUGH I HAD NOT RECEIVED AN IFR CLRNC. WHILE NO RULES WERE VIOLATED; AND NO SAFETY OF FLT ISSUES WERE ENCOUNTERED; POOR COM CAPABILITIES WITH FSS POTENTIALLY CAUSED SOME CONFUSION. THERE HAVE BEEN SEVERAL INSTANCES WHEN I HAVE BEEN UNABLE TO CONTACT FSS AT THE YKN ARPT ON THE APPROPRIATE FREQ 122.55. I DO NOT KNOW IF THE NEW FSS ARRANGEMENT IS AT FAULT OF IF IT IS AN EQUIP PROB AT YKN. ADEQUATE COM FACILITIES NEED TO BE IN PLACE AND MAINTAINED TO PROVIDE FOR THE NECESSARY COM WITH CTL FACILITIES.

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

Attributes
ACN	781743
Time
Date	200804
Place
Locale Reference	airport : ykn.airport
State Reference	SD
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Small Transport Low Wing 2 Recip Eng
Operating Under FAR Part	Part 91
Flight Phase	ground : preflight ground : parked
Flight Plan	IFR
Person 1
Affiliation	other
Qualification	pilot : atp
Experience	flight time last 90 days : 20 flight time total : 9000 flight time type : 4000
ASRS Report	781743
Events
Anomaly	non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	ATC Facility
Primary Problem	ATC Facility

Light twin pilot reports inability to communicate with huron FSS on the ground at ykn after initially making contact.