EJA635 (Netjets Sales) was operating from KTMB to KBNA (Nashville International Airport) on 2026-03-31. SkyMeter detected a diversion to Greenville Downtown Airport (KGMU) on runway 01 at 23:07 UTC. Peak cruise altitude FL425, turnaround area near Villano Beach, US. Approach stability score: 75/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, 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/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 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 01
  • 1048 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 75/100
  • 6 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • METAR KGMU 231853Z 04011KT 10SM OVC014 18/15 A3021 RMK AO2 SLP224 T01830150

Flight context

  • EJA635
  • Netjets Sales
  • C68A
  • KTMB → KGMU
  • 2026-03-31 23:07 UTC
  • KGMU runway 01

All events on this flight

Diversion 23:07:44 UTC · KGMU runway 01 · 1,048 ft AGL · 120 kt GS
Diversion 23:07:44 UTC · KGMU runway 01 · 1,048 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· KGMU