Return to field — TKR10

KRDM · 29

2026-07-17 20:30 UTC· KRDM KRDM· NEPTUNE AVIATION SERVICES INC· B462

TKR10 (Neptune Aviation Services) had departed KRDM on 2026-07-17. SkyMeter detected a return to field at Roberts Field (KRDM) on runway 29 at 20:30 UTC. Peak altitude 9,989 ft, turnaround area near Prineville, US. Approach stability score: 41/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 →

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
  • 9989 ft AGL at event
  • 315 kt ground speed
  • 0 fpm vertical
  • Approach stability 41/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KRDM 121456Z 17005KT 10SM CLR 16/08 A3005 RMK AO2 SLP152 T01610078 53002

Flight context

  • TKR10
  • Neptune Aviation Services
  • B462
  • KRDM → KRDM
  • 2026-07-17 20:30 UTC
  • KRDM runway 29

All events on this flight

Return to field 20:30:56 UTC · KRDM runway 29 · 9,989 ft AGL · 315 kt GS
Unstable approach 21:13:03 UTC · KRDM runway 29 · 4,172 ft AGL · 128 kt GS
Unstable approach 21:13:03 UTC · KRDM runway 29 · 4,172 ft AGL · 128 kt GS
Unstable approach 21:13:03 UTC · KRDM runway 29 · 4,172 ft AGL · 128 kt GS
Unstable approach 21:13:03 UTC · KRDM runway 29 · 4,172 ft AGL · 128 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