There are three types of pointouts which are used by ZLA controllers. They are each described in the following paragraphs. This is an exclusive list; if a permanent/prearranged
pointout is not documented below, it does not exist.
Permanent Pointouts - There are four permanent pointouts in ZLA. In each case, the pointout requires no contact between the controllers in question. The controller who owns the airspace affected by the pointout must protect that airspace at all times. These are the four permanent pointouts:
1. Aircraft routed via the SADDE6 arrival are permitted to enter BUR_APP's airspace, along the STAR track, at or above 12,000'. During east or noise abatement operations at LAX, aircraft routed via the MOOR3 arrival are permitted to enter BUR_APP's airspace, along the STAR track, at or above 11,000'. In either case, BUR_APP must always protect the appropriate airspace, as LAX_A_CTR is not required to coordinate its use. LAX_A_CTR is responsible to ensure separation between aircraft on the MOOR3 STAR to LAX and FERN5 STAR to BUR, until the MOOR3 arrival enters LAX_W_APP airspace.
2. Aircraft routed via the RIIVR1 or SEAVU1 arrival are permitted to enter ONT_APP's airspace, along the STAR track, so long as they are in compliance with the charted alitude restrictions for the procedure. ONT_APP must always protect this airspace, as LAX_FE_APP is not required to coordinate its use.
3. For aircraft routed to KLAX via SLI, LAX_S_APP has control for turns between heading 300 clockwise to 020, and descent between 7,000 and 3,500 after the aircraft has passed SLI VOR. SNA_APP must always protect this airspace, as LAX_S_APP is not required to coordinate its use.
4. Aircraft routed via any of the SIDs from ONT may operate closer than 1.5 miles from the ONT_APP/LAX_N_APP boundary. LAX_N_APP must always protect this airspace, as ONT_APP is not required to coordinate its use.
5. The LAX_APP airspace is designed for west operations. During east operations
and noise abatement operations, several SOPs describe permanent pointouts that are used by controllers; please see those SOPs for more information.
Prearranged Pointouts - There are several prearranged pointouts in ZLA. In each case, the controller who needs to permit an aircraft to enter another controller's airspace must first perform an automated pointout with the controller who will have the aircraft enter his airspace, as described below. The automated pointout is performed in VRC or ASRC using the command syntax "F1 sectorID ASEL". The controller client should respond with a message indicating that the pointout has been sent (see the radar client documentation for more information). No verbal or text communication is required; the receiving controller must advise the other controller if any restrictions are required on the pointout. The controller who receives the pointout must only protect the affected airspace if he has received an automated pointout. These are the prearranged pointouts for ZLA:
1. Aircraft climbing off of LAX on the LOOP4 departure are handed from LAX_DEP to LAX_B_CTR. They will operate in LAX_E_CTR airspace for a short time. At least one minute prior to an aircraft reaching 13000', LAX_DEP must perform an automated pointout with LAX_E_CTR; B_CTR must have accepted the handoff prior to communication transfer. E_CTR is expected to advise LAX_DEP or B_CTR of any needed restrictions.
2. Aircraft operating along V186, or on the ELMOO SID from BUR or GLEN SID from VNY, will briefly operate in LAX_N_APP airspace. Eastbound aircraft will be handed from BUR_APP to ONT_APP; westbound aircraft will be handed from ONT_APP to BUR_APP. The sector initiating the handoff will perform an automated pointout with LAX_N_APP at least one minute prior to the aircraft crossing the LAX_N_APP boundary. Operations under this paragraph must occur at or below 7000'. Any aircraft operating along V186 above 7000' must be coordinated by voice or text with LAX_N_APP as a standard pointout (discussed in the next section).
3. Aircraft operating on the KAYOH4 arrival via DAWNA intersection will be handed from LAX_C_CTR to ONT_APP. These aircraft will likely cross through LAX_FE_APP airspace. Aircraft may enter LAX_FE_APP airspace at or below 13,000' as long as ONT_APP performs an automated pointout with LAX_FE_APP at least one minute prior to aircraft crossing the LAX_FE_APP boundary.
4. BUR_APP may clear aircraft for approaches to CMA or OXR as long as BUR_APP performs an automated pointout with NTD_APP at least one minute prior to the aircraft crossing the NTD_APP boundary.
5. BUR_APP may clear aircraft for an approach to EMT as long as an automated pointout is performed with both ONT_APP and LAX_N_APP prior to the aircraft being cleared for the approach and at least one minute prior to the aircraft crossing the FAF. IFR departures from EMT must be coordinated with ONT_APP and LAX_N_APP as standard pointouts (see the next section) prior to departure.
6. BUR_APP may clear aircraft for an approach to L70 as long as an automated pointout is performed with LAX_B_CTR prior to the aircraft being cleared for the approach. IFR departures from L70 must be coordinated with LAX_B_CTR as a standard pointout (see the next section) prior to departure.
7. VFR aircraft operating on the Hollywood Park route through the LAX class B airspace will be handed from LAX_DEP to LAX_N_APP when northbound and from LAX_N_APP to LAX_DEP when southbound. These aircraft will briefly operate in LAX_S_APP airspace. Aircraft may enter LAX_S_APP airspace, between 7000' and 10,000', as long as an automated pointout is performed with LAX_S_APP at least one minute prior to the aircraft crossing the LAX_S_APP boundary.
8. VFR aircraft operating on the Shoreline Route through the LAX class B airspace will be handed between LAX_DEP and BUR_APP. These aircraft may enter LAX_N_APP
airspace so long as an automated pointout is performed at least one minute prior to aircraft crossing the airspace boundary.
9. LAX_DEP may climb aircraft on the GMN4 departure into LAX_W_APP airspace once they are north of the SADDE6 arrival stream so long as LAX_DEP performs an automated pointout with LAX_W_APP at least one minute prior to the aircraft initiating a climb above 6000'.
10. Turboprop and turbojet aircraft routed to KLAX via SLI will be handed off from SNA_APP to LAX_S_APP level at or descending to 7,000. Such aircraft may penetrate LAX_DEP airspace between 11,000 and 9,000 so long as SNA_APP performs an automated pointout with LAX_DEP at least one minute prior to the aircraft crossing the LAX_DEP boundary. During those times where LAX_DEP airspace is owned by LAX_S_APP, the initiation of the handoff may substitute for the automated pointout if it is initiated at least one minute prior to the airspace boundary (LAX_S_APP need not accept the handoff, the handoff only needs to be initiated in this case).
Standard Pointouts - Any pointout not specifically mentioned in the two groups above must be approved by the receiving controller via text or voice prior to the aircraft entering his airspace. The phraseology for standard pointouts is discussed in .65 section 5-4 and in Jeff Clark's article.
