Return to field — VILLN63
KHIF · 322026-07-15 22:08 UTC· KHIF → KHIF· TACTICAL AIR SUPPORT INC· F5
VILLN63 (Tactical AIR Support) had departed KHIF on 2026-07-15. SkyMeter detected a return to field at Hill Air Force Base (KHIF) on runway 32 at 22:08 UTC. Peak cruise altitude FL299, turnaround area near Cassia, US. Approach stability score: 20/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/4555 2026-07-10 14:00Z – 2026-07-23 04:00Z SFC–10,500 ft
44NM NE WELLS, NV, Friday, July 10, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/5155 2026-07-13 13:00Z – 2026-07-26 04:00Z SFC–11,000 ft
40NM NE WELLS, NV, Monday, July 13, 2026 through Sunday, July 26, 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
- 29938 ft AGL at event
- 574 kt ground speed
- 0 fpm vertical
- Approach stability 20/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KHIF 170555Z AUTO 10016G25KT 10SM CLR 23/10 A3008 RMK AO2 SLP121 T02320096 10290 20231 52006
Flight context
- VILLN63
- Tactical AIR Support
- F5
- KHIF → KHIF
- 2026-07-15 22:08 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