Point Mugu Approach (NTD)

POC: Facility Advisory Board	Date: 2008-12-24
Code: ZLA-303	Version: 2.00

1. PURPOSE.

This Standard Operating Procedure (SOP) outlines the general procedures to be used by controllers working Point Mugu Tracon(NTD)s to ensure safe and efficient handling of air traffic into, out of and through the NTD airspace. By specifying standard phraseology and procedure, this SOP provides for the use of common air traffic handling language and operations.

2. ROLES AND RESPONSIBILITIES.

The Office of Primary Responsibility (OPR) for this SOP is the ZLA Facility Advisory Board (FAB). This SOP was approved by the FAB on January 01, 2003. This SOP shall be maintained, revised, updated or canceled by the ZLA FAB or any other organization that supersedes, replaces or assumes the FAB responsibilities. Any suggestions for modification or amendment to this SOP should be sent to the ZLA FAB for review.

3. DISTRIBURTION.

This SOP is intended for use by controllers staffing the NTD Tracon Position.

4. REQUIREMENTS.

a. Frequency: 124.7

b. Airspace: NTD shall own all airspace from the Surface to 8000 as depicted on the NTD Sector Map.

5. OPERATING PROCEDURES

a. General

Point Mugu Approach handles IFR arrivals/departures into and out of Camarillo (CMA), Oxnard(OXR) and Point Mugu NAS(NTD). It also handles low altitude traffic enroute between Santa Barbara and SOCAL Tracons. In addition, NTD_APP is responsible for maintaining a "sterile" airspace corridor offshore from the NAS, as low-level missile tests are sometimes conducted offshore from this location.

b. CMA and OXR

Instrument arrivals into CMA and/or OXR will normally be vectored onto the final approach course by BUR APP and handed off to NTD_APP when established. NTD_APP must monitor the approach from that point and handle any missed approaches. NTD retains control and sequencing authority for the final approach course of these airports, and BUR APP must perform an automated at least one minute prior to crossing the NTD airspace boundary. See the Pointout and Controller Coordination SOP for more details.