Return to field — TKR910

KMFR · 32

2026-07-20 20:00 UTC· KMFR → KMFR· BC AIRCRAFT LEASING LLC· DC10

▶ Replay 📊 Analyse

TKR910 (BC Aircraft Leasing) had departed KMFR on 2026-07-20. SkyMeter detected a return to field at Rogue Valley International Medford Airport (KMFR) on runway 32 at 20:00 UTC. Peak altitude 13,424 ft, turnaround area near Montague, US. Approach stability score: 42/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/6409 2026-07-17 04:39Z – 2026-07-30 07:00Z SFC–11,000 ft

    10NM SW MOUNT SHASTA, CA, Friday, July 17, 2026 through Thursday, July 30, 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
  • 13424 ft AGL at event
  • 383 kt ground speed
  • 0 fpm vertical
  • Approach stability 42/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KMFR 161853Z 00000KT 10SM CLR 19/08 A3000 RMK AO2 SLP153 T01890083

Flight context

  • TKR910
  • BC Aircraft Leasing
  • DC10
  • KMFR → KMFR
  • 2026-07-20 20:00 UTC
  • KMFR runway 32

All events on this flight

Return to field 20:00:46 UTC · KMFR runway 32 · 13,424 ft AGL · 383 kt GS
Unstable approach 21:55:05 UTC · KMFR runway 14 · 2,423 ft AGL · 159 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