Unauthorized uncoord runway operation at a non tower airport.

Attributes
ACN	302444
Time
Date	199504
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : frm
State Reference	MN
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	descent : approach ground other : taxi landing other
Flight Plan	None
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Beech 1900
Operating Under FAR Part	Part 135
Flight Phase	descent : approach landing : go around
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 27 flight time total : 740 flight time type : 275
ASRS Report	302444
Person 2
Affiliation	Other
Function	observation : passenger
Qualification	other other : other
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	other flight crewa other other : unspecified
Resolutory Action	none taken : detected after the fact other
Consequence	Other
Miss Distance	horizontal : 5000 vertical : 500

Narrative:

I departed frm on an evening pleasure flight with a first- time passenger and my teenage son on board. Upon returning to frm for landing, I had a sick passenger in the back seat who advised me to land as soon as practical. Approaching frm I called on 122.8, my position as '5 mi west, inbound, landing.' subsequently, I crossed over the VOR and entered a standard l-hand pattern, downwind for runway 13. No other traffic was observed in the pattern. I again advised 'downwind for runway 13' and proceeded on a normal approach for landing. My final advisory call was 'turning final for runway 13, fairmont.' after landing, I immediately executed a 180 degree turn, on the runway to exit via the nearest taxiway. After executing this turn, I observed aircraft lights from the local commuter also approaching for a landing. He pwred up and did a go around. While taxing to the hangar, I determined the cause of the radio 'problem' and called the beech 1900. I advised him, 'I did not hear any other traffic in the area because my receiver wasn't working.' I then apologized for not clearing the runway soon enough for him to land. My specific words were, 'I always yield to the airliner.' he responded, 'that's ok, I needed the go around practice anyway.' after parking the aircraft, I checked and double-checked the intercom box, wiring connections, etc, and found everything in working order. I can only surmise the volume was inadvertently turned too low for me to hear other traffic. A local pilot reported my radio xmissions sounded 'real muffled' so something was transmitting. I did not exit the runway to the side because of the extensive rainfall which made the area between the runway and taxiway too soggy to use. I also felt turning around again (another 180 degrees) turn and fast taxiing to the next exit would not have provided sufficient clearance for the beech to land either. I have now added 'check radios' to my prelndg checklist. I doubt if I will ever again try to land-short to exit via the taxiway closest to the hangars. It was this haste, coupled with the sick passenger, and the quiet radio which caused the commuter to 'go around' in the first place.

Original NASA ASRS Text

Title: UNAUTH UNCOORD RWY OP AT A NON TWR ARPT.

Narrative: I DEPARTED FRM ON AN EVENING PLEASURE FLT WITH A FIRST- TIME PAX AND MY TEENAGE SON ON BOARD. UPON RETURNING TO FRM FOR LNDG, I HAD A SICK PAX IN THE BACK SEAT WHO ADVISED ME TO LAND AS SOON AS PRACTICAL. APCHING FRM I CALLED ON 122.8, MY POS AS '5 MI W, INBOUND, LNDG.' SUBSEQUENTLY, I CROSSED OVER THE VOR AND ENTERED A STANDARD L-HAND PATTERN, DOWNWIND FOR RWY 13. NO OTHER TFC WAS OBSERVED IN THE PATTERN. I AGAIN ADVISED 'DOWNWIND FOR RWY 13' AND PROCEEDED ON A NORMAL APCH FOR LNDG. MY FINAL ADVISORY CALL WAS 'TURNING FINAL FOR RWY 13, FAIRMONT.' AFTER LNDG, I IMMEDIATELY EXECUTED A 180 DEG TURN, ON THE RWY TO EXIT VIA THE NEAREST TXWY. AFTER EXECUTING THIS TURN, I OBSERVED ACFT LIGHTS FROM THE LCL COMMUTER ALSO APCHING FOR A LNDG. HE PWRED UP AND DID A GAR. WHILE TAXING TO THE HANGAR, I DETERMINED THE CAUSE OF THE RADIO 'PROB' AND CALLED THE BEECH 1900. I ADVISED HIM, 'I DID NOT HEAR ANY OTHER TFC IN THE AREA BECAUSE MY RECEIVER WASN'T WORKING.' I THEN APOLOGIZED FOR NOT CLRING THE RWY SOON ENOUGH FOR HIM TO LAND. MY SPECIFIC WORDS WERE, 'I ALWAYS YIELD TO THE AIRLINER.' HE RESPONDED, 'THAT'S OK, I NEEDED THE GAR PRACTICE ANYWAY.' AFTER PARKING THE ACFT, I CHKED AND DOUBLE-CHKED THE INTERCOM BOX, WIRING CONNECTIONS, ETC, AND FOUND EVERYTHING IN WORKING ORDER. I CAN ONLY SURMISE THE VOLUME WAS INADVERTENTLY TURNED TOO LOW FOR ME TO HEAR OTHER TFC. A LCL PLT RPTED MY RADIO XMISSIONS SOUNDED 'REAL MUFFLED' SO SOMETHING WAS XMITTING. I DID NOT EXIT THE RWY TO THE SIDE BECAUSE OF THE EXTENSIVE RAINFALL WHICH MADE THE AREA BTWN THE RWY AND TXWY TOO SOGGY TO USE. I ALSO FELT TURNING AROUND AGAIN (ANOTHER 180 DEGS) TURN AND FAST TAXIING TO THE NEXT EXIT WOULD NOT HAVE PROVIDED SUFFICIENT CLRNC FOR THE BEECH TO LAND EITHER. I HAVE NOW ADDED 'CHK RADIOS' TO MY PRELNDG CHKLIST. I DOUBT IF I WILL EVER AGAIN TRY TO LAND-SHORT TO EXIT VIA THE TXWY CLOSEST TO THE HANGARS. IT WAS THIS HASTE, COUPLED WITH THE SICK PAX, AND THE QUIET RADIO WHICH CAUSED THE COMMUTER TO 'GAR' IN THE FIRST PLACE.

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.