EJA774 (Netjets Sales) was operating from KBFI to KBZN (Gallatin Field) on 2026-03-14. SkyMeter detected a diversion to Phoenix Sky Harbor International Airport (KPHX) on runway 08 at 14:58 UTC. Peak cruise altitude FL419, turnaround area near Battle Mountain, US. Approach stability score: 68/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 4 kt wind, 1 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/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft

    Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

    BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 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 08
  • 1135 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 68/100
  • 4 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • METAR KPHX 271151Z 09005KT 10SM FEW170 BKN200 OVC250 27/12 A2986 RMK AO2 SLP090 T02670117 10306 20267 55001 $

Flight context

  • EJA774
  • Netjets Sales
  • CL35
  • KBFI → KPHX
  • 2026-03-14 14:58 UTC
  • KPHX runway 08

All events on this flight

Diversion 14:58:46 UTC · KPHX runway 08 · 1,135 ft AGL · 120 kt GS
Diversion 14:58:46 UTC · KPHX runway 08 · 1,135 ft AGL · 120 kt GS

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

SkyMeter · trace data observed via ADS-B· KPHX