Latest News

Last year Teterboro Airport completed a full rehabilitation of Runway 6/24. The airport is now soliciting feedback on how the project went to determine where Airport Operations could improve on customer satisfaction and communication. If you could please complete the survey at the link below it would be greatly appreciated.

https://www.surveymonkey.com/r/5LCJ5ZN

The FAA recently approved two new VFR waypoints that will assist pilots in visually executing the circling portion of the KTEB ILS 6 Circle Rwy 1. These waypoints are intended to be drawn from FMS databases to enhance pilot situational awareness.

Honeywell agreed to a TUG request to publish these VFR waypoints in all generic Business and General Aviation NavDBs that include KTEB, and will do so beginning with cycle 2303. Although the effective date for this cycle is March 23, the fact that NavDBs contain two cycles of data means that customers will see these VFR waypoints as soon as they load the next update, which will be posted on March 15.

TUG will continue to encourage other FMS OEMs to include these VFR waypoints in their NavDBs at their earliest opportunity.

The waypoints are:

VPEZA (404827.35N/0740449.37W), located .5 nm SW of MetLife Stadium

VPDAU (404912.97N/0740342.22W), located .5 nm east of the Race Track

The bearing/distance from TORBY to VPEZA are: 097.39° / 2.38 NM;

The bearing/distance from VPEZA to VPDAU are 060.19° / 1.14 NM; and 

The bearing from VPDAU to RWY 1 is 015.21° / 1.23 NM

Please see the attached graphics to help familiarize yourself with these waypoints.

A recent increase in RUUDY 6 pilot deviations, as well as a Rwy 19 missed approach pilot deviation, prompted the FAA to issue the following two Letters to Airmen. The Teterboro Users Group published and disseminated RUUDY 6 guidance material on May 5, 2018, and are re-posting the information below. Since the RUUDY 6 is the primary SID issued to flight crews departing KTEB Rwy 24, please carefully review the text and graphics specified on the Jeppesen and/or U.S. Government charts, and brief the lateral and vertical modes, ASEL selection, automation management and crew coordination requirements necessary to comply with all published lateral and vertical provisions of the procedure.

Our own Captain Jim Dramis has written an excellent article regarding his technique recommendations for how to fly the RUUDY 6 SID. You can download the article via our Operations > Airspace & Procedures tab: https://teterborousersgroup.org/operations/airspace/

We’ve come to understand that there exists a restriction in the practical application of CPDLC DCL within the U.S. NAS. This restriction is specific to the FAA Data Comm system, and therefore impacts all users and all FMS regardless of OEM.

When issued a CPDLC DCL other than “Cleared As Filed”, the clearance will include a loadable route (“Push to Load”), which the crew must Insert and Activate. This loaded route will NOT contain the assigned SID. If the Runway and SID had been previously loaded into the FMS, this action may retain the Runway and associated performance information but will drop the SID and its associated waypoint list segments and constraints. Consequently, the crew will need to reinsert and activate the SID for which they’ve been cleared.

The FAA and its industry partners are exploring options that may allow the DCL system to incorporate the SID into the loadable clearance. In the meantime, crews are encouraged to comply with SOPs and remain vigilant in verifying that the FMS is properly programmed with the cleared flight segments, as well as altitude and speed constraints, and that the appropriate level of automation (flight guidance, autoflight, autothrottles) and crew coordination is briefed and implemented.

TUG strongly encourages operators to make reservations with FBOs in an effort to prevent gridlock, which has occurred several times in recent days. Some operators have failed to make reservations at all. Others who’ve been informed by FBOs of ramp constraints have represented that they’re “just a drop and go,” only to leave the aircraft and return the following day. The result has been gridlock on ramps and taxiways that have precipitated ground delay programs elsewhere in the NAS.

Please make every effort to share your arrival information in advance with the FBO of your choosing so as to enable better allocation of limited ramp space and avoid unnecessary delays for all of KTEB’s operators.