Narrative:

B737 was inbound on the SUNSET2 RNAV arrival; but was not descending via. We were on configuration 6; landing runway 19L/7R. Runway 19R was notamed closed; adding to our complexity. There were 6 other aircraft in or affecting our sector to the east; over 30 NM away. I issued speed of 210 KTS and then a descent to 11;000 to B737 and to expect runway 7R. As the B737 neared tragr way point; my ojti observed a primary target near the B737 and instructed me to issue traffic. I issued the primary traffic only to the B737; and then went back to the other aircraft in the eastern part of my airspace. Then B737 reported something like; 'wow; that's a glider and he's at my altitude!' the targets were separated by less than a mile. B737 continued inbound and got vectored around to the right traffic pattern for runway 7R. L30 needs to establish RNAV routes for all configurations to protect for the differing flow of traffic; rather than slightly alter the RNAV routes depending on how we are landing. This will permit us to identify low volume areas for glider and other recreational aircraft operations. L30 needs to establish VFR corridors to keep aircraft safely out of the way of the arrival/departure routes. L30 needs to add to the class B airspace to more accurately reflect our traffic movement; and help prevent primary only aircraft from operating so close to the airfield. L30 has numerous radar coverage problems; and needs to address these areas; to better 'see' the aircraft that are out there; this glider was a very small primary only target and we had only 3 or 4 good hits on it. This airspace is far too busy to continue working with such spotty radar coverage.

Related reports:

Google
 

Original NASA ASRS Text

Title: L30 Controller described conflict event between an air carrier arrival and a glider; traffic information was issued; the reporter suggesting a number of procedural changes to prevent future like occurrences.

Narrative: B737 was inbound on the SUNSET2 RNAV arrival; but was not descending VIA. We were on Configuration 6; landing Runway 19L/7R. Runway 19R was NOTAMed closed; adding to our complexity. There were 6 other aircraft in or affecting our sector to the east; over 30 NM away. I issued speed of 210 KTS and then a descent to 11;000 to B737 and to expect Runway 7R. As the B737 neared TRAGR way point; my OJTI observed a primary target near the B737 and instructed me to issue traffic. I issued the primary traffic only to the B737; and then went back to the other aircraft in the eastern part of my airspace. Then B737 reported something like; 'wow; that's a glider and he's at my altitude!' the targets were separated by less than a mile. B737 continued inbound and got vectored around to the right traffic pattern for Runway 7R. L30 needs to establish RNAV routes for all configurations to protect for the differing flow of traffic; rather than slightly alter the RNAV routes depending on how we are landing. This will permit us to identify low volume areas for glider and other recreational aircraft operations. L30 needs to establish VFR corridors to keep aircraft safely out of the way of the arrival/departure routes. L30 needs to add to the CLASS B airspace to more accurately reflect our traffic movement; and help prevent primary only aircraft from operating so close to the airfield. L30 has numerous RADAR coverage problems; and needs to address these areas; to better 'see' the aircraft that are out there; this glider was a very small primary only target and we had only 3 or 4 good hits on it. This airspace is far too busy to continue working with such spotty RADAR coverage.

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