|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||atc facility : zhu.artcc|
|Altitude||msl bound lower : 12000|
msl bound upper : 16000
|Controlling Facilities||artcc : zhu.artcc|
|Operator||common carrier : air carrier|
|Make Model Name||Canadair/Bombardier Undifferentiated or Other Model|
|Operating Under FAR Part||Part 121|
|Flight Phase||descent : intermediate altitude|
|Affiliation||government : faa|
|Function||controller : radar|
|Qualification||controller : radar|
|Experience||controller radar : 16|
|Anomaly||other anomaly other|
|Independent Detector||other controllera|
|Resolutory Action||none taken : anomaly accepted|
|Problem Areas||Navigational Facility|
|Primary Problem||Navigational Facility|
Air carrier Y was descending into crp. I had issued a pilot's discretion descent and amended it to a descend-and-maintain descent because of control instructions I had received from another controller to clear an air carrier Y jet around thunderstorms. I climbed the air carrier Y and turned him head-on with air carrier X. I issued a descent clearance to air carrier X and saw the frequency lights on the vscs illuminate; but received no response. I called again with no response; so I turned air carrier Y into the thunderstorm and keyed and unkeyed my microphone quickly. This action had worked in the past and worked at this time. I got the readback from air carrier X and returned air carrier Y to the WX avoidance course. I reported the issue to the supervisor who called the communication technician. The communication technician acted like it was the first time he had heard of the issue. It has been an ongoing issue for over 8 months. The communication technician then told the supervisor that the problem was caused by the controller -- meaning that I had diversity algorithm on and only 1 frequency selected. This was not the case; but allows them to close out the issue without action. Our frequency problems at ZHU affect several sectors and will; without a doubt; cause an accident. I have been a controller for over 16 yrs and this is the most frightening situation that I have ever seen. 128.15; 126.1; 133.75; 132.8; and 127.8 are all malfunctioning. When reported to the supervisors; the issues are ignored.
Original NASA ASRS Text
Title: ZHU CTLR VOICED CONCERN REGARDING ONGOING FREQ PROBLEMS; CITING VSCS AS INDICATING RECEPTION INPUT; BUT NOTHING RECEIVED BY THE CTLR.
Narrative: ACR Y WAS DSNDING INTO CRP. I HAD ISSUED A PLT'S DISCRETION DSCNT AND AMENDED IT TO A DSND-AND-MAINTAIN DSCNT BECAUSE OF CTL INSTRUCTIONS I HAD RECEIVED FROM ANOTHER CTLR TO CLR AN ACR Y JET AROUND TSTMS. I CLBED THE ACR Y AND TURNED HIM HEAD-ON WITH ACR X. I ISSUED A DSCNT CLRNC TO ACR X AND SAW THE FREQ LIGHTS ON THE VSCS ILLUMINATE; BUT RECEIVED NO RESPONSE. I CALLED AGAIN WITH NO RESPONSE; SO I TURNED ACR Y INTO THE TSTM AND KEYED AND UNKEYED MY MIKE QUICKLY. THIS ACTION HAD WORKED IN THE PAST AND WORKED AT THIS TIME. I GOT THE READBACK FROM ACR X AND RETURNED ACR Y TO THE WX AVOIDANCE COURSE. I RPTED THE ISSUE TO THE SUPVR WHO CALLED THE COM TECHNICIAN. THE COM TECHNICIAN ACTED LIKE IT WAS THE FIRST TIME HE HAD HEARD OF THE ISSUE. IT HAS BEEN AN ONGOING ISSUE FOR OVER 8 MONTHS. THE COM TECHNICIAN THEN TOLD THE SUPVR THAT THE PROB WAS CAUSED BY THE CTLR -- MEANING THAT I HAD DIVERSITY ALGORITHM ON AND ONLY 1 FREQ SELECTED. THIS WAS NOT THE CASE; BUT ALLOWS THEM TO CLOSE OUT THE ISSUE WITHOUT ACTION. OUR FREQ PROBS AT ZHU AFFECT SEVERAL SECTORS AND WILL; WITHOUT A DOUBT; CAUSE AN ACCIDENT. I HAVE BEEN A CTLR FOR OVER 16 YRS AND THIS IS THE MOST FRIGHTENING SITUATION THAT I HAVE EVER SEEN. 128.15; 126.1; 133.75; 132.8; AND 127.8 ARE ALL MALFUNCTIONING. WHEN RPTED TO THE SUPVRS; THE ISSUES ARE IGNORED.
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.