Return to field — TKR106

KHIF · 14

2026-06-20 21:03 UTC· KHIF KHIF· CORSAIR TWO LLC· MD87

TKR106 (Corsair TWO) had departed KHIF on 2026-06-20. SkyMeter detected a return to field at Hill Air Force Base (KHIF) on runway 14 at 21:03 UTC. Peak altitude 11,481 ft, turnaround area near Herriman, US. 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)
  • HAZARDS6/6827 2026-06-09 17:15Z – 2026-06-22 02:00Z SFC–10,000 ft

    9NM SW TOOELE, UT, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6965 2026-06-10 14:00Z – 2026-06-22 03:00Z SFC–10,000 ft

    9NM SW TOOELE, UT, Wednesday, June 10, 2026 through Monday, June 22, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft

    27NM SW PROVO, UT, Saturday, June 20, 2026 through Friday, July 3, 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 14
  • 11481 ft AGL at event
  • 365 kt ground speed
  • 0 fpm vertical
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KHIF 180355Z 16006KT 10SM SCT090 BKN110 22/09 A3007 RMK AO2A SLP121 T02230088

Flight context

  • TKR106
  • Corsair TWO
  • MD87
  • KHIF → KHIF
  • 2026-06-20 21:03 UTC
  • KHIF runway 14

All events on this flight

Return to field 21:03:09 UTC · KHIF runway 14 · 11,481 ft AGL · 365 kt GS
Go-around 21:45:04 UTC · KHIF runway 32 · 6,425 ft AGL · 222 kt GS
Go-around 21:45:04 UTC · KHIF runway 32 · 6,425 ft AGL · 222 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· KHIF