Virtual Jacksonville Air Route Traffic Control Center Orlando International ATCT Standard Operating Procedures

Virtual Jacksonville Air Route Traffic Control Center Orlando International ATCT Standard Operating Procedures 1) Disclaimer: The information contained herein is meant for flight simulation purposes only and not real world aviation. ZJX describes a virtual ARTCC within the VATSIM Network and in no way represents real world ZJX, F11 or the FAA. 2) Purpose: This document describes the standard operating procedures for the Central Florida TRACON (hereafter designated F11), its positions, and operation procedures unique to F11. 3) Positions: Position Relief Name Voice Callsign MCO_E_TWR* MCO_E1_TWR LCE Orlando Tower MCO_W_TWR MCO_W1_TWR LCW Orlando Tower MCO_E_GND MCO_E1_GND GCE Orlando Ground MCO_W_GND* MCO_W1_GND GCW Orlando Ground MCO_DEL MCO_1_DEL CD Orlando Delivery Frequency Position Symbol ID 118.450 1T T 124.300 1S T 126.400 1Y N/A 121.800 1G N/A 134.700 1D N/A * Positions are primary positions. When these positions are opened, controllers have the option of removing the location identifier (E/W). Example: MCO_E_TWR > MCO_TWR. Relief callsigns become the full callsign, example MCO_TWR will be relieved by MCO_E_TWR a. F11 Positions/Acronyms: Position Sector Frequency Pos ID Symbol MCO_E_APP Departure Radar East (DRE) 124.800 4 E MCO_W_APP Departure Radar East (DRW) 120.150 4 W MCO_B_APP Arrival Radar Bitho (ARB) 125.550 4 B MCO_L_APP Arrival Radar Leese (ARL) 134.050 4 L MCO_M_APP Arrival Radar Monitor(ARM) 127.750 4 M MCO_N_APP Satellite Radar North (SRN) 121.100 4 N MCO_D_APP Satellite Radar Disney (SRD) 119.400 4 D MCO_K_APP Satellite Radar Kape (SRK) 134.950 4 K MCO_S_APP Satellite Radar South (SRS) 132.650 4 S When DRW/DRE: are open, ARB, SRN, SRK and SRS combine with DRE. ARL, SRD combine with DRW Satellites do not combine with other satellites except for SRK and SRS. SRK is primary. 1

4) Order of Opening: Primary positions as indicated in the table in part 3 shall be opened before splitting the position. Local Control (LC) 1) Area of Responsibility: a. MCO ATCT has responsibility for a 2 mile by 2 mile box as indicated in Annex 1 from SFC up to and including 2,000 MSL. The airspace immediately above is owned by SRD when open. 2

2) Active Runway Selection: a. Under most instances, MCO ATCT shall utilize southern operations. South Ops is the designated calm wind runways. b. When wind is less than 10 knots, utilize the calm wind runway configuration. c. The flows are as follows: i. South Ops: a) Departures- 1. Terminal Departures will utilize 18L and 17R. 2. West Ramp Departures will utilize 18R if traffic allows. b) Arrivals- 1. Arrivals will utilize 18R and 17L - Pilots or local control may request or suggest landing on the inner rails and is approved as traffic flow allows to reduce taxi time on the ground. ii. North Ops: a) Departures - 1. Terminal departures will utilize 36R and 35L 2. West ramp departures will utilize 36L if traffic allows. b) Arrivals - 1. Visual approaches to the west complex will utilize 36R*. During periods of high departure volume, 36L may be used. Pilots or Local Control may request or suggest landing on 36L to facilitate taxi to the west ramp (GA and cargo aircraft for example). Instrument approaches to west complex will utilize 36R. 2. Visual approaches to east complex will utilize 35R - Pilots or Local Control may request or suggest landing on 35L to reduce taxi time to the terminal. Instrument approaches to east complex will utilize 35R. *36R localizer available to facilitate joining final approach course. Most air carriers require crew to tune in localizer when available during a straight-in visual approach for backup in case of encountering IMC conditions during the approach. 3

d. Local control may opt to utilize a different runway configuration at their discretion but must coordinate changes with departure and wait for departure notification of readiness before executing the new runway configuration. e. Extreme caution should be exercised for departures from 18R/36L due to the close proximity of the parallel runway. f. Noise Abatement Operations 1. Noise Abatement procedures will remain in effect from 2300 until 0700 EST. 2. South Operation Local Control Deviations - NONE 3. North Operation Local Control Deviations - All aircraft departing to the north shall be given a heading of 060. 3) Runway Change Checklist: a. When changing runways, local control must verbally coordinate with the appropriate radar approach position(s) for the last departure/arrival off the previously used runway and the first departure/arrival off the newly selected active runway(s). b. Notify DRE of the new runway configuration and last departure and arrivals. c. When notified by DRE, stop all departures on the present configuration. d. Notify GCE and GCW of the new runway configurations and divert all departures to the new runways. e. When F11 is ready for the new configuration, DRE will notify LCE. Upon completion of notification, departures may resume with the new configuration. f. Ensure ATIS has been updated to reflect the new configuration. 4) Rolling Calls: a. When requested by F11, MCO ATCT shall ensure rolling calls are completed. Rolling calls can be completed via chat box, override, team speak or as otherwise coordinated and agreed upon. b. Rolling calls shall indicate the call sign, departure runway, first fix on the route or name of SID, and assigned departure heading. RH may be used to indicate runway heading. 5) Simultaneous Runway Use: a. Runway 36L and 36R may not be used for simultaneous instrument approaches. b. The ATIS shall indicate at all times Caution simultaneous approaches in use prior to stating the arrival runways. 4

6) IFR Departure Headings: 1. Orlando, McCoy and Jaguar Departures (Jet, Turboprop) a. Runway 18R/L Departures Gate Headings CAMDT/KLMAN/JAG 205 MCCOY/ATLAS/WORMS 140 b. Runway 17 R/L Departures Gate Headings CAMDT/KLMAN/JAG 220 MCCOY/ATLAS/WORMS 160 c. Runway 36 R/L Departures Gate Headings CAMDT/KLMAN 345-010 ATLAS 060 WORMS/JAG/MCCOY 010 d. Runway 35 R/L Departures Gate Headings CAMDT/KLMAN 345-010 ATLAS 060 WORMS/JAG/MCCOY 025-035 2. Citrus Departure (Piston) a. ALL RUNWAYS DTA Heading VIZTA (Northwest) 270 KLMAN (Southwest) 270 KNEED (Southwest) 270 TPSTR (Southeast) 090 WORMS (North) 270 5

7) Local Control Release Coordination: a. LW/LE must coordinate a departure sequence/release, from the other LC, for traffic that will transition to the other controller s airspace, in accordance with the following: 1. Request a release for aircraft routed via DRE or DRW sectors by stating the word REQUEST followed by the DTA identifier. As appropriate, use the word PROP, BOEING SEVEN FIVE SEVEN, or HEAVY. EXAMPLE Request VIZTA Prop. Request Heavy Worms. Request CAMDT. Request JAG Boeing Seven Five Seven. 2. Request a release for aircraft routed via Satellite airspace by stating REQUEST(assigned heading). EXAMPLE Request zero niner zero. 3. When a release is predicated on traffic, the LC position issuing the release shall reference only one aircraft positioned where it is obviously discernible from other aircraft on the movement area. The positions are limited to: 1) Holding short of the runway and number one for takeoff. 2) On the runway, holding in position. 3) On takeoff roll, midfield or airborne. b. The number of aircraft released by a single authorization is not limited. In the case of multiple releases, the LC position that has authorized the releases must be informed when the last departure is no longer a factor. EXAMPLE Follow the Boeing Seven Five Seven lifting off the Runway, to Worms released. c. When weather precludes the use of visual separation between an arrival to one LC position and a departure from the other LC position, the controller who issues the departure release must authorize the release by stating the word RELEASED, followed by the arriving traffic s call sign and position. PHRASEOLOGY RELEASED, TRAFFIC (aircraft call sign), (aircraft position). EXAMPLE Released, Traffic Delta Four Ten two mile final. 6

d. The LC position that has received a release clearance must ensure any potential conflict is resolved by visually observing the other local controller s runway and departure area prior to allowing an aircraft to start a turn that enters the other LC airspace. 8) Missed Approaches / Go Arounds / Practice Approaches: a. Assign runway heading and a climb to 3000 then hand off to the appropriate departure controller. b. Do not assign the published missed approach for instrument aircraft unless pilot requests or requested by the Arrival Radar sectors. c. Radar handoffs should be initiated as soon as practical. 9) Radar: a. MCO ATCT is a radar tower. It will receive radar handoffs from the Arrival Radar Monitor (ARM) position for aircraft inbound on final prior to the aircraft receiving approach clearance. b. MCO ATCT shall not terminate aircraft until they have completely landed at the airport. c. MCO ATCT shall radar identify VFR aircraft that will not need radar services from F11 and track the aircraft until they are clear of the ATCT airspace. This will only occur if the aircraft will remain below 900 ft to stay clear of the Class Bravo Airspace. This is usually a helicopter operation. ALL other VFR AND IFR aircraft must be handed off to Orlando departure. d. MCO ATCT shall not modify scratch pads or temporary altitudes of any aircraft. e. All piston aircraft departing the WEST complex shall be given a heading of 270. All piston aircraft departing the EAST complex shall be given a heading of 090. 10) VFR Departures: a. All VFR piston departures shall depart via the piston departure headings of 270 and 090 with an initial altitude of 1500 ft and handed off to Orlando Departure. b. VFR Aircraft may request flight following at the time of clearance delivery and VFF should be placed in the scratchpad. 11) Closed Traffic: a. GA aircraft may operate in the pattern at KMCO at or below 1500 ft. Typically RW 18R (Right Traffic) or 36L (Left Traffic) shall be utilized. All aircraft in the pattern should squawk a discrete beacon code. 12) Taxiways between runways: a. Local Controllers are responsible for all taxiways between the runways. 7

13) Contact / Monitor Operations: a. Local may request GC to instruct aircraft to monitor instead of contact LC. When these operations are in effect, GC will issue a point out to LC through the radar client after issuing the instruction to notify LC it has occurred unless another method is coordinated. 14) Approach Scratchpads: a. Uses a 3 letter format consisting of XYY where X identifies the type of approach and YY consists of the runway truncated to 2 characters. For example, runway 9 would be 09, runway 18R would be 8R and so on Type Localizer RNAV (GPS/RNP) ILS VOR Visual Overhead Break Letter L G I R V B 15) Line Up and Wait (LUAW) Procedures: a. Do not authorize a landing clearance to an aircraft requesting a full stop, touch and go, stop and go, option or low approach on the same runway with an aircraft that is holding position or taxiing to line up and wait until the aircraft in position starts the take off roll. b. Do not authorize an aircraft to LUAW if an aircraft has been cleared to land, touch and go, stop and go, option, or low approach on the same runway. c. Do not authorize multiple aircraft to LUAW on the same runway. Local Control East (LCE) 1) Responsibilities: a. LCE is the Tower Cab Supervisor and the primary local controller when combined operations. b. LCE is responsible for the east complex (Runway 35L/35R//17L/17R and all taxiways between). c. LCE is responsible for maintaining or delegating ATIS responsibilities. d. LCE may handle VFR transitions going east to west and shall issue a point out via VRC to LCW. 2) Position: a. Frequency: 118.450 b. Callsign: MCO_E_TWR [Combined: MCO_TWR] c. Relief Callsign: MCO_E1_TWR d. Position ID: 1T e. Symbol: T 8

Local Control West (LCW) 1) Responsibilities: a. LCW may handle VFR transitions going west to east and shall issue a point out via VRC to LCE. b. LCW is responsible for the west complex (Runway 36L/36R//18L/18R and all taxiways between). 2) Position: a. Frequency: 124.300 b. Callsign: MCO_W_TWR c. Relief Callsign: MCO_W1_TWR d. Position ID: 1S e. Symbol: T 9

GROUND CONTROL 1) Area of Responsibility: 2) Pushback and Startups: a. GC does not authorize push backs or start ups unless the aircraft pushing back will enter a controlled area during push back. I. In these instances, aircraft should be instructed Push back approved, push tail facing (direction) with direction keeping the aircraft pointed in the direction they will taxi. II. If the pilot calls to push and no controlled area will be penetrated, simply advise the pilot to Push at your discretion 10

3) ATIS: a. GC shall ensure pilots have the current ATIS or report have the numbers prior to communications transfer to LC. b. Aircraft that do not report the ATIS or numbers shall be instructed to: I. Monitor the ATIS and report the appropriate code. II. Be issued the departure runway, surface wind, and altimeter setting. 4) Runway Assignments: a. During period of light traffic, GC shall taxi aircraft to the nearest active departure runway. b. During periods of heavy load, LC will active the DRA (Departure Runway Assignments). These will involve taxiing an aircraft to the runway appropriate for their direction of flight, even if on the other side of the airfield. I. East Complex: ATLAS, WORMS, Jaguar SID (North OPS), McCoy SID, DABbound, MLB-bound. II. West Complex: CAMDT, KLMAN, Jaguar SID (South OPS), VIZTA, TPAbound, JAX-bound. III. All piston aircraft may depart from Runway 18R or 36L. 5) Transfer of Communications: a. During periods of normal traffic flows, GC shall instruct aircraft to Contact Tower (frequency) b. During periods of high traffic flows, LC may ask the GC to utilize monitor procedures. Aircraft, once clear of conflicts and established in their sequence, shall instruct aircraft to Monitor Tower (frequency). c. During Monitor Periods, GC shall utilize the radar client s point out feature to the appropriate LC to notify LC when a pilot has been given the monitor instruction. Ground Control East (GCE) 1) Responsibilities: a. Responsible for all ramps from the centerline of the airport to the east, with the exception of any taxiways between the parallels as depicted above. 2) Position: a. Frequency: 126.400 b. Callsign: MCO_E_GND c. Relief Callsign: MCO_E1_GND d. Position ID: 1Y e. Symbol: Not Applicable 11

Ground Control West (GCW) 1) Responsibilities: a. Responsible for all ramps from the centerline of the airport to the west and the ramps on the west side of 36L/18R, with the exception of any taxiways between the parallels as depicted above. b. Primary Ground Control Position. 2) Position a. Frequency: 121.800 b. Callsign: MCO_W_GND [Combined: MCO_GND] c. Relief Callsign: MCO_W1_GND d. Position ID: 1G e. Symbol: Not Applicable 12

Clearance Delivery (CD) 1) Responsibilities: a. Issue/Relay ATC Clearances to all departing aircraft, both VFR and IFR. 2) Position: a. Frequency: 134.700 b. Callsign: MCO_DEL c. Relief Callsign: MCO_1_DEL d. Position ID: 1D e. Symbol: Not Applicable 3) IFR Departure Instructions: a. Departure Transition Areas (DTA's) shall always be assigned to departing aircraft and inserted in the routing. The following lists the departure transition areas (DTAs) and the next fix of their route. Table 3-1. Departure Transition Areas (DTAs) Orlando Departure (Turbojet/Turboprop) DTA CAMDT (West) KLMAN (Southwest) ATLAS (Southeast) WORMS (North) Associated Fix CTY, SZW, OCF, KNOST, BULZI, HEVVN, RSW, SRQ, CYY MLB,TRV, PBI, FLL TAY, CRG, OMN, SGJ, SSI Citrus Departure (Piston Only) DTA VIZTA (Northwest) KLMAN (Southwest) KNEED (Southwest) TPSTR (Southeast) WORMS (North) Associated Fix CTY, SZW, OCF, BULZI, HEVVN RSW, SRQ, CYY PIE, MCF, LAL TRV, PBI, FLL, MLB, PHK TAY, CRG, OMN, SGJ, SSI 13

I. Aircraft with none of the above as their first fixes shall use the departure gate closest to their first fix so long as the fix is outside of the F11 airspace. Example, if an aircraft files direct to PAM shall be routed through CAMDT if a Jet, or VIZTA if a Prop. II. Jets or Turboprops destined for Savannah or Cecil may receive the Jaguar or McCoy departures in lieu of the departure gate. b. Instruct all pilots fo turbojet and turboprop aircraft to maintain 5000 and to expect filed cruise altitude (if higher) 10 minutes after departure. Instruct IFR Piston aircraft to maintain 1500 and to expect filed cruise altitude (if higher) 10 minutes after departure. Substitute 5000 or 1500 for lower if an aircraft s IFR cruise altitude is filed for lower. c. Issue the departure frequency as follows: I. Jet/Turboprop DRE ATLAS, WORMS, JAGUAR (NORTH OPS), MCCOY. DRW CAMDT, KLMAN, JAGUAR (SOUTH OPS) If satellite radars are open: Aircraft filed at an altitude below 5000 shall receive SRN as their departure frequency during north flow. During south operations, aircraft that would otherwise go to DRE shall be given SRK s frequency for departure and DRW would receive SRD s frequency for departure. II. Piston SRD - VIZTA, KLMAN, KNEED, WORMS SRK TPSTR If satellite radars are closed, SRD shall be given DRW s frequency and SRK shall be given DRE s frequency. d. Assign a beacon code 4) VFR Departure Instructions: a. Clear the aircraft into the Orlando Class Bravo airspace. b. Instruct piston aircraft to MAINTAIN VFR at or below 1,500. Jet/turboprops shall MAINTAIN VFR at or below 5000. c. VFR to the West shall be given SRD s frequency (DRW or DRE depending on where combined). VFR to the east shall be given SRK s frequency (or DRE if not open). VFR to the south should be given SRD s frequency (DRW if SRD closed or DRE if SRD and DRW are closed). If on the west complex, or SRK s frequency (or DRE if SRK closed) if on the east complex. VFR to the north shall be given SRN s frequency (DRE if SRN closed). d. GA aircraft requesting closed traffic shall be given a squawk code. 5) Ground Stops: 14

a. If Ground Stops are in effect, inform the aircraft after issuance of clearance and acknowledgement that there is a ground stop in effect and to monitor the Clearance Delivery frequency for further instructions. I. Ensure you inform the aircraft their EDCT (Estimated Departure Clearance Time), if known, as well as the cause for Ground Stops. b. GC will notify CD when the aircraft can expect to taxi, relay this to the pilot. Once the aircraft is released from the Ground Stop, notify the aircraft Push and Start Approved. Contact ground (frequency) for taxi. 6) Scratchpads: a. To assist the departure controllers, CD shall ensure the following scratchpads are set in a pilot s flight plan only after the clearance has been issued to notify the Departure Controller of an active flight plan. Departure Gate SID, TRACON, Airport MCCOY JAG CAMDT KLMAN ATLAS KNEED WORMS TPSTR VIZTA Jacksonville ATCT Daytona ATCT Tampa TRACON Orlando Executive Sanford Melbourn Kissimmee Leesburg County VFR No Flight Following VFR Flight Following Scratchpad Entry M J C K A N W T V JA DA TA ORL SFB MLB ISM LEE (None) VFF Appendix A. Radar Identifiers for Interfacility Handoffs 15

F11 Complex ATCTs CALLSIGN FREQUENCY ID TAG MCO_E_TWR 118.450 1T T MCO_W_TWR 124.300 1S T DAB ATCTs CALLSIGN FREQUENCY SECTOR DESC. ID TAG DAB_H_APP 125.720 High 5H 5 DAB_L_APP 127.070 Lamma (Mid South) 5L 5 DAB_M_APP 118.850 Mateo (Mid North) 5M 5 DAB_F_APP 125.800 Final 5F 5 JAX ATCTs CALLSIGN FREQUENCY SECTOR DESC. ID TAG JAX_N_APP 119.000 North Sector 3N N JAX_S_APP 118.000 South Sector 3S S JAX_J_APP 119.850 Final 3J J JAX_L_APP 124.900 Satellite 3L L JAX_V_APP 118.600 Vitts 3V V TPA ATCTs CALLSIGN FREQUENCY SECTOR DESC. ID TAG TPA_B_DEP 135.500 East Departure 9B 9 TPA_D_DEP 118.800 West Departure 9D 9 TPA_G_DEP 134.250 South Departure 9G 9 TPA_E_APP 118.150 East Arrival 9E 9 TPA_F_APP 118.500 TPA Final 9F 9 TPA_L_APP 119.900 East Satellite 9L 9 TPA_M_APP 126.000 MacDill 9M 9 TPA_P_APP 125.300 West Satellite 9P 9 TPA_R_APP 120.650 Lakeland Low 9R 9 TPA_S_APP 119.650 South Satellite 9S 9 TPA_W_APP 132.520 West Arrival 9W 9 Appendix A. Radar Identifiers for Interfacility Handoffs 16

ZJX EN-ROUTE CALLSIGN FREQUENCY SECTOR DESC. ID TAG JAX_10_CTR (PRI) 135.050 METTA LOW C10 C JAX_13_CTR 134.450 ASHBURN LOW C13 C JAX_15_CTR 133.320 OCALA LOW C15 C JAX_30_CTR 124.770 NEPTA HIGH C30 C JAX_33_CTR 134.850 TORRY HIGH C33 C ZMA EN-ROUTE CALLSIGN FREQUENCY ID TAG MIA_3_CTR (PRI) 132.250 M03 M MIA_17_CTR 128.650 M17 M MIA_22_CTR 133.470 M22 M MIA_23_CTR 126.950 M23 M MIA_64_CTR 126.520 M64 M MIA_65_CTR 125.070 M65 M MIA_67_CTR 127.200 M67 M For use with the F11 Pro POF. Sector IDs will be different for ATCT positions in the primary. Appendix B. Video Map Descriptions 17

NAME DESCRIPTION 000 AIRPORT DIAGRAM Ground Layout for MCO ATCT for use by GC and CD 001 SAT NORTH Satellite Radar Map when MCO is in North Operations 002 SAT SOUTH Satellite Radar Map when MCO is in South Operations 003 ORLANDO AREA FINALS Extended Runway Centerlines for primary airports in F11 complex 005 MCO FINAL NTZ MCO Non-Transgression Zone Markings 006 VFR MAP Lakes and Major Highways 008 MCO TWR MAP Major Markings meant for MCO ATCT use 009 LOW AIRWAY MAP A map of all the low altitude airways 001 SAT NORTH Satellite Radar Map when MCO is in North Operations 002 SAT SOUTH Satellite Radar Map when MCO is in South Operations 003 ORLANDO AREA FINALS Extended Runway Centerlines for primary airports in F11 complex 010 GPS MAP Map of GPS approaches 011 HIGH AIRWAY MAP Map of all high altitude airways 013 AIRPORTS Draws all the airports within the F11 Complex 014 ARL/ARB SOUTH OPS Advanced markings for ARL/ARB when MCO is in South Operations 015 ARL/ARB NORTH OPS Advanced markings for ARL/ARB when MCO is in North Operations 016 MCO MVA The MVA for when the radar antenna is located at KMCO 018 ARR SOUTH OPS SIMPLE Simple Markings for ARL/ARB when MCO is in South Operations 019 ARR NORTH OPS SIMPLE Simple Markings for ARL/ARB when MCO is in North Operations 021 ILS Fixes Shows the ILS Fixes for F11 complex airports 022 MCO FINAL MONITOR Final Control airspace 023 STN BASE SFB RWY 9 Simple markings for STD/STN when SFB Rwy 9 and MCO North Flow 024 STN BASE SFB RWY 27 Simple markings for STD/STN when SFB Rwy 27 and MCO North Flow 026 DEP RDR NORTH FLOW Departure Radar Map for MCO North Operations 027 DEP RDR SOUTH FLOW Departure Radar Map for MCO South Operations 028 STD BASE EAST FLOW Simple markings for STD/STN when SFB Rwy 9 and MCO South Flow 029 STD BASE WEST FLOW Simple markings for STD/STN when SFB Rwy 27 and MCO South Flow 030 FINAL NORTH OPS ARM Markings when MCO is in North Operations 031 FINAL SOUTH OPS ARM Markings when MCO is in South Operations 033 ORL RWY 7 Executive Rwy 7 extended centerlines 034 ORL RWY 27 Executive Rwy 27 extended centerlines 040 HIGHWAY MAP Draws all major roads and highways 042 ORL CLASS AIRSPACE Draws Class B/C and Executive Class D airspaces 060 RNAV ARR POINTS Draws fixes for all RNAV Arrivals 062 RNAV DEP POINTS Draws fixes for all RNAV Departures 999 COASTLINE Draws detailed coastline Appendix C. MCO ATCT Scratchpads 18

Approach Scratchpads Uses a 3 letter format consisting of XYY where X identifies the type of approach and YY consists of the runway truncated to 2 characters. For example, runway 9 would be 09, runway 18R would be 8R and so on. Type Localizer RNAV (GPS/RNP) ILS VOR TACAN NDB Visual Overhead Break Letter L G I R T N V B Departure Scratchpads Departure Gate, SID, TRACON, ATCT, Airport MCCOY JAG CAMDT (EXCEPT LAL/KNOST) KLMAN ATLAS KNEED WORMS TPSTR Jacksonville ATCT Daytona ATCT Tampa TRACON Orlando Executive Sanford Melbourne Kissimmee Leesburg County VFR No Flight Following VFR Flight Following Scratchpad Entry M J C K A N W T JA DA TA ORL SFB MLB ISM LEE (none) VFF 19