Return to field — VILLN61
KHIF · 322026-07-09 20:19 UTC· KHIF → KHIF· TACTICAL AIR SUPPORT INC· F5
VILLN61 (Tactical AIR Support) had departed KHIF on 2026-07-09. SkyMeter detected a return to field at Hill Air Force Base (KHIF) on runway 32 at 20:19 UTC. Peak cruise altitude FL336, turnaround area near Tooele County, US. Approach stability score: 25/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). 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/1072 2026-06-27 14:12Z – 2026-07-10 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/1144 2026-06-28 14:00Z – 2026-07-11 04:00Z SFC–11,000 ft
27NM SW PROVO, UT, Sunday, June 28, 2026 through Saturday, July 11, 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 32
- 33643 ft AGL at event
- 528 kt ground speed
- 0 fpm vertical
- Approach stability 25/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KHIF 301355Z AUTO 11013KT 10SM CLR 11/04 A2998 RMK AO2 SLP111 T01140041
Flight context
- VILLN61
- Tactical AIR Support
- F5
- KHIF → KHIF
- 2026-07-09 20:19 UTC
- KHIF runway 32
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