Unstable approach — TKR136

TKR136 (CSC Delaware Tust) was operating from 12OR to KMFR on 2026-07-28. SkyMeter detected a low approach-stability score at Rogue Valley International Medford Airport (KMFR) on runway 27 at 03:29 UTC. Trace data at the event: 2413 ft AGL, 155 kt GS. Approach stability score: 20/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 9 kt wind, 5 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/6100 2026-07-16 14:00Z – 2026-07-30 04:00Z SFC–10,000 ft

  41NM SE BURNS, OR, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6363 2026-07-17 01:54Z – 2026-07-31 04:00Z SFC–8,000 ft

  20NM NW MEDFORD, OR, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7914 2026-07-22 18:44Z – 2026-08-05 04:00Z SFC–7,000 ft

  20NM NW MEDFORD, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8323 2026-07-23 23:15Z – 2026-08-05 05:00Z SFC–10,000 ft

  95NM SE BURNS, OR, Thursday, July 23, 2026 through Wednesday, August 5, 2026 UTC

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

  44NM SW BURNS, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8460 2026-07-24 18:30Z – 2026-08-08 05:00Z SFC–10,000 ft

  95NM SE BURNS, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

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

  95NM SE BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

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

  95NM SE BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8784 2026-07-26 18:45Z – 2026-08-10 05:00Z SFC–10,000 ft

  44NM SW BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9354 2026-07-27 22:15Z – 2026-08-10 05:00Z SFC–10,000 ft

  26NM S BURNS, OR, Monday, July 27, 2026 through Monday, August 10, 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