A320
Air Traffic Control Developmental
Other / Unknown
ATC Issue All Types
General None Reported / Taken
Procedure
This report is regarding a procedure that is used routinely; that causes conflicts in the air; and potential safety hazards in order to expedite and reduce taxi time. At LAS there are several RNAV departures; and several non RNAV departures; that are designed for direction of departure from TRACON to Center airspace. Runway 25 is generally used by Air Carrier aircraft; and Runway 19 is generally used by private and business aircraft. This causes the problem described in this report. The STAAV Departure was designed to allow departure traffic to be balanced between the two departure sectors. The STAAV Departure is only used with departures off of Runway 25. Here in lies the problem; the Runway 19 departures; who naturally would rather not taxi to Runway 25; but instead depart Runway 19; are assigned a departure SID that is non-RNAV; and converges in the air to the Northeast of LAS causing an imbalance of traffic volume in the two sectors; as well as additional workload to both sectors due to the SID being non RNAV. Possible solution; either allow the Runway 19 departures to fly the STAAV departure SID; or discontinue allowing the Runway 19 departures; instead requiring those aircraft to taxi to Runway 25 to be flowed in with all departures thereby providing the built in balance of volume between the sectors. Either allow the Runway 19 departures to fly the STAAV SID; or discontinue allowing the Runway 19 departures; instead requiring those aircraft to taxi to Runway 25 to be flowed in with all departures thereby providing the built in balance of volume between the sectors.
L30 Controller voiced concern regarding the current departure runway assignments noting alternate departure runway assignments and/or changing the SID would elevate the potential conflicts now being experienced.