letter of agreement - ivao usaivaous.org/fdr/loas/zla/sct/040 - sct crq.pdf · gillespie,...

Southern California TRACON and Palomar Airport Traffic Control Tower

LETTER OF AGREEMENT

EFFECTIVE: August 22, 2013 SUBJECT: Interfacility Coordination Procedures 1. PURPOSE: To define procedures for coordination and control of air traffic between Southern California TRACON (TRACON) and Palomar Airport Traffic Control Tower (Tower) at Palomar (CRQ) airport. This agreement is supplementary to the procedures contained in FAA JO Order 7110.65, Air Traffic Control. 2. CANCELLATION: Southern California TRACON, Brown Federal Contract Tower, Gillespie, Montgomery, and Palomar Towers Letter of Agreement, Subject: Interfacility Coordination Procedures, dated November 1, 2001. 3. SCOPE: The procedures outlined herein are for establishing specific procedures for the handling of IFR, VFR, and Special VFR operations at CRQ. Procedures and responsibilities contained in this agreement apply during periods when the Tower is in operation. 4. RESPONSIBILITIES:

a. TRACON is responsible for control of all IFR aircraft at CRQ. b. Tower is responsible for and must:

(1) Provide separation between IFR/SVFR operations. (2) Provide separation between SVFR operations. (3) Provide separation between IFR departures and IFR arrivals. (4) Control VFR aircraft within the Tower Class D Surface Area and Class E Arrival Extensions. (5) Conduct SVFR operations within the Tower’s Class D Surface Area as provided in this Agreement. (6) Use data displayed on the Certified Tower Radar Display (CTRD) to ensure/provide separation between IFR/SVFR operations. (7) Utilize CTRD procedures when the CTRD is operational.

5. PROCEDURES:

a. Coordination:


2

(1) TRACON must:

(a) Notify Tower of San Diego Lindbergh and Los Angeles Airport configurations, and flow control implementations and/or cancellations, when Tower FDIO is out-of-service. (b) Notify Tower either verbally or via FDIO when there are changes in communications, NAVAIDS, ARTS/STARS, FDIO, ZLA/SCT interface, and when there is a change to Miramar or Camp Pendleton radar sensors.

(2) Tower must:

(a) Notify TRACON Flight Data position of current ATIS letter, and all hourly and special weather observations via FDIO. Notify TRACON Flight Data position of runway changes via landline. (b) Notify TRACON Supervisor/CIC of changes in field conditions, communications, NAVAIDS, FDIO, and CTRD status. (c) Coordinate with TRACON Flight Data upon opening and closing of Tower. During this coordination, each facility must exchange pertinent traffic information, including, but not limited to, aircraft that have received an IFR clearance but have not departed, opening ATIS code, current weather and runway in use, and any airport conditions which may affect aircraft operations. (d) Enter a departure message on all non-beacon departures via the FDIO. (e) Enter a departure message on all IFR departures via the FDIO when ZLA/SCT interface is out-of-service. (f) Forward flight data information for all proposed departures when TRACON FDIO is out-of-service.

b. Communications:

(1) The “CRQ Ring Line” (P10002) must be used by Tower for departure releases and inactive messages.

(a) Del Mar Sector (127.3 / 323.0) -- dial 75. (b) TRACON Flight Data -- dial 77.

(2) The “PAL Hot Line” (P11043) must be used by TRACON for IFR inbounds and active control messages.


3

(3) TRACON must advise Tower of intent to combine/de-combine Del Mar sector at least three (3) minutes in advance. (4) Tower must assign departures and missed approaches 127.3 / 323.0. (5) TRACON must assign 118.6 / 392.0 to all IFR arrivals.

c. Clearances:

(1) Tower must:

(a) Request clearance from TRACON at least ten (10) minutes prior to release request for flights into Mexico (except if filed over JLI) or westbound oceanic. (b) When CTRD is not operational/available, forward to the TRACON Flight Data the following information on local IFR flight plans:

1) Aircraft identification. 2) Type aircraft and equipment suffix. 3) Destination airport or clearance limit. 4) Requested altitude.

(c) Enter IFR climb to VFR on top flight plans via the FDIO by utilizing the letter “P” rather “N” to depict the aircraft’s call sign, and entering the destination with requested VFR altitude in the remarks section. Example:

FP P12345 C172/A 100 CRQ PXX00 40 CRQ..OCN °VNY/45 NOTE: The following entry via the ARTS/STARS keyboard may be made to expedite movement of IFR climb to VFR on top civil aircraft in MEDEVAC status: Example: FLT DATA (F6) (call sign) LN12345 (space) (indicates IFR) + (space) (primary scratchpad) CRQ*MYF (space) (secondary scratchpad) +OTP (space) (type aircraft) C172 (enter)


4

(d) Enter local IFR flight plans via the ARTS/STARS keyboard, as follows:

Example: FLT DATA (F6) (call sign) N12345 (space) (indicates IFR) + (space) (primary scratchpad) CRQ*MYF (space) (type aircraft) C172 (enter)

(e) Unless otherwise verbally coordinated, assign heading 250 to Runway 24 IFR departures, radar vector first fix/route. Assign the published Obstacle Departure Procedure to Runway 6 departures. (f) Issue the appropriate IFR clearance in accordance with the provisions contained in TABLE 1 for aircraft destined for local San Diego area airports or an IFR climb to VFR conditions on top. (g) Issue the appropriate Tower Enroute Control (TEC) clearance for the type aircraft, destination, and Los Angeles runway configuration as contained in the Airport Facilities Directory. (h) Instruct all IFR departures to “maintain 3000.” All departures “expect (higher altitudes shown below) one zero minutes after departure.”

1) IFR departures exiting TRACON airspace: filed or TEC altitude, as appropriate. 2) Local IFR clearances: refer to the TABLE 1.

(i) Issue a clearance void time (obtained from the TRACON) for all IFR departure clearances issued to aircraft that have not departed prior to Tower closing. (j) Preferential Routing (PDR). When a computer generated flight progress strip’s routing contains plus signs (a PDR), Tower must ensure that all information between the plus signs is issued. (k) Issue all flight plan amendments.

(2) TRACON must:

(a) Obtain clearance for departures entering Mexican airspace via TIJ VOR. (b) Obtain an Oceanic release (ZLA Sec 28) when needed. (c) Ensure and/or amend IFR clearance routing for aircraft filed outside of TRACON airspace.


5

d. IFR Departures:

(1) Tower must:

(a) Request a departure release from the appropriate TRACON control position no earlier than five (5) minutes after filing or receiving a flight plan via the FDIO. (b) Utilize the ARTS/STARS rundown patch feature to request IFR departure releases as follows:

1) Ensure departures are entered into the appropriate sector’s rundown list and that the order of IFR departing aircraft is correct. 2) Forward flight plan amendments by putting “AM” in the remarks section of the rundown list followed by the flight plan amendment number (AM1). 3) Forward Traffic Management release times in the remarks section by using “RL” followed by minutes past the hour, e.g., a TMU release of 1845 void 1847 would be entered as “RL45.” 4) The remarks section of the rundown patch must be used first to forward information as to flight plan amendments. Verbally coordinate additional requests or information. 5) Verbal coordination must supersede any requests placed into the rundown patch. When verbal coordination is effected for a departure release, the flashing request in the rundown list does not need to be acknowledged to depart that aircraft. 6) Notify TRACON of any changes to the departure sequence either by re-entering the applicable aircraft into the rundown list in the correct order, or through verbal coordination. 7) Allow three (3) minutes for acknowledgement of the rundown list prior to initiating verbal coordination with the TRACON. 8) Depart aircraft within three (3) minutes of acknowledgement of the rundown list or verbal coordination. Depart aircraft with a Traffic Management release time within its assigned three (3) minute window. 9) Verbally coordinate with the TRACON any aircraft that is removed from the rundown list, is delayed, or cancels. However, should an aircraft not depart within three (3) minutes as provided for above, Tower may re-enter that aircraft into the


6

rundown list with the flash feature as long as the entry is made prior to the expiration of the three (3) minutes from the time of the original release.

NOTE: Combining or de-combining positions will result in a clearing of the rundown list. Affected departures must be manually placed in the appropriate sector’s rundown list.

10) Alternate headings Runway 24 Only: Request an alternate departure heading by putting “H” in the remarks section of the rundown list, followed by the three digit heading (H230). No heading information needs to be entered into the remarks section of the rundown list on aircraft that will depart on heading 250. The only allowable alternate heading requests must be H230 and H270, based on the following:

a) Heading 230 may be requested for aircraft with destinations south of CRQ including JLI. b) Heading 270 may be requested for aircraft en route to Oceanside Airport or TEC routes.

(c) Verbally request IFR release of aircraft departing a runway other than the on advertised on the ATIS. State the departure runway when requesting the release. (d) Utilize verbal coordination when Del Mar sector is combined at a position other than North or Miramar. (e) Ensure that all IFR aircraft are airborne within three (3) minutes after obtaining departure release from TRACON or re-coordinate. If multiple departure releases are approved, ensure that departing aircraft are airborne within three (3) minutes of the preceding departure aircraft. (f) Forward departure times to the TRACON on all IFR non-transponder equipped aircraft and all IFR departures when TRACON ARTS/STARS is out-of-service. (g) Separate a departing IFR aircraft from an arriving IFR aircraft on final approach by:

1) A minimum of three (3) miles. 2) A minimum of two (2) miles if separation will increase to a minimum of three (3) miles within one minute after takeoff. 3) Visual separation.


7

(h) Separate successive IFR departures as follows:

1) Aircraft that will fly courses diverging by 15 degrees or more immediately after takeoff--one mile. 2) Aircraft that will fly the same course--3 miles, provided the succeeding aircraft is the same or slower speed than the preceding aircraft. Faster following slower must be assigned by TRACON.

(i) When CTRD is not operational/available:

1) Tower must suspend IFR departures when the IFR arrival is over the final approach fix. The local controller may release the IFR departure reference the IFR arrival when one of the following exist:

a) The local controller sees the arrival and can provide visual separation. b) The local controller coordinates with the TRACON to determine that the arrival has not reached the final approach fix. c) The local controller ascertains from the pilot that the aircraft has not crossed the final approach fix.

2) TRACON must specify departure interval for successive departures.

(j) Notify TRACON when a departure does not auto-acquire within five (5) miles of the departure end of the runway. Phraseology: “A/C position, ACID, no tag.” (k) Release control of IFR aircraft off their initial departure heading west of the coastline or at or above 2500 feet MSL. Release control of VFR aircraft upon transfer of communications.

(2) TRACON must:

(a) Use the rundown patch to release departures, acknowledge flight plan amendments, approve requested alternate headings, and changes to the rundown sequence. (b) Verbally coordinate departure releases with Tower when unable to release aircraft via the rundown patch, whether due to changes in sequence, headings, or otherwise, and advise Tower of anticipated delay estimates. Advise Tower of any condition which may cause delays of more than five (5) minutes to IFR departures. (c) Coordinate with Tower prior to combining or de-combining the Del Mar sector to confirm the status of any aircraft in the rundown list.


8

e. IFR Arrivals:

(1) TRACON must:

(a) Retain continuous control of IFR aircraft. (b) Advise Tower when Del Mar Sector is combined at another radar position. (c) Transfer communications to Tower no earlier than twelve (12) flying miles, but not less than seven (7) flying miles from the airport, unless otherwise coordinated. For aircraft on straight-in instrument approach, transfer communications no later than final approach fix. (d) Ensure Runway 24 J and M aircraft will be no less than four (4) miles from end of runway when vectoring to a base leg entry, unless otherwise coordinated. (e) Verbally coordinate, no later than fifteen (15) flying miles from the airport, the position, aircraft identification, and sequence of all aircraft executing a contact approach. (f) IFR aircraft executing an instrument approach must be afforded standard IFR separation until the aircraft lands or the pilot cancels the IFR flight plan. Only IFR aircraft are authorized to execute the published missed approach. IFR aircraft requesting VFR services must cancel IFR with Tower or TRACON prior to the issuance of VFR climb-out instructions. Any aircraft that does not cancel IFR should be given a full-stop landing. If it is not practicable for the aircraft to land, the aircraft must be issued a published missed approach. Tower must advise TRACON of any unplanned missed approaches. (g) TRACON must provide the Tower IFR and VFR arrival information and approach sequence via Auto-Quicklook function through an ARTS/STARS Full Data Block (FDB) ensuring the following scratch pad information is contained in the FDB. A trailing “V” at the end of the second line of the FDB indicates that the aircraft is VFR and is conducting practice approaches in VFR conditions. If the VFR aircraft will make a full stop landing at the conclusion of its VFR practice approach, the appropriate approach identifier must be placed in the secondary scratchpad.


9

SCRATCH PAD TYPE APPROACH None Primary IAP (ILS, VOR, LOC) to a full stop ILS, LOC, VOR, GPS, RNV ILS, LOC, VOR, NDB, GPS or RNAV to a full stop

V Visual Approach with the field in sight VV Visual Approach with the preceding IFR aircraft in sight I__ = ILS L__ = LOC

G__ = GPS R__ = VOR

Practice IAP followed by standard VFR climb out back to TRACON *Note 1

IT__ LT__ GT__ RT__

Practice IAP followed by VFR climb out. No further TRACON service requested.

*Note 1: Standard VFR climb out for CRQ = south for aircraft with destinations to or south of CRQ, and west for aircraft with destinations north of CRQ. This means aircraft must cancel IFR flight plan with Tower. TRACON requests Tower route aircraft VFR in the standard direction. Tower must ensure the pilot cancels IFR and is instructed to “maintain VFR” prior to issuing VFR climb out instructions. TRACON must verbally coordinate any direction except standard VFR climb out instruction. (Note: 3rd character in scratch pad for TRACON use only.)

(h) TRACON must not make changes to scratch pad information after frequency change has been initiated, without coordination. (i) In the event of an ARTS/STARS failure, TRACON must advise Tower of aircraft position, callsign, type aircraft, type approach, and intentions (if other than a full stop) no later than fifteen (15) flying miles from the airport.

(2) Tower must:

(a) Notify TRACON of a missed approach via the “shout” line. Aircraft executing a missed approach shall be assigned one of the following climb-out instructions:

1) Aircraft on a published instrument approach (for either runway), issue the published missed approach. 2) Aircraft on Runway 24 published straight-in instrument approaches with a slower IFR departure ahead. Tower shall coordinate as soon as practical with TRACON if these headings are used.

a) Heading 270, maintain 3000 feet, if preceding departure has destination south of CRQ including JLI.


10

b) Heading 230, maintain 3000 feet, if preceding departure has destination north of OKB or any TEC routes.

(b) Advise TRACON of any aircraft on an instrument approach that cancels IFR prior to the airport. (c) Ensure that aircraft cancel IFR prior to issuing VFR Climb out instructions and that the pilot is instructed to “maintain VFR.” (d) Utilize Auto-Forced ARTS/STARS data to obtain arrival information and approach sequence on all IFR arrivals. (e) Notify TRACON Supervisor/CIC if the automated arrival procedures cannot be utilized due to equipment limitations or any failure of the automated Quicklook function.

f. Special VFR:

(1) Tower is authorized to conduct SVFR operations in its Class D Airspace and Class E Arrival Extensions at and below 2500 feet MSL. Coordination must be accomplished with the TRACON prior to issuing a SVFR clearance to an aircraft in the northwest Class E arrival extension. (2) Tower must provide separation between SVFR and SVFR/IFR as follows:

(a) SVFR helicopter separation in accordance with FAA JO 7110.65, Air traffic Control. (b) Suspend Fixed Wing SVFR operations prior to an arriving IFR aircraft crossing the final approach fix. SVFR operations may be resumed when the arrival has landed or the Tower has both aircraft in sight and can provide visual separation. (c) Suspend Fixed Wing SVFR operations until a departing IFR aircraft has exited the Class D Surface Area. (d) Tower may provide visual separation between successive Fixed Wing SVFR arrivals when Tower has both aircraft insight. (e) Visual separation may be authorized between successive same direction Fixed Wing SVFR departures or arrivals provided the succeeding aircraft has the preceding aircraft in sight and agrees to maintain visual separation from it. (f) Visual separation may be authorized between multiple Fixed Wing SVFR operations which are conducted solely within the airport traffic pattern.


11

g. Opposite Direction Operations:

(1) General:

(a) Same runway opposite direction procedures are applicable when both of the opposing aircraft are IFR. (b) Local control and the TRACON arrival sector are responsible for initiating coordination required to accomplish an opposite direction arrival or departure. (c) Traffic advisories must be issued to both the arriving and departing aircraft.

EXAMPLE:

OPPOSITE DIRECTION TRAFFIC (distance) MILE FINAL, (type aircraft). OPPOSITE DIRECTION TRAFFIC ONE FIVE MILES EAST, (type aircraft). OPPOSITE DIRECTION TRAFFIC DEPARTING RUNWAY (number), (type aircraft)

(d) Do not allow opposite direction same runway operations with opposing traffic inside the cutoff point unless an emergency situation exists. (e) Opposite direction operations conducted from parallel runways must be turned away from opposing traffic when inside the cutoff point to the other runway.

(2) Coordination:

(a) Tower must verbally request opposite direction departures with TRACON. (b) TRACON must verbally request opposite direction arrivals with Tower. (c) All coordination must be on a recorded line and must state, “Opposite Direction”, and include call-sign, type, and arrival or departure runway.

(3) IFR Arrival and IFR Departure:

(a) Tower must issue appropriate Departure Procedure to the departing aircraft. (b) Tower must ensure the departure is airborne and observed turning to avoid conflict prior to the arrival aircraft reaching a point within a ten (10) nautical mile radius from the arrival runway threshold.

(4) IFR Arrival and IFR Arrival: TRACON arrival sector must ensure that the first arrival has crossed the runway threshold prior to the opposing arrival reaching a point within ten (10) nautical mile radius from the arrival runway threshold.

letter of agreement - ivao usaivaous.org/fdr/loas/zla/sct/040 - sct crq.pdf · gillespie,...

Documents