Pilot of a beech king air BE90 lost radio communication and declared an emergency for loss of radio ...

Attributes
ACN	426319
Time
Date	199901
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : apa
State Reference	CO
Altitude	msl bound lower : 7000 msl bound upper : 7000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	general aviation : corporate
Flight Plan	None
Aircraft 2
Flight Phase	descent : approach
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : flight engineer
Experience	flight time last 90 days : 25 flight time total : 3100 flight time type : 55
ASRS Report	426319
Person 2
Function	flight crew : single pilot
Events
Anomaly	aircraft equipment problem : critical conflict : nmac other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified other flight crewa
Resolutory Action	flight crew : declared emergency other
Consequence	faa : reviewed incident with flight crew Other
Miss Distance	horizontal : 300 vertical : 0
Supplementary
Air Traffic Incident	other

Narrative:

On radar vectors for ILS runway 35L at cos, when communications were lost. I was on a heading for pike's peak below the summit at night. I squawked 7700 for 1 min while turning away from the mountain and towards home -- apa. After 1 min, I changed squawk to 7600 for the duration of the flight. I transmitted in the blind my intent to fly the ILS runway 35R at apa. Radio reception was intermittent but at one point I heard cos approach ask if I wanted the equipment standing by at apa. I responded 'negative.' inbound to the LOM/IAF (casse) at 35 NM, I broadcast my intent on apa tower frequency (118.9) to fly the ILS. Every 5 NM thereafter, I broadcast my position. Inside the marker another aircraft descended in front of me on the ILS. I estimate the distance at 300 ft or less. I sidestepped to the left for separation. At that point, tower transmitted 'king air aircraft X, if you read, don't key your microphone, turn left 15 degrees.' I complied. Tower then transmitted 'do not key your microphone, if you read, flash your landing lights.' I complied. I was then cleared to land on runway 35L. Airport security followed me to parking and asked me to call the tower. Tower said the 7600 was great because they knew exactly my problem. They then asked that in the future, should this happen again, I not 'clog up the final approach' but instead make a visual entry and look for light signals on downwind. I would be happy to comply in the daylight but not on a dark night. Since the tower was aware of my situation and that I had declared an emergency, I believe tower should have given me priority to land rather than clearing another aircraft to fly the same approach I was flying. Next day, troubleshooting showed an intermittent sticking microphone switch. I was able to transmit but the switch would stick for 30-40 seconds and I would not receive the response. The switch would then unstick and I would hear other radio traffic. Very confusing!

Original NASA ASRS Text

Title: PLT OF A BEECH KING AIR BE90 LOST RADIO COM AND DECLARED AN EMER FOR LOSS OF RADIO COMS, BUT ANNOUNCED HIS INTENTIONS AS TO RETURN TO HOME BASE. DURING FINAL AT HOME BASE HE HAD NMAC WITH ANOTHER KING AIR ON FINAL APCH.

Narrative: ON RADAR VECTORS FOR ILS RWY 35L AT COS, WHEN COMS WERE LOST. I WAS ON A HDG FOR PIKE'S PEAK BELOW THE SUMMIT AT NIGHT. I SQUAWKED 7700 FOR 1 MIN WHILE TURNING AWAY FROM THE MOUNTAIN AND TOWARDS HOME -- APA. AFTER 1 MIN, I CHANGED SQUAWK TO 7600 FOR THE DURATION OF THE FLT. I XMITTED IN THE BLIND MY INTENT TO FLY THE ILS RWY 35R AT APA. RADIO RECEPTION WAS INTERMITTENT BUT AT ONE POINT I HEARD COS APCH ASK IF I WANTED THE EQUIP STANDING BY AT APA. I RESPONDED 'NEGATIVE.' INBOUND TO THE LOM/IAF (CASSE) AT 35 NM, I BROADCAST MY INTENT ON APA TWR FREQ (118.9) TO FLY THE ILS. EVERY 5 NM THEREAFTER, I BROADCAST MY POS. INSIDE THE MARKER ANOTHER ACFT DSNDED IN FRONT OF ME ON THE ILS. I ESTIMATE THE DISTANCE AT 300 FT OR LESS. I SIDESTEPPED TO THE L FOR SEPARATION. AT THAT POINT, TWR XMITTED 'KING AIR ACFT X, IF YOU READ, DON'T KEY YOUR MIKE, TURN L 15 DEGS.' I COMPLIED. TWR THEN XMITTED 'DO NOT KEY YOUR MIKE, IF YOU READ, FLASH YOUR LNDG LIGHTS.' I COMPLIED. I WAS THEN CLRED TO LAND ON RWY 35L. ARPT SECURITY FOLLOWED ME TO PARKING AND ASKED ME TO CALL THE TWR. TWR SAID THE 7600 WAS GREAT BECAUSE THEY KNEW EXACTLY MY PROB. THEY THEN ASKED THAT IN THE FUTURE, SHOULD THIS HAPPEN AGAIN, I NOT 'CLOG UP THE FINAL APCH' BUT INSTEAD MAKE A VISUAL ENTRY AND LOOK FOR LIGHT SIGNALS ON DOWNWIND. I WOULD BE HAPPY TO COMPLY IN THE DAYLIGHT BUT NOT ON A DARK NIGHT. SINCE THE TWR WAS AWARE OF MY SIT AND THAT I HAD DECLARED AN EMER, I BELIEVE TWR SHOULD HAVE GIVEN ME PRIORITY TO LAND RATHER THAN CLRING ANOTHER ACFT TO FLY THE SAME APCH I WAS FLYING. NEXT DAY, TROUBLESHOOTING SHOWED AN INTERMITTENT STICKING MIKE SWITCH. I WAS ABLE TO XMIT BUT THE SWITCH WOULD STICK FOR 30-40 SECONDS AND I WOULD NOT RECEIVE THE RESPONSE. THE SWITCH WOULD THEN UNSTICK AND I WOULD HEAR OTHER RADIO TFC. VERY CONFUSING!

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.

Pilot of a beech king air BE90 lost radio communication and declared an emergency for loss of radio communications, but announced his intentions as to return to home base. During final at home base he had near midair collision with another king air on final approach.