Return to field — N984GE

KTYQ · 36

2026-06-19 20:09 UTC· KTYQ → KTYQ· PILATUS BUSINESS AIRCRAFT LTD· PC24

▶ Replay 📊 Analyse

N984GE (Pilatus Business Aircraft) had departed KTYQ on 2026-06-19. SkyMeter detected a return to field at Indianapolis Executive Airport (KTYQ) on runway 36 at 20:09 UTC. Peak cruise altitude FL352, turnaround area near Bloomington, US. Approach stability score: 57/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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • UAS PUBLIC GATHERING6/8284 2026-06-19 21:30Z – 2026-06-21 04:30Z SFC–400 ft

    Chicago, IL, Friday, June 19, 2026 through Sunday, June 21, 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 36
  • 35228 ft AGL at event
  • 534 kt ground speed
  • 0 fpm vertical
  • Approach stability 57/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • METAR KTYQ 101335Z AUTO 00000KT 10SM CLR 15/10 A3019 RMK AO2 T01450103

Flight context

  • N984GE
  • Pilatus Business Aircraft
  • PC24
  • KTYQ → KTYQ
  • 2026-06-19 20:09 UTC
  • KTYQ runway 36

All events on this flight

Return to field 20:09:54 UTC · KTYQ runway 36 · 35,228 ft AGL · 534 kt GS
Unstable approach 22:03:20 UTC · KTYQ runway 36 · 2,034 ft AGL · 157 kt GS
Unstable approach 22:03:20 UTC · KTYQ runway 36 · 2,034 ft AGL · 157 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· KTYQ