Diversion — EJA262
KBHM · 062026-03-30 18:48 UTC· KPBI → KBHM· AP NS HOLDINGS LLC, BIG ZIGGY LLC, LJT22 LLC, LUMEN TECHNOLOGIES· CL60
EJA262 (AP NS Holdings) was operating from KPBI to KHPN (Westchester County Airport) on 2026-03-30. SkyMeter detected a diversion to Birmingham-Shuttlesworth International Airport (KBHM) on runway 06 at 18:48 UTC. Peak cruise altitude FL395, turnaround area near Steinhatchee, 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 6 kt wind, 4 kt crosswind component, 16,093 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 → - HAZARDS6/4875 2026-03-30 13:00Z – 2026-04-04 06:00Z SFC–2,500 ft
20NM NW MEDFORD, OR, Friday, July 10, 2026 through Saturday, July 25, 2026 UTC
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 06
- 621 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 72/100
- 6 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR KBHM 241553Z 12005KT 10SM OVC012 23/18 A3019 RMK AO2 SLP215 T02280183
Flight context
- EJA262
- AP NS Holdings
- CL60
- KPBI → KBHM
- 2026-03-30 18:48 UTC
- KBHM runway 06
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