Return to field — TKR102

KRDM · 29

2026-07-26 01:52 UTC· KRDM → KRDM· CORSAIR TWO LLC· MD87

▶ Replay 📊 Analyse

TKR102 (Corsair TWO) had departed KRDM on 2026-07-26. SkyMeter detected a return to field at Roberts Field (KRDM) on runway 29 at 01:52 UTC. Peak altitude 9,515 ft, turnaround area near Culver, US. 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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/6458 2026-07-17 15:40Z – 2026-08-01 04:00Z SFC–9,000 ft

    9NM E MADRAS, OR, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6695 2026-07-18 20:09Z – 2026-07-31 04:00Z SFC–9,000 ft

    12NM SE MADRAS, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6757 2026-07-19 16:07Z – 2026-08-02 04:00Z SFC–9,000 ft

    12NM SE MADRAS, OR, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8322 2026-07-23 22:15Z – 2026-07-30 05:00Z SFC–8,000 ft

    8NM NE MADRAS, OR, Thursday, July 23, 2026 through Thursday, July 30, 2026 UTC

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

    12NM SE MADRAS, OR, Friday, July 24, 2026 through Friday, August 7, 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/8565 2026-07-25 22:00Z – 2026-08-09 05:00Z SFC–9,000 ft

    20NM SE MADRAS, OR, Saturday, July 25, 2026 through Sunday, August 9, 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.

Pilot review data

  • Runway 29
  • 9515 ft AGL at event
  • 318 kt ground speed
  • 0 fpm vertical
  • Approach stability 38/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KRDM 160856Z AUTO 31006KT 10SM FEW055 BKN110 10/08 A3005 RMK AO2 RAB03E34 SLP163 P0000 60001 T01000078 51006 $

Flight context

  • TKR102
  • Corsair TWO
  • MD87
  • KRDM → KRDM
  • 2026-07-26 01:52 UTC
  • KRDM runway 29

All events on this flight

Return to field 01:52:02 UTC · KRDM runway 29 · 9,515 ft AGL · 318 kt GS
Unstable approach 02:31:24 UTC · KRDM runway 29 · 4,134 ft AGL · 151 kt GS

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

SkyMeter · trace data observed via ADS-B· KRDM