This configuration uses three sectors and shelves the airspace in two places, as depicted in this diagram:
All sectors have control on contact unless otherwise specified below, as long as the handoff continues toward the receiving controller's airspace and remains clear of the third controller's airspace. LAS_TWR owns the airspace within 5 miles of the airport, SFC-4000'. All departures except the STAAV are worked by W_APP. Arrivals overflying FUZZY or CLARR are handed by center to W_APP. Arrivals overflying LUXOR or KADDY are handed to E_APP by center. Since most arrivals will go to runway 25L, F_APP has a small airspace area to keep his workload manageable and relies on E_APP and W_APP as feeders to provide whatever MIT (Miles In Trail) he specifies. E_APP owns a shelf above F_APP to allow TRALR and LAS departures to pass overhead. W_APP owns a shelf above the SE corner of E_APP's airspace to allow COWBY, PRFUM, and HOOVR departures to remain in W_APP airspace as they climbout. LSV_APP airspace is owned by E_APP. There are no permanent or prearranged pointouts in this configuration.
Hand arrivals overflying FUZZY or CLARR to W_APP. Hand arrivals overflying LUXOR or KADDY to E_APP. The crossing restriction at KADDY is important since W_APP owns a shelf beginning at 13,000' along the KADDY/TYSSN STARs. If aircraft will not be level at 12,000' 2.5 miles or more from the LAS_APP boundary, they must be turned or coordinated with W_APP. All departures are worked by W_APP, except for the STAAV (and some vectored departures who aren't assigned a SID). STAAV departures are worked by E_APP. LSV_APP is owned by E_APP. Each approach sector has control on contact with all arrivals.
W_APP
W_APP owns the airspace as depicted on the diagram above. Note that W_APP owns a shelf above E_APP in the grey colored area, which allows COWBY/PRFUM/HOOVR departures to remain in W_APP airspace. Initial separation for all departures is provided by tower. Aircraft may not be vectored by W_APP until they are established in his airspace to ensure that separation is maintained. All departures will be worked by W_APP except for the STAAV, which is worked by E_APP. W_APP hands LAS and TRALR departures to E_APP for sequencing with STAAV departures prior to the E/W boundary. These departures must cross the airspace boundary between E and W_APP at or above 10,000' so that they are clear of F_APP airspace. All other departures are handed to the appropriate center sector by W_APP. COWBY, PRFUM, and HOOVR departures must cross the E/W boundary at/above 13000' so that they remain within W_APP airspace and above KADDY arrivals.
FUZZY and CLARR arrivals are handed to W_APP by center. These aircraft should generally be assigned runway 25L, merged into a single stream, and handed to F_APP with the MIT required by F_APP. These aircraft must cross the W/F_APP boundary at/below 9000, since E_APP owns a shelf at/above 10,000' over F_APP. F_APP does not have control for descent until aircraft enter his airspace. As needed, aircraft may be offloaded to runway 19L/R. 19L/R arrivals should be vectored toward a left downwind and overfly the eastern boundary of the airport at/above 5000' (tower owns the airspace SFC-4000' within 5 miles of the airport), and handed to E_APP with the required MIT. 19L/R arrivals must not be vectored west of the airport as they may conflict with departures. W_APP must ensure that aircraft vectored to 19L/R are separated from departures. Tower may assign any approved heading to departures; W_APP may require call for release on certain headings to allow more airspace for 19L/R arrivals to descend. E_APP may require advance notice of 19L/R arrivals so that they may be sequenced with arrivals from the NE; ensure these requirements are met.
Go arounds will be separated from departures by tower and assigned an approved heading. Some of these aircraft will be assigned a southbound heading and passed to W_APP for resequencing. Vector these aircraft such that the MIT requirements are met for the assigned runway.
W_APP is responsible for HND arrivals/departures. Both IAPs for HND require coordination with F_APP since the missed approach procedures operate in F_APP airspace. The approved headings for departures will likely create conflicts with LAS arrivals/departures. Pilots may need to depart VFR or confirm that southbound headings will permit terrain clearance to facilitate their departures.
E_APP
E_APP owns the airspace as shown on the diagram above. E_APP also owns LSV_APP airspace. Note that E_APP owns a shelf 10,000' and above over F_APP. This shelf allows TRALR and LAS departures to pass above F_APP, and those departures are handed from W_APP to E_APP for sequencing over TRALR intersection. In the grey colored airspace area in the SE corner, E_APP owns the airspace 12,000' and below. W_APP owns the overlying airspace to allow COWBY, PRFUM, and HOOVR departures to pass overhead.
Initial separation for all departures is provided by tower. Aircraft may not be vectored by E_APP until they are established in his airspace to ensure that separation is maintained. E_APP initially works STAAV departures. E_APP will eventually be handed TRALR and LAS departures from W_APP for sequencing with STAAV departures over TRALR intersection. E_APP may also occasionally handle a departure assigned a northwestbound heading. All other departures will not enter E_APP airspace.
LUXOR and KADDY arrivals will be handed to E_APP from center. GRNPA arrivals will remain within E_APP airspace when flying the STAR track. LUXOR arrivals must be vectored off the STAR so that they do not enter F_APP airspace. Both the KADDY and TYSSN STARs should remain within E_APP airspace. E_APP will assign KADDY/LUXOR arrivals either runway 19L/R or 25L depending on demand. 25L arrivals should be merged into a single stream and handed to F_APP with the MIT required by F_APP. E_APP works the 19L/R final and shall advise W_APP of any MIT requirements for these arrivals. E_APP should consider asking W_APP for advance notice of 19L/R arrivals, so that space can be made for them. Due to the constrained airspace available for 19L/R arrivals, E_APP should consider requiring speed/altitude restrictions for handoffs from W_APP.
Go arounds will be separated from departures by tower and assigned an approved heading. Some of these aircraft will be assigned a northwestbound heading and passed to E_APP for resequencing. Vector these aircraft such that the MIT requirements are met for the assigned runway.
Since E_APP owns LSV_APP airspace, he controls all operations at LSV and VGT. When LSV_APP is staffed, all IFR operations at VGT must be coordinated between LSV_APP and E_APP.
F_APP
F_APP owns the airspace, surface to 9000', as depicted on the diagram above and is responsible for working the 25L final. Runway 25R may not be used for arrivals unless coordinated with LAS_TWR. Most arrivals will land on runway 25L, and F_APP is responsible for advising E_APP and W_APP of any MIT requirements, or other restrictions. Aircraft on the SUNST and KEPEC arrivals must be vectored off the arrival, since they will enter E_APP airspace if they fly the arrival as charted. F_APP does not have control for descent on handoffs from W_APP until those aircraft enter his airspace. The airspace south of the 25L final is provided for delay vectors and general flexibility. F_APP's airspace ends at a 3½ mile final for 25L. Tower owns the adjacent airspace from the surface to 4000'. Ensure aircraft cross this boundary at/below 4000' (aircraft on the glideslope should cross the boundary at roughly 3200').
LAS_TWR owns the airspace within 5 miles of the airport from the surface to 4000'. LAS_TWR has IFR and VFR release authority, and is responsible for ensuring separation between all departures. Runways 25L, 25R, 19L, and 19R are authorized for departures; use of any other runway for departures requires coordination with the appropriate approach control sectors. Departures assigned a SID need not be issued an altitude in their IFR clearance, they should follow the altitude guidance shown on the SID chart. Departures that are not assigned a SID shall be assigned 7000' (or their cruise altitude if lower). Altitude assignments for go arounds are discussed below. F_APP controls the 25L final and may not use runway 25R, unless coordinated with LAS_TWR. E_APP works the 19L/R final and may use either runway for arrivals at his discretion.
LAS_TWR shall coordinate with LAS_GND any requirements for departure runway assignment. Otherwise, GND may taxi aircraft to any active runway at his discretion. Tower is responsible for initial separation of departures and may release aircraft at his discretion. Keep in mind that, except for the STAAV departure, all 19L/R departures converge with 25L/R departures and tower must sequence aircraft appropriately. All RNAV departures except the STAAV converge at ROPPR intersection. 19 departures fly two fewer miles to ROPPR than runway 25 departures. If a 19 departure follows a 25 departure, tower must provide additional spacing to accommodate the shorter distance to ROPPR. Aircraft not flying a SID (including VFR aircraft) must be issued headings approved in the "Assignment of Headings to Departures and Missed Approaches" SOP to ensure terrain separation. Tower shall choose a heading which ensures separation from other departures/missed approaches. Departures may not be assigned a north or northeast heading. Tower must include the consideration of aircraft speed and performance when releasing departures. Tower may want to consider assigning propeller driven aircraft an approved heading that will keep the aircraft east of the other SIDs. The STAAV3 departure is handed to E_APP; also, northwestbound departures are handed to E_APP. All other departures are handed to W_APP. LAS_DEL shall ensure that the correct departure frequency is issued. LAS_TWR shall provide rolling/boundary notifications to E/W_APP including the SID or assigned heading and departure runway.
Go arounds require precise instructions. All go arounds must be restricted to 4000' until they are abeam the LAS VOR, since W_APP may route 19L/R arrivals over the approach end of 25L at 5000'. Once aircraft are abeam the VOR they shall be assigned 7000'. 19L/R go arounds must be assigned headings such that they pass over or west of the LAS VOR to ensure separation from arrivals. Go arounds may not be assigned a northeast or eastbound heading since those might conflict with 19L/R arrivals. Go arounds must be separated from departures and passed to the appropriate approach sector based upon assigned heading. To affect separation, tower may assign any heading within his airspace. Go arounds must depart tower airspace on a heading approved in the "Assignment of Headings to Departures and Missed Approaches" SOP. For example, if a 25L go around will conflict with a 19R departure, the go around may be assigned a 270 heading initially (even though it is not an approved heading), and later assigned an approved heading once he is separated from the departure. Again, he must depart tower airspace on an approved heading to ensure terrain avoidance.