Unstable approach — TKR136

TKR136 (CSC Delaware Tust) was operating from KRDM to KRDM on 2026-08-14. SkyMeter detected a low approach-stability score at Roberts Field (KRDM) on runway 23 at 23:13 UTC. Trace data at the event: 4134 ft AGL, 138 kt GS. Approach stability score: 41/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 7 kt wind, 6 kt crosswind component, 14,484 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/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/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/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 →

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