Unstable approach — TKR168

TKR168 (Aero-Flite) was operating from KMCC to KHIF on 2026-08-24. SkyMeter detected a low approach-stability score at Hill Air Force Base (KHIF) on runway 14 at 22:25 UTC. Trace data at the event: 5851 ft AGL, 185 kt GS. Approach stability score: 28/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.

• SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

  BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• HAZARDS6/4085 2026-08-12 04:00Z – 2026-08-25 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Wednesday, August 12, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4104 2026-08-12 04:00Z – 2026-08-25 04:00Z SFC–11,000 ft

  15NM NW RENO, NV, Wednesday, August 12, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4110 2026-08-12 14:00Z – 2026-08-26 03:00Z SFC–12,500 ft

  12NM SE DRESSLERVILLE, NV, Wednesday, August 12, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5067 2026-08-14 02:15Z – 2026-08-27 04:00Z SFC–11,000 ft

  15NM NW RENO, NV, Friday, August 14, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5242 2026-08-15 23:15Z – 2026-08-29 04:00Z SFC–9,500 ft

  15NM NW RENO, NV, Saturday, August 15, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5250 2026-08-16 13:00Z – 2026-08-30 04:00Z SFC–11,000 ft

  52NM NE FALLON, NV, Sunday, August 16, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5423 2026-08-16 19:15Z – 2026-08-30 04:00Z SFC–11,000 ft

  52NM NE FALLON, NV, Sunday, August 16, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5937 2026-08-18 13:00Z – 2026-08-31 03:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5897 2026-08-18 14:00Z – 2026-08-31 02:00Z SFC–7,500 ft

  15NM NW RENO, NV, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6067 2026-08-18 18:15Z – 2026-09-01 02:00Z SFC–11,000 ft

  52NM NE FALLON, NV, Tuesday, August 18, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7113 2026-08-22 20:30Z – 2026-09-05 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Saturday, August 22, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7127 2026-08-23 05:30Z – 2026-09-06 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7283 2026-08-23 16:00Z – 2026-09-06 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

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

  35NM SW PROVO, UT, Monday, August 24, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7530 2026-08-24 17:00Z – 2026-09-06 03:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Sunday, September 6, 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.

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