Narrative:

I relieved a controller at ZLA. During the relief briefing I was not made aware of the frequency problems or the recent change in airspace confign. We had recently been delegating airspace in that area at and below FL190 to nellis atcf. In order to get propellers to meet their crossing restr for descent into las; I needed to descend them to FL200 and hand them off to natcf. At about XA55 I descended the king air from FL250 to FL200. At about XA58 conflict alert activated between the king air and the B737; which was about 4 mi behind the king air. The B737 was at FL230. I stopped the king air's descent at FL240; but he went through it to FL236. I also turned the B737 and descended him to FL200. I believe the true cause of this incident was the fact that I was completely preoccupied with a family member's health. The fact that the recent change in airspace was incorrectly depicted on the radar map also led me to believe that the airspace had not been changed. If I had known that; I would have never descended the king air. I was also repeating myself to several airplanes at that sector from the bad frequencys. If I was able to make 1 transmission to each airplane; this might not have happened. This sector is known for its unforgiving nature. The northern end of the sector is 15-20 NM wide; however we are required to work both las arrs and departures; with bad frequencys; I believe that zola's airspace is completely out of date with its traffic needs. My experience working on the east coast has shown me that working busy departure and arrival traffic at the same sector is just unwise.

Google
 

Original NASA ASRS Text

Title: ZLA CTLR EXPERIENCED OPERROR AT APPROX FL230 WHEN FREQ PROBLEMS/AIRSPACE CHANGES WERE NOT BRIEFED; CONTRIBUTING TO ERROR.

Narrative: I RELIEVED A CTLR AT ZLA. DURING THE RELIEF BRIEFING I WAS NOT MADE AWARE OF THE FREQ PROBS OR THE RECENT CHANGE IN AIRSPACE CONFIGN. WE HAD RECENTLY BEEN DELEGATING AIRSPACE IN THAT AREA AT AND BELOW FL190 TO NELLIS ATCF. IN ORDER TO GET PROPS TO MEET THEIR XING RESTR FOR DSCNT INTO LAS; I NEEDED TO DSND THEM TO FL200 AND HAND THEM OFF TO NATCF. AT ABOUT XA55 I DSNDED THE KING AIR FROM FL250 TO FL200. AT ABOUT XA58 CONFLICT ALERT ACTIVATED BTWN THE KING AIR AND THE B737; WHICH WAS ABOUT 4 MI BEHIND THE KING AIR. THE B737 WAS AT FL230. I STOPPED THE KING AIR'S DSCNT AT FL240; BUT HE WENT THROUGH IT TO FL236. I ALSO TURNED THE B737 AND DSNDED HIM TO FL200. I BELIEVE THE TRUE CAUSE OF THIS INCIDENT WAS THE FACT THAT I WAS COMPLETELY PREOCCUPIED WITH A FAMILY MEMBER'S HEALTH. THE FACT THAT THE RECENT CHANGE IN AIRSPACE WAS INCORRECTLY DEPICTED ON THE RADAR MAP ALSO LED ME TO BELIEVE THAT THE AIRSPACE HAD NOT BEEN CHANGED. IF I HAD KNOWN THAT; I WOULD HAVE NEVER DSNDED THE KING AIR. I WAS ALSO REPEATING MYSELF TO SEVERAL AIRPLANES AT THAT SECTOR FROM THE BAD FREQS. IF I WAS ABLE TO MAKE 1 XMISSION TO EACH AIRPLANE; THIS MIGHT NOT HAVE HAPPENED. THIS SECTOR IS KNOWN FOR ITS UNFORGIVING NATURE. THE NORTHERN END OF THE SECTOR IS 15-20 NM WIDE; HOWEVER WE ARE REQUIRED TO WORK BOTH LAS ARRS AND DEPS; WITH BAD FREQS; I BELIEVE THAT ZOLA'S AIRSPACE IS COMPLETELY OUT OF DATE WITH ITS TFC NEEDS. MY EXPERIENCE WORKING ON THE EAST COAST HAS SHOWN ME THAT WORKING BUSY DEP AND ARR TFC AT THE SAME SECTOR IS JUST UNWISE.

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