Return to field — TKR912

KMFR · 32

2026-08-09 02:40 UTC· KMFR KMFR· BC AIRCRAFT LEASING LLC· DC10

TKR912 (BC Aircraft Leasing) had departed KMFR on 2026-08-09. SkyMeter detected a return to field at Rogue Valley International Medford Airport (KMFR) on runway 32 at 02:40 UTC. Peak altitude 14,636 ft, turnaround area near Jackson County, 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/9403 2026-07-28 13:00Z – 2026-08-10 03:00Z SFC–7,000 ft

    20NM NW MEDFORD, OR, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9888 2026-07-29 13:00Z – 2026-08-12 03:00Z SFC–6,000 ft

    20NM NW MEDFORD, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0890 2026-08-02 13:00Z – 2026-08-15 03:00Z SFC–5,000 ft

    20NM NW MEDFORD, OR, Sunday, August 2, 2026 through Saturday, August 15, 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 32
  • 14636 ft AGL at event
  • 352 kt ground speed
  • 0 fpm vertical
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KMFR 161653Z VRB03KT 10SM CLR 13/07 A3002 RMK AO2 SLP163 T01330072

Flight context

  • TKR912
  • BC Aircraft Leasing
  • DC10
  • KMFR → KMFR
  • 2026-08-09 02:40 UTC
  • KMFR runway 32

All events on this flight

Return to field 02:40:38 UTC · KMFR runway 32 · 14,636 ft AGL · 352 kt GS
Long landing rollout 03:20:37 UTC · KMFR runway 32 · 1,305 ft AGL · 0 kt GS
Long landing rollout 03:20:37 UTC · KMFR runway 32 · 1,305 ft AGL · 0 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· KMFR