Unstable approach — TKR101

TKR101 (Corsair TWO) was operating from KHIF to KHIF on 2026-08-10. SkyMeter detected a low approach-stability score at Hill Air Force Base (KHIF) on runway 14 at 20:58 UTC. Trace data at the event: 5831 ft AGL, 147 kt GS. Approach stability score: 47/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 8 kt wind, 4 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.

• HAZARDS6/3044 2026-08-08 18:30Z – 2026-08-15 04:00Z SFC–9,000 ft

  20NM NE SALT LAKE CITY, UT, Saturday, August 8, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3080 2026-08-08 22:15Z – 2026-08-22 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3097 2026-08-09 13:00Z – 2026-08-23 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3156 2026-08-10 13:00Z – 2026-08-24 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Monday, August 10, 2026 through Monday, August 24, 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.

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