Diversion — EJA449
KHPN · 162026-03-13 12:39 UTC· KPBI → KHPN· NETJETS SALES INC, JAR JET LLC, VAN HARTE JEFFERY S TRUSTEE, SMI· E55P
EJA449 (Netjets Sales) was operating from KPBI to KABY (Southwest Georgia Regional Airport) on 2026-03-13. SkyMeter detected a diversion to Westchester County Airport (KHPN) on runway 16 at 12:39 UTC. Peak cruise altitude FL423, turnaround area near Swansboro, US. Approach stability score: 72/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 5 kt wind, 5 kt crosswind component, 1,609 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 16
- 380 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 72/100
- 5 kt wind
- 5 kt crosswind component
- 1,609 m visibility
- METAR KHPN 271856Z 03010KT 1SM R16/5500VP6000FT -RA BR BKN008 OVC012 17/16 A2970 RMK AO2 SFC VIS 3 RAE02B20 SLP054 P0002 T01670156
Flight context
- EJA449
- Netjets Sales
- E55P
- KPBI → KHPN
- 2026-03-13 12:39 UTC
- KHPN runway 16
All events on this flight
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data