Unstable approach — KILO6

KILO6 (United States Department of Interior) was operating from KRDM to KRDM on 2026-08-08. SkyMeter detected a low approach-stability score at Roberts Field (KRDM) on runway 11 at 01:26 UTC. Trace data at the event: 4196 ft AGL, 151 kt GS. METAR at the time reported 17 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/8438 2026-07-24 18:30Z – 2026-08-08 04:00Z SFC–9,500 ft

  25NM SW THE DALLES, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

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

  10NM W MADRAS, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8490 2026-07-25 01:45Z – 2026-08-08 04:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8545 2026-07-25 17:00Z – 2026-08-09 04:00Z SFC–7,000 ft

  8NM SW THE DALLES, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8555 2026-07-25 19:00Z – 2026-08-09 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

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

  10NM W MADRAS, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8585 2026-07-26 14:00Z – 2026-08-09 05:00Z SFC–9,500 ft

  25NM SW THE DALLES, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8859 2026-07-26 22:00Z – 2026-08-10 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9852 2026-07-29 00:30Z – 2026-08-12 04:00Z SFC–9,000 ft

  17NM NW REDMOND, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9939 2026-07-29 14:00Z – 2026-08-12 04:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0415 2026-07-30 15:00Z – 2026-08-12 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0573 2026-07-31 04:00Z – 2026-08-12 04:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Friday, July 31, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0581 2026-07-31 05:30Z – 2026-08-14 04:00Z SFC–10,500 ft

  25NM SW THE DALLES, OR, Friday, July 31, 2026 through Friday, August 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0952 2026-08-02 17:00Z – 2026-08-16 05:00Z SFC–9,000 ft

  10NM W MADRAS, OR, Sunday, August 2, 2026 through Sunday, August 16, 2026 UTC

  View FAA NOTAM →
• 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/1478 2026-08-04 05:00Z – 2026-08-18 05:00Z SFC–10,500 ft

  25NM SW THE DALLES, OR, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1681 2026-08-04 16:00Z – 2026-08-19 05:00Z SFC–10,500 ft

  25NM SW THE DALLES, OR, Tuesday, August 4, 2026 through Wednesday, August 19, 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