VILLN52 (Taslo) was operating from 54UT to KHIF on 2026-06-10. SkyMeter detected a low approach-stability score at Hill Air Force Base (KHIF) on runway 32 at 20:43 UTC. Trace data at the event: 5846 ft AGL, 209 kt GS. METAR at the time reported 9 kt wind, 9 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. 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 →
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
- 5846 ft AGL at event
- 209 kt ground speed
- 0 fpm vertical
- 9 kt wind
- 9 kt crosswind component
- 16,093 m visibility
- KHIF 131940Z 00000KT 10SM BKN025 BKN032 BKN085 BKN140 09/04 A3001 RMK AO2A DZB02E25 CIG 025V085 BKN025 V SCT SLP142
Flight context
- VILLN52
- Taslo
- F5
- 54UT → KHIF
- 2026-06-10 20:43 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