Return to field — TKR102
KRDM · 292026-07-19 22:28 UTC· KRDM → KRDM· CORSAIR TWO LLC· MD87
TKR102 (Corsair TWO) had departed KRDM on 2026-07-19. SkyMeter detected a return to field at Roberts Field (KRDM) on runway 29 at 22:28 UTC. Peak altitude 6,340 ft, turnaround area near Terrebonne, 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 →
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
- 6340 ft AGL at event
- 289 kt ground speed
- 0 fpm vertical
- Approach stability 38/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KRDM 101456Z 16003KT 10SM CLR M02/M04 A2980 RMK AO2 SLP099 T10221039 55000 $
Flight context
- TKR102
- Corsair TWO
- MD87
- KRDM → KRDM
- 2026-07-19 22:28 UTC
- KRDM runway 29
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