Narrative:

I was working granite sector which is an arrival sector for our airspace. We were in the process of a runway configuration change. I was informed that a B737 would be my first arrival to the new runway. Traffic flow changes for my sector with the runway change. I was told we were on new configuration which gave me airspace that I did not previously have. I turned the B737 and descended aircraft to 11;000 and told aircraft to expect runway 07R. Aircraft was leveled at 12;000 when a pop-up VFR track appeared on scope at 11;500. I was then yelled at by the departure controller wanting to know what I was doing with the B737. Initially I responded with I'm level at 12;000 but when I cleared the VFR aircraft I descended the B737 to 11;000. It seems that the departure controller was not aware of a runway change and wanted to know what I was doing with the B737. I responded that I was vectoring for runway 07R. With our local procedures; departure control has pre approval to go through arrival airspace as long as they miss the arrival traffic. This did not occur because they did not realize we had changed configurations. My recommendation is a change in the way we train here at L30. I understand that RNAV is coming but we are starting to get a lot of aircraft monitors and don't have to many air traffic controllers left. The departure controller had aircraft level at 11;000 on the departure as per the restrictions. However; those restrictions only work if every one is on the same configuration. If departure would have just climbed the departures unrestricted to FL190 this incident would never have happened. We are training that if you leave an aircraft on a departure you don't have to separate him from anything which causes aircraft monitors to become complacent in there scan of the radar presentation.

Google
 

Original NASA ASRS Text

Title: L30 Controller described a conflict event when runway configuration changes were not disseminated to all of the controllers in the room causing the incident; the reporter feels controllers are not as attentive as in the past.

Narrative: I was working Granite Sector which is an arrival sector for our airspace. We were in the process of a runway configuration change. I was informed that a B737 would be my first arrival to the new runway. Traffic flow changes for my sector with the runway change. I was told we were on new configuration which gave me airspace that I did not previously have. I turned the B737 and descended aircraft to 11;000 and told aircraft to expect Runway 07R. Aircraft was leveled at 12;000 when a pop-up VFR track appeared on scope at 11;500. I was then yelled at by the Departure Controller wanting to know what I was doing with the B737. Initially I responded with I'm level at 12;000 but when I cleared the VFR aircraft I descended the B737 to 11;000. It seems that the Departure Controller was not aware of a runway change and wanted to know what I was doing with the B737. I responded that I was vectoring for Runway 07R. With our local procedures; Departure Control has pre approval to go through arrival airspace as long as they miss the arrival traffic. This did not occur because they did not realize we had changed configurations. My recommendation is a change in the way we train here at L30. I understand that RNAV is coming but we are starting to get a lot of aircraft monitors and don't have to many air traffic controllers left. The Departure Controller had aircraft level at 11;000 on the departure as per the restrictions. However; those restrictions only work if every one is on the same configuration. If Departure would have just climbed the departures unrestricted to FL190 this incident would never have happened. We are training that if you leave an aircraft on a departure you don't have to separate him from anything which causes aircraft monitors to become complacent in there scan of the RADAR presentation.

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