| Position | Callsign | Radio Name | Frequency | Identifier |
|---|---|---|---|---|
| Clearance Delivery | FRG_DEL | Republic Clearance Delivery | 128.250 | 2P |
| Ground | FRG_GND | Republic Ground | 121.600 | 2N |
| Tower | FRG_TWR | Republic Tower | 118.800 | 2M |
| ATIS | KFRG_ATIS | 126.650 |
No edit summary |
m (→Clearance Delivery: fix CD > LOA) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{SOPHeader | {{SOPHeader | ||
|Facility=FRG | |Facility=Republic Airport (FRG) | ||
|Version=5 | |Version=5 | ||
}} | }} | ||
| Line 9: | Line 9: | ||
|- | |- | ||
{{TableHeaders-Airports}} | {{TableHeaders-Airports}} | ||
|- | |||
| {{TableRow-Airport | | {{TableRow-Airport | ||
|Ident=KFRG | |Ident=KFRG | ||
|Name=Republic Airport | |Name=Republic Airport | ||
|Class=D | |Class=D | ||
}} | }} | ||
|} | |} | ||
| Line 365: | Line 364: | ||
|SHIPP Y492 SQUAD | |SHIPP Y492 SQUAD | ||
|} | |} | ||
</div> | </div> | ||
|-|LOA Routes= | |-|LOA Routes= | ||
Routing to certain airports in ZNY, ZDC and ZBW ARTCCs is pre-coordinated through letters of agreement (LOA). These routes have been added to the | Routing to certain airports in ZNY, ZDC and ZBW ARTCCs is pre-coordinated through [[LOA|letters of agreement (LOA)]]. These routes have been added to the [[PRD|Preferred Route Database (PRD)]]. | ||
| Line 383: | Line 380: | ||
{{phraseology|syntax=Cleared to (destination), Republic (Version #) Departure, radar vectors (exit); then, as filed..}} | {{phraseology|syntax=Cleared to (destination), Republic (Version #) Departure, radar vectors (exit); then, as filed..}} | ||
Because this departure procedure does not have published altitude restrictions, the phrase "Maintain (initial altitude)" must be included in the IFR clearance, as explained in | Because this departure procedure does not have published altitude restrictions, the phrase "Maintain (initial altitude)" must be included in the IFR clearance, as explained in {{Reference7110|chapter=4|section=3|reference=4-3-2}}. | ||
====DEEZZ# ==== | ====DEEZZ# ==== | ||
| Line 421: | Line 418: | ||
{{phraseology|syntax=Cleared to (clearance limit), DEEZZ (Version #) Departure, (climb procedure as applicable), (CANDR or TOWIN) transition; then, as filed..}} | {{phraseology|syntax=Cleared to (clearance limit), DEEZZ (Version #) Departure, (climb procedure as applicable), (CANDR or TOWIN) transition; then, as filed..}} | ||
Because this departure procedure does not have published altitude restrictions, the phrase "Maintain (initial altitude)" must be included in the IFR clearance, as explained in {{Reference7110|chapter=4|section=3|reference=4-3-2}}. | |||
====No SID ==== | ====No SID ==== | ||
| Line 446: | Line 443: | ||
</tabber> | </tabber> | ||
=== Ground === | === Ground === | ||
| Line 482: | Line 478: | ||
* Advise LC when helicopters will operate on or adjacent to movement areas. Helicopter operations may be conducted at any point on the airport, in movement and non-movement areas, contingent upon traffic conditions, airport conditions, and the issuance of proper instructions to all aircraft affected. | * Advise LC when helicopters will operate on or adjacent to movement areas. Helicopter operations may be conducted at any point on the airport, in movement and non-movement areas, contingent upon traffic conditions, airport conditions, and the issuance of proper instructions to all aircraft affected. | ||
* Maintain awareness of any aircraft that may have taxied into an Area of Non-Visibility from the Tower. The movement areas in this category are the run-up areas on Taxiway Alpha adjacent to the approach end of runways 14 and 32. | * Maintain awareness of any aircraft that may have taxied into an Area of Non-Visibility from the Tower. The movement areas in this category are the run-up areas on Taxiway Alpha adjacent to the approach end of runways 14 and 32. | ||
* Assist LC to ensure all runway exiting is in accordance with | * Assist LC to ensure all runway exiting is in accordance with {{Reference7110|chapter=3|section=10|reference=3-10-9}} | ||
** Ensure that proper coordination is accomplished with LC to protect a taxiway/runway/ramp, if an aircraft is required to enter that intersection to clear the landing runway. | ** Ensure that proper coordination is accomplished with LC to protect a taxiway/runway/ramp, if an aircraft is required to enter that intersection to clear the landing runway. | ||
** GC may have to hold an aircraft short of the runway intersection, if it is known where an aircraft will be exiting the runway. | ** GC may have to hold an aircraft short of the runway intersection, if it is known where an aircraft will be exiting the runway. | ||
* Protect ILS Critical Area in accordance with | * Protect ILS Critical Area in accordance with {{ExtLink_FAA7110}}. Hold Position Lines and proper signage are located on the Charlie Taxiway defining the boundary of the Glide Slope Critical Area. The only critical area at Farmingdale is located on all of taxiway Echo, and taxiway Charlie between Echo and Runway 14-32. | ||
* Do not authorize aircraft operations in or over the area when an arriving aircraft inbound on the ILS 14 is inside the ILS OM (FRIKK - 3.9 DME from the runway threshold) unless the arriving aircraft has reported the runway in sight or is circling to land on another runway when the official weather observation indicates a ceiling of less than 800 feet or visibility less than 2 miles. | * Do not authorize aircraft operations in or over the area when an arriving aircraft inbound on the ILS 14 is inside the ILS OM (FRIKK - 3.9 DME from the runway threshold) unless the arriving aircraft has reported the runway in sight or is circling to land on another runway when the official weather observation indicates a ceiling of less than 800 feet or visibility less than 2 miles. | ||
{{phraseology|syntax=Hold short of runway 14 ILS critical area.}} | {{phraseology|syntax=Hold short of runway 14 ILS critical area.}} | ||
| Line 622: | Line 618: | ||
* Missed approaches or go-arounds shall fly runway heading or track the localizer until reaching the departure end of the runway, then be issued a heading in accordance with the table unless the controller determines that it would be advantageous to delay or initiate a turn early. | * Missed approaches or go-arounds shall fly runway heading or track the localizer until reaching the departure end of the runway, then be issued a heading in accordance with the table unless the controller determines that it would be advantageous to delay or initiate a turn early. | ||
* In order to prevent increased workload on Departure Control, consider issuing missed approaches or go-arounds speed restrictions in accordance with | * In order to prevent increased workload on Departure Control, consider issuing missed approaches or go-arounds speed restrictions in accordance with {{ExtLink_FAA7110}}. | ||
* Coordinate all IFR go arounds with N90/JFK sector as soon as possible and hand off when Local Control traffic is not a factor. | * Coordinate all IFR go arounds with N90/JFK sector as soon as possible and hand off when Local Control traffic is not a factor. | ||
* Issue control instructions as necessary to establish separation and avoid arriving aircraft from overflying departing aircraft or aircraft on the runway. Consider wake turbulence, runway configuration, traffic pattern flows, weather conditions, slow rolling departures, and type of approach in use. Deviate as necessary from the following headings and altitudes if using them would compromise safety. | * Issue control instructions as necessary to establish separation and avoid arriving aircraft from overflying departing aircraft or aircraft on the runway. Consider wake turbulence, runway configuration, traffic pattern flows, weather conditions, slow rolling departures, and type of approach in use. Deviate as necessary from the following headings and altitudes if using them would compromise safety. | ||
| Line 689: | Line 685: | ||
==Letters of Agreement == | ==Letters of Agreement == | ||
= | <showhide title="New York TRACON (N90) & Republic Tower (FRG)"> | ||
{{:LOA/N90_FRG}} | |||
</showhide> | |||
Latest revision as of 05:01, 13 January 2026
Rev. 5 — Revised: 2026-01-13
Area at a glance
| ICAO Code | Airport Name | Airspace |
|---|---|---|
| KFRG | Republic Airport | D |
- Purpose
- This document prescribes the procedures to be utilized for providing air traffic control services at Republic Air Traffic Control Tower (ATCT). The procedures described herein are supplemental to the New York ARTCC Standard Operating Procedures and FAA Order JO 7110.65.
- Distribution
- This order is distributed to all New York ARTCC personnel.
- Procedural Deviations
- Exceptional or unusual requirements may dictate procedural deviations or supplementary procedures to this order. A situation may arise that is not adequately covered herein; in such an event use good judgment to adequately resolve the problem.
Operational Positions
| Sector | Callsign | Frequency | Identifier | Combined Sector |
|---|---|---|---|---|
| LaGuardia Departure | LGA_DEP | 120.400 | 1L | Primary Departure |
| HAARP | LGA_V_APP | 120.800 | 1V | Primary Approach (LGA_APP when combined) |
| Final Vector | LGA_F_APP | 134.900 | 1F | 1V |
| NYACK | LGA_Y_DEP | 120.550 | 1Y | 1X (1L if NOBBI is not covered) |
| EMPYR | LGA_D_APP | 127.300 | 1D | 1V |
| NOBBI | LGA_X_APP | 126.400 | 1X | 1V |
| Sector | Callsign | Frequency | Identifier | Combined Sector |
|---|---|---|---|---|
| Final Vector | JFK_A_APP | 132.400 | 2A | 2K |
| CAMRN | JFK_G_APP | 128.125 | 2G | 2K |
| Kennedy Departure | JFK_DEP | 135.900 | 2J | Primary Departure |
| ROBER | JFK_K_APP | 125.700 | 2K | Primary Approach (JFK_APP when combined) |
| Kennedy Satellite | JFK_M_APP | 118.400 | 2M | 2K |
| Sector | Callsign | Frequency | Identifier | Combined Sector |
|---|---|---|---|---|
| Calverton | ISP_N_APP | 120.050 | 3N | Primary TRACON (ISP_APP if combined) |
| Islip | ISP_H_APP | 134.550 | 3H | 3N |
| SEALL | ISP_R_APP | 133.100 | 3R | 3N |
| VIKKY | ISP_O_APP | 128.625 | 3O | 3N |
| LOVES | ISP_Z_APP | 124.075 | 3Z | 3N |
| BEADS Low | ISP_I_APP | 118.950 | 3I | 3N |
| BEADS High | ISP_B_APP | 125.975 | 3B | 3N |
| Sector | Callsign | Frequency | Identifier | Combined Sector |
|---|---|---|---|---|
| Newark Departure | EWR_DEP | 119.200 | 4N | Primary Departure |
| Yardley | EWR_P_APP | 128.550 | 4P | Primary Approach (EWR_APP when combined) |
| Final Vector 22 | EWR_M_APP | 125.500 | 4M | 4P |
| Final Vector 4 | EWR_Q_APP | 125.500 | 4Q | 4P |
| North Arrival | EWR_A_APP | 120.150 | 4A | 4P |
| MUGZY | EWR_U_APP | 127.600 | 4U | 4P |
| ZEEBO | EWR_S_APP | 123.775 | 4S | 4U |
| METRO | EWR_H_APP | 132.800 | 4H | 4U |
| Sector | Callsign | Frequency | Identifier | Combined Sector |
|---|---|---|---|---|
| East | NY_LE_DEP | 126.800 | 5E | 5W |
| West | NY_LW_DEP | 120.850 | 5W | Primary TRACON (NY_L_APP when combined and covering Catskill) |
| North | NY_LN_DEP | 118.175 | 5T | 5W |
| South | NY_LS_DEP | 124.750 | 5S | 5W |
| Catskill | SWF_APP | 132.750 | 5H | 5W |
ATCT
Clearance Delivery
| Exit Gate | Exit | Scratchpad | Radial |
|---|---|---|---|
| North | SAX | SAX | |
| COATE | COA | SAX 311 | |
| NEION | NEI | LGA 322 | |
| HAAYS | HAY | HUO 145 | |
| GAYEL | GAY | DPK 320 | |
| DEEZZ | DEZ | DPK 324 | |
| East | GREKI | GRE | CMK 057 |
| MERIT | MER | LGA 055 | |
| BAYYS | BAY | BDR 054 | |
| BDR | BDR | ||
| Southwest LGA refers to these as "South" |
DIXIE | DIX | JFK 222 |
| WHITE | WHI | JFK 222 | |
| RBV | RBV | ||
| ARD | ARD | ||
| Water | BETTE | BET | JFK 109 |
| HAPIE | HAP | JFK 124 | |
| SHIPP | SHI | JFK 139 | |
| WAVEY | WAV | JFK 156 |
Notes
- Although JFK VOR is listed as a valid exit on REP# departure procedure, it can only be used in conjunction with a Southwest Gate exit, e.g. JFK V1 DIXIE...
| Position | Frequency | Identifier |
|---|---|---|
| JFK_S_APP | 118.400 | 2S |
| JFK_R_APP | 125.700 | 2K |
| JFK_APP | 128.125 | 2G |
| NY_CTR | 125.325 | N56 |
The table on the right lists the common frequencies used as departure frequency by FRG Clearance Delivery. The first available controller in this list should be handling departures.
Note that this table only serves as a guide. The actual departure frequency has to be determined based on coordination with the other online controllers.
If there is no other controller online that would accept departures from FRG, advise the pilot that they should use the appropriate CTAF frequency upon departure.| Airway | Join |
|---|---|
| T224 | DIXIE T224 |
| V249 | SAX V249 |
| V252 | HAAYS HUO V252 |
| V276 | DIXIE V276 |
| V30 | SAX V249 SBJ V30 |
| J110 | RBV Q430 AIR J110 |
| J132 | NEION J223 CORDS J132 |
| J223 | NEION J223 |
| J48 | RBV Q430 BYRDD J48 |
| J6 | RBV Q430 SAAME J6 |
| J60 | DEEZZ# CANDR J60 |
| J95 | GAYEL J95 |
| L453 | SHIPP Y488 SAUCR L453 |
| L454 | SHIPP Y490 ROLLE ATUGI L454 |
| L455 | SHIPP Y489 RESQU SKPPR L455 |
| L456 | SHIPP Y482 SQUAD DARUX L456 |
| L457 | SHIPP Y489 RESQU SKPPR L457 |
| L459 | SHIPP Y482 SQUAD DARUX L459 |
| L461 | SHIPP Y487 KINGG KINER L461 |
| L462 | SHIPP Y483 ISLES KAYYT L462 |
| Q167 | WAVEY EMJAY Q167 |
| Q409 | WHITE Q409 |
| Q430 | RBV Q430 |
| Q436 | COATE Q436 |
| Q480 | RBV Q430 AIR Q480 |
| Q75 | RBV Q430 COPES Q75 |
| Q812/Q818 | GAYEL Q812/Q818 |
| Y483/Y487/Y488/
Y489/Y490/Y492 |
SHIPP Y4## |
| Filed Exit | Amendment |
|---|---|
| ACK | BETTE ACK |
| BOS | MERIT HFD PUT BOS |
| BYRDD | RBV Q430 BYRDD |
| CFB | GAYEL J95 CFB |
| COPES | RBV Q430 COPES |
| EMI | RBV Q430 BYRDD J48 EMI |
| EMJAY | WAVEY EMJAY |
| ENE | GREKI JUDDS MARTN ENE |
| HNK | GAYEL Q812 HNK |
| HUO | HAAYS HUO |
| JUDDS | GREKI JUDDS |
| KINGG | SHIPP Y487 KINGG |
| LRP | RBV Q430 SAAME J6 LRP |
| MARTN | GREKI JUDDS MARTN |
| MXE | RBV Q430 COPES Q75 MXE |
| PSB | DEEZZ# CANDR J60 PSB |
| PTW | RBV Q430 BYRDD J48 PTW |
| PUT | MERIT HFD PUT |
| RESQU | SHIPP Y489 RESQU |
| ROLLE | SHIPP Y490 ROLLE |
| SAAME | RBV Q430 SAAME |
| SQUAD | SHIPP Y492 SQUAD |
Routing to certain airports in ZNY, ZDC and ZBW ARTCCs is pre-coordinated through letters of agreement (LOA). These routes have been added to the Preferred Route Database (PRD).
The initial altitude for IFR departures is 3,000’. If Kennedy is on the 22's configuration, the initial altitude for IFR departures becomes 2,000'. Use the tabs below to access information about various departure procedures, their climbs, and proper initial altitude phraseology.
REP#
This is the default departure procedure to be used by aircraft departing Republic (pronounced Republic (Version #), such as Republic One). It should always be assigned, unless the pilot indicates not possessing charts, or they meet the requirements for the DEEZZ# departure.
Cleared to (destination), Republic (Version #) Departure, radar vectors (exit); then, as filed..
Because this departure procedure does not have published altitude restrictions, the phrase "Maintain (initial altitude)" must be included in the IFR clearance, as explained in FAA Order JO 7110.65 § 4-3-2.
DEEZZ#
| Airway | Transition |
|---|---|
| J60 | CANDR J60 |
| J64 | CANDR J60 DANNR RAV J64 |
| Q480 | CANDR Q480 |
| J42 | CANDR Q480 SPOTZ Q42 |
| J6 | TOWIN J6 (TMU only) |
This DP is only used for RNAV equipped turbojet aircraft that are filed for J60, J64, Q480, Q42, or J6 (with a destination located south of the Potomac TRACON or to Cleveland-Hopkins International [KCLE] or Midway [KMDW]). Non-RNAV turbojet departures filed J6 (with a destination located south of the Potomac TRACON or to Cleveland-Hopkins International [KCLE] or Midway [KMDW]) should be routed via RBV SAAME J6.
The DEEZZ# has required climb instructions off of runways 4L and 13L/R - see the Climb Procedures tab for more information.
Note about J6: The DEEZZ# is only assigned to aircraft routed to J6 under the following conditions:
- A heavy flow of traffic simultaneously going to RBV
- Dangerous and/or severe weather in the vicinity of RBV Q430 SAAME (SWAP in effect, see appendix for more information).
TMU makes the final decision regarding J6 reroutes. Unless told otherwise by TMU, and during normal operations, the pilot should be routed via RBV Q430 SAAME J6 ...
This DP has two transitions: CANDR (which is on both J60 and Q480) and TOWIN (which is on J6). Aircraft should be routed to the appropriate transition, and route string if needed, according to the table on the right.
Cleared to (clearance limit), DEEZZ (Version #) Departure, (climb procedure as applicable), (CANDR or TOWIN) transition; then, as filed..
Because this departure procedure does not have published altitude restrictions, the phrase "Maintain (initial altitude)" must be included in the IFR clearance, as explained in FAA Order JO 7110.65 § 4-3-2.
No SID
When a SID is not issued, assign the following headings:
RWY 32/1 - heading 010
RWY 14/19 - heading 220
Cleared to (destination), fly heading (heading) for vectors to (exit); then as filed...
Departing FRG Airspace Into New York Class B
If an aircraft indicates that they would eventually like to be cleared into the New York Class Bravo airspace, then Republic Tower should instruct the pilot to depart to the north or south, remain clear of the Class Bravo airspace, and contact the appropriate New York Approach Control frequency.
Do NOT issue a New York Class Bravo clearance since FRG is not an authorized Class B controlling agency. While filing a flight plan is not required, it can be useful to later ATC. Request that the pilot file a quick VFR flight plan with the departure and arrival airports, requested VFR cruising altitude, and route of flight.
Pattern Work or Departure Outside New York Class B
No squawk code need be assigned to these aircraft. Even though a discreet squawk code is not required for aircraft operating in the pattern or outside of the New York Class Bravo, they must still Squawk Mode C as FRG resides within the 30 nm Mode C Veil.
Advise the pilot to contact Ground Control with his or her request. If the pilot’s plan is to depart the area, ensure they state requested direction of flight.Ground
- Departure Sequencing
| Exit Gate | Exits |
|---|---|
| North | COATE, NEION, HAAYS, GAYEL, DEEZZ, SAX |
| East | GREKI, MERIT, BAYYS, BDR |
| Southwest | WHITE, DIXIE, RBV, ARD |
| West | BETTE, HAPIE, SHIPP, WAVEY |
- Aircraft should be sequenced to depart in the following order:
- By alternating gate group.
- If not the above, then by alternating exit.
- If not the above, then by aircraft type largest to smallest.
Duties and Procedures
- Assist LC in scanning runways, especially during periods of heavy traffic, two runway operation, and unfamiliar aircraft taxiing in close proximity to the active runway.
- Coordinate with LC to obtain specific approval prior to permitting an aircraft to cross or enter a runway designated as active.
- Assign departure runways and intersection departures that will facilitate the most expeditious movement of traffic.
- Advise LC when helicopters will operate on or adjacent to movement areas. Helicopter operations may be conducted at any point on the airport, in movement and non-movement areas, contingent upon traffic conditions, airport conditions, and the issuance of proper instructions to all aircraft affected.
- Maintain awareness of any aircraft that may have taxied into an Area of Non-Visibility from the Tower. The movement areas in this category are the run-up areas on Taxiway Alpha adjacent to the approach end of runways 14 and 32.
- Assist LC to ensure all runway exiting is in accordance with FAA Order JO 7110.65 § 3-10-9
- Ensure that proper coordination is accomplished with LC to protect a taxiway/runway/ramp, if an aircraft is required to enter that intersection to clear the landing runway.
- GC may have to hold an aircraft short of the runway intersection, if it is known where an aircraft will be exiting the runway.
- Protect ILS Critical Area in accordance with FAA Order JO 7110.65. Hold Position Lines and proper signage are located on the Charlie Taxiway defining the boundary of the Glide Slope Critical Area. The only critical area at Farmingdale is located on all of taxiway Echo, and taxiway Charlie between Echo and Runway 14-32.
- Do not authorize aircraft operations in or over the area when an arriving aircraft inbound on the ILS 14 is inside the ILS OM (FRIKK - 3.9 DME from the runway threshold) unless the arriving aircraft has reported the runway in sight or is circling to land on another runway when the official weather observation indicates a ceiling of less than 800 feet or visibility less than 2 miles.
Hold short of runway 14 ILS critical area.
Tower
Tower Procedures
- Releases
- Releases from Republic are requested per aircraft, unless N90 permits blanket releases.
- In order to depart Republic under an IFR flight plan, TRACON must issue a release for departure. Departure restrictions such as release times and clearance void times are necessary to separate departures from other traffic in the airspace or to regulate the departure flow. Through land line communications, tower will obtain a release from TRACON for a specific flight after which tower can then issue departure instructions and takeoff clearance.
- Separation
- The standard departure separation technique to be used is anticipated radar separation. Only use timed separation if the pilot requests it.
- Radar
- This tower uses a RACD radar only and is not certified for any approach control services. By agreement with New York TRACON, this tower will NOT radar identify departing IFR aircraft and will instruct a departure to contact departure control once the aircraft appears to be clear of any traffic. It is imperative that tower controllers observe departing traffic turning towards the assigned heading before handing off. VFR aircraft can and must be radar identified to receive flight following within the tower's airspace, otherwise it is not necessary.
- Operating Hours
- Normal opening time is 0700 Local time. Normal closing time is 2300 Local time.
- Helipads
- H1 located on Taxiway Bravo at the intersection of Taxiway Foxtrot. H2 located on Taxiway Bravo north of Taxiway Bravo-4.
- Land and Hold Short Operations (LAHSO)
LAHSO may be conducted as long as these conditions are met:
- At least 3 miles visibility
- At least 1,000' ceiling
- No wind shear has been reported
- The LAHSO runway must be dry
- The tailwind on the hold short runway must be calm (less than 3 knots)
- An announcement shall be made in the ATIS (Example: "LAHSO in effect")
- LAHSO may be conducted with this configuration
- Land runway 32, hold short of Runway 01-19. ALD 3650’.
- Line Up and Wait (LUAW) Operations
LUAW may be conducted as long as these conditions are met:
- There are no emergencies inbound to the airport
- The local position is not combined with a non-local position (i.e. ground control or clearance delivery)
- No procedures that require a safety logic system - FRG does not have one
- LUAW cannot be conducted at an intersection between sunset and sunrise
- LUAW must not be conducted when the takeoff position is not visible from the tower or during IFR conditions
- Aircraft Exiting the Runway
- Instruct aircraft where to exit the runway after landing and, where appropriate, advise the aircraft to hold short of a runway or taxiway for traffic. Use caution in areas where the runway hold position markings are in close proximity to the runway (i.e. taxiways Bravo and Gulf).
Runway Selection
| Wind Speed | Direction | Depart | Land |
|---|---|---|---|
| 0-4 | Any | 19 | 19 |
| 5+ | 080-150 | 14 | 14 |
| 151-260 | 19 | 19 | |
| 261-340 | 32 | 32 | |
| 341-079 | 1 | 1 |
Departure Headings (IFR)
- For IFR traffic that has filed REP# or DEEZZ# departure procedures, departure heading is published on the DP. Nevertheless, repeat the departure heading at the time you are clearing them for takeoff (see table below).
- For IFR traffic that is not flying a REP# or DEEZZ#, issue the following headings as part of the takeoff clearance.
| Runway | Heading |
|---|---|
| 1 | 010 |
| 14 | 220 |
| 19 | 220 |
| 32 | 010 |
| Runway | Heading | Altitude |
|---|---|---|
| 1 | 010 | 2000 |
| 14 | 220 | 2000 |
| 19 | 220 | 2000 |
| 32 | 010 | 2000 |
- Missed approaches or go-arounds shall fly runway heading or track the localizer until reaching the departure end of the runway, then be issued a heading in accordance with the table unless the controller determines that it would be advantageous to delay or initiate a turn early.
- In order to prevent increased workload on Departure Control, consider issuing missed approaches or go-arounds speed restrictions in accordance with FAA Order JO 7110.65.
- Coordinate all IFR go arounds with N90/JFK sector as soon as possible and hand off when Local Control traffic is not a factor.
- Issue control instructions as necessary to establish separation and avoid arriving aircraft from overflying departing aircraft or aircraft on the runway. Consider wake turbulence, runway configuration, traffic pattern flows, weather conditions, slow rolling departures, and type of approach in use. Deviate as necessary from the following headings and altitudes if using them would compromise safety.
- The table indicates the heading and altitude that need to be assigned to a missed approach or go-around prior to release to Departure Control frequency.
Airspace
- Radar
This tower uses DBRITE radar only and is not certified for any approach control services. The following are the uses of the DBRITE radar at Republic:
- To determine an aircraft's exact location. This is accomplished by radar identifying the VFR aircraft through any of the techniques available to a radar position, such as having the aircraft squawk ident. Once identified, the aircraft's position and spatial relationship to other aircraft can be determined. Once initial radar identification of a VFR aircraft has been established and the appropriate instructions have been issued, radar monitoring may be discontinued; the reason being that the local controller's primary means of surveillance in VFR conditions is visually scanning the airport and local area.
- To provide radar traffic advisories. Radar traffic advisories may be provided to the extent that the local controller is able to monitor the radar display. Local Control has primary control responsibilities to the aircraft operating on the runways, which will normally supersede radar monitoring duties.
- To provide a direction or suggested heading. The local controller may provide pilots flying VFR with generalized instructions which will facilitate operations. The instructions are advisory aids to the pilot flying VFR and are not radar vectors.
- To provide information and instructions to aircraft operating within Class B, Class C, and Class D surface areas. In an example of this situation, the local controller would use the radar to advise a pilot on an extended downwind when to turn base leg.
- Departures
All departures whose destination is known to be JFK, LGA, EWR, TEB, or HPN should remain on the ground until an approval has been received from the destination tower that they are able to accept the aircraft into their airspace.
- VFR Reporting Points
At airports like Republic, pilots will often report a geographical location or checkpoint to verify and announce their location and position in relation to the field. Most VFR checkpoints are depicted on sectional aeronautical and terminal area charts. Some of the reporting points for Republic are as follows:
- From EAST: Belmont Lake
- From NORTH: Northport Stacks / Walt Whitman Mall
- From SOUTH: Captree Monument / Inner Shoreline
- Pattern Work
NOTE: All helicopters should be at 600’, props at 1,100’, and jets at 1,600’.
| Runway | Direction |
|---|---|
| 1 | Right |
| 14 | Left |
| 19 | Left |
| 32 | Right |
Visual approaches are the preferred approach type for FRG IFR arrivals. They should be run as long as the visibility is greater than 5 miles and ceilings are 2,100' or greater.
IFR aircraft inbound on a visual approach will be instructed to "maintain 2,000 until advised by the tower." This is to allow the tower to sequence inbound IFR aircraft into the traffic pattern if it is too busy for aircraft to make a straight in for the runway.
Examples:
- "Republic Tower, Flexjet 426, inbound visual approach runway 19, maintaining 2,000 until advised"
- "Flexjet 426, descend at your discretion, traffic to follow is a Cessna 172 on a 2 mile final for runway 19"
- "Flexjet 426, Republic Tower, descend to 1,600, enter left downwind runway 19"
Letters of Agreement
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Republic Airport (FRG) and New York TRACON (N90).
- Scope
- The procedures contained herein must apply unless prior coordination is effected.
- Disclosure
- vZNY and any other facilities mentioned in this document are affiliated with the Virtual Air Traffic Simulation (VATSIM) network. The procedures outlined in this document are intended exclusively for use in the VATSIM flight simulation environment and must never be used for actual flight or air traffic control operations. vZNY and any other facility mentioned in this document are not affiliated with the FAA in any manner.
FRG Arrival Procedures
- N90 TRACON shall
- Transfer IFR arrival data to the TOWER using the handoff function.
- Verbally advise the TOWER of an IFR arrival’s call sign when FRG TOWER does not accept the handoff prior to 10 miles from the airport.
- Verbally advise of arrival runway or approach, if other than the primary runway or approach in use.
- Transfer communications to FRG TOWER prior to the final approach fix or prior to entering the surface area.
- Restrict all visual approaches to "maintain 2000 until advised by the TOWER".
- Not issue visual approaches when visibility is five miles or less.
- FRG TOWER shall
- Forward the current ATIS code, runway usage, and approach information verbally.
- Verbally advise and receive an acknowledgement for changes in ATIS and visibility, wind and altimeter changes not reflected in current weather observations.
- Advise of airport conditions which may affect the movement of air traffic.
- Not issue any instructions to aircraft which would disrupt the approach sequence established by N90 TRACON without prior coordination.
- Advise of IFR aircraft utilizing a runway other than the primary arrival runway.
- FRG TOWER is authorized to clear IFR arrivals for a visual approach in accordance with FAA Order JO 7110.65 § 7-4-3, and shall advise N90 TRACON whenever this option is exercised.
FRG Departure Procedures
- N90 TRACON shall
- Advise FRG TOWER to instruct departures to maintain 2,000’ when JFK is landing RWYs 22L and 22R.
- FRG TOWER shall
- Advise N90 TRACON when an IFR aircraft is taxiing and include call sign, departure runway and sequence.
- Obtain IFR releases from N90 TRACON.
- Provide a “rolling call” to denote an aircraft’s departure roll to the ROBER position, which may consist of the call sign only, per FAA Order JO 7110.65 § 2-4-12.
- Advise N90 TRACON of IFR aircraft utilizing other than the primary departure runway.
- Restrict IFR departures to "maintain 3000, expect clearance to (requested altitude) 10 minutes after departure". When Standard Instrument Departure is not issued, assign the following headings "for vectors to (first route fix)":
- RWY 32/1 - heading 010.
- RWY 14/19 - heading 220.
- FRG TOWER is authorized, after N90 TRACON release, to separate an IFR departure from an IFR arrival using visual separation in accordance with FAA Order JO 7110.65 § 7-2-1
N90 TRACON shall, when conditions permit, allow departures to climb to 2,000 feet on their initial headings.
Practice Instrument Approaches
- N90 TRACON shall advise FRG TOWER how the approach will terminate (i.e. full stop landing, touch and go, missed approach instructions, etc.). This information shall be given when the aircraft is no closer than 10 miles from the airport.
- FRG TOWER shall advise whenever they cannot approve approaches.
Delegation of Authority
Authorization and responsibility for the control of Special VFR operations at and below 1,500 feet within the Class D Surface Area is delegated to FRG Local Control.
Special VFR Operations
Upon request, N90 TRACON shall advise the TOWER when an IFR departure leaves Class D Airspace or reaches 2000, when the weather is IFR.
