Return to field — TKR103

KRDM · 29

2026-07-17 23:14 UTC· KRDM → KRDM· CORSAIR TWO LLC· MD87

▶ Replay 📊 Analyse

TKR103 (Corsair TWO) had departed KRDM on 2026-07-17. SkyMeter detected a return to field at Roberts Field (KRDM) on runway 29 at 23:14 UTC. Peak altitude 5,265 ft, turnaround area near Terrebonne, US. Approach stability score: 43/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/6408 2026-07-17 04:31Z – 2026-07-31 04:00Z SFC–9,000 ft

    10NM SW CULVER, OR, Friday, July 17, 2026 through Friday, July 31, 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
  • 5265 ft AGL at event
  • 297 kt ground speed
  • 0 fpm vertical
  • Approach stability 43/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KRDM 161456Z 33008KT 10SM FEW039 11/09 A3012 RMK AO2 SLP191 60000 T01060089 51015 $

Flight context

  • TKR103
  • Corsair TWO
  • MD87
  • KRDM → KRDM
  • 2026-07-17 23:14 UTC
  • KRDM runway 29

All events on this flight

Return to field 23:14:18 UTC · KRDM runway 29 · 5,265 ft AGL · 297 kt GS
Unstable approach 23:25:40 UTC · KRDM runway 29 · 4,087 ft AGL · 137 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