Unstable approach — TKR183

TKR183 (Bank of Utah) was operating from KRDM to KLGD on 2026-08-16. SkyMeter detected a low approach-stability score at La Grande/Union County Airport (KLGD) on runway 30 at 21:59 UTC. Trace data at the event: 3753 ft AGL, 119 kt GS. Approach stability score: 38/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 6 kt wind, 1 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/1476 2026-08-04 05:00Z – 2026-08-19 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Tuesday, August 4, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1978 2026-08-05 06:00Z – 2026-08-20 05:00Z SFC–10,000 ft

  50NM W JOHN DAY, OR, Wednesday, August 5, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2774 2026-08-07 05:00Z – 2026-08-21 05:00Z SFC–9,000 ft

  20NM SE MADRAS, OR, Friday, August 7, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2775 2026-08-07 15:00Z – 2026-08-21 04:00Z SFC–10,000 ft

  22NM NW JOHN DAY, OR, Friday, August 7, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3074 2026-08-08 19:45Z – 2026-08-23 05:00Z SFC–9,000 ft

  20NM SE MADRAS, OR, Saturday, August 8, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3608 2026-08-10 23:00Z – 2026-08-25 04:00Z SFC–9,500 ft

  39NM NW JOHN DAY, OR, Monday, August 10, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3763 2026-08-11 15:45Z – 2026-08-26 04:00Z SFC–10,500 ft

  20NM SW THE DALLES, OR, Tuesday, August 11, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4057 2026-08-11 22:45Z – 2026-08-26 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Tuesday, August 11, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4083 2026-08-12 00:30Z – 2026-08-26 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Wednesday, August 12, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4094 2026-08-12 02:00Z – 2026-08-27 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4725 2026-08-13 14:00Z – 2026-08-27 07:00Z SFC–9,000 ft

  24NM E PENDLETON, OR, Thursday, August 13, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4957 2026-08-13 17:30Z – 2026-08-28 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5112 2026-08-14 16:30Z – 2026-08-29 03:00Z SFC–9,500 ft

  19NM NW JOHN DAY, OR, Friday, August 14, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5137 2026-08-15 04:00Z – 2026-08-27 15:00Z SFC–6,500 ft

  18NM NW JOHN DAY, OR, Saturday, August 15, 2026 through Thursday, August 27, 2026 UTC

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

  20NM SW THE DALLES, OR, Saturday, August 15, 2026 through Saturday, August 29, 2026 UTC

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

  19NM NW JOHN DAY, OR, Saturday, August 15, 2026 through Sunday, August 30, 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