Return to field — TKR160

KRDM · 29

2026-08-14 22:47 UTC· KRDM KRDM· AERO-FLITE INC· RJ85

TKR160 (Aero-Flite) had departed KRDM on 2026-08-14. SkyMeter detected a return to field at Roberts Field (KRDM) on runway 29 at 22:47 UTC. Peak altitude 11,030 ft, turnaround area near Prineville, US. 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/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.

Pilot review data

  • Runway 29
  • 11030 ft AGL at event
  • 304 kt ground speed
  • 0 fpm vertical
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KRDM 152056Z 33009KT 10SM FU CLR 28/09 A3010 RMK AO2 SLP167 T02780089 58005

Flight context

  • TKR160
  • Aero-Flite
  • RJ85
  • KRDM → KRDM
  • 2026-08-14 22:47 UTC
  • KRDM runway 29

All events on this flight

Return to field 22:47:03 UTC · KRDM runway 29 · 11,030 ft AGL · 304 kt GS
Unstable approach 23:41:12 UTC · KRDM runway 29 · 4,147 ft AGL · 144 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