Narrative:

At L30 there is a configuration with departures off runway 1. The departure requires the aircraft to depart and reaching an altitude turn right to a heading of 050. The tower is to ensure the aircraft starts this turn before transferring communications to the TRACON. If everyone does their job; the tower and TRACON controllers; and the pilots; all goes well; however if one person in the chain makes a mistake; the potential for error or collision is great. A hawker departed runway 1 and called the TRACON prior to starting the turn; and continued to climb straight out; directly toward lsv TRACON airspace; located approximately 3 miles away. As the TRACON controller; I am not allowed to issue a vector below the MVA; therefore if the tower does not observe the turn; and I am in communication with the aircraft; he may proceed straight; depending on climb rate; and penetrate lsv airspace before he can be turned. If lsv cannot approve the point out; there is a potential for loss of separation or collision. Lsv routinely has high speed aircraft in the pattern; and this departure points right at them. Lsv had an aircraft maneuvering at 6;000 ft; and had I not been able to vector when I did; would have been in conflict. I was able to complete the point out; but this is an area of concern; as any number of things can go wrong; and there are very limited options to resolve the situation. In addition; the sector gets crowded very quickly as soon as one aircraft deviates from the norm; as all others pile up behind it. Due to the high number of aircraft that have difficulty flying procedures in and around las; a more positive controlled situation needs to be developed. L30 controllers are routinely asked to expose themselves to needless risk and lack of proper application of ATC rules; and management continues to ignore the problem; by continuing to allow dangerous operations.

Google
 

Original NASA ASRS Text

Title: L30 Controller voiced concern regarding the Runway 1 departure procedures noting that if the Tower; flight crew or the TRACON makes an error an airspace incursion with LSV is likely to occur.

Narrative: At L30 there is a configuration with departures off Runway 1. The departure requires the aircraft to depart and reaching an altitude turn right to a heading of 050. The Tower is to ensure the aircraft starts this turn before transferring communications to the TRACON. If everyone does their job; the Tower and TRACON controllers; and the pilots; all goes well; however if one person in the chain makes a mistake; the potential for error or collision is great. A Hawker departed Runway 1 and called the TRACON prior to starting the turn; and continued to climb straight out; directly toward LSV TRACON airspace; located approximately 3 miles away. As the TRACON Controller; I am not allowed to issue a vector below the MVA; therefore if the Tower does not observe the turn; and I am in communication with the aircraft; he may proceed straight; depending on climb rate; and penetrate LSV airspace before he can be turned. If LSV cannot approve the point out; there is a potential for loss of separation or collision. LSV routinely has high speed aircraft in the pattern; and this departure points right at them. LSV had an aircraft maneuvering at 6;000 FT; and had I not been able to vector when I did; would have been in conflict. I was able to complete the point out; but this is an area of concern; as any number of things can go wrong; and there are very limited options to resolve the situation. In addition; the sector gets crowded very quickly as soon as one aircraft deviates from the norm; as all others pile up behind it. Due to the high number of aircraft that have difficulty flying procedures in and around LAS; a more positive controlled situation needs to be developed. L30 controllers are routinely asked to expose themselves to needless risk and lack of proper application of ATC rules; and management continues to ignore the problem; by continuing to allow dangerous operations.

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.