Long landing rollout — TKR912

KMFR · 32

2026-08-26 01:09 UTC· KMFR KMCC· BC AIRCRAFT LEASING LLC· DC10

TKR912 (BC Aircraft Leasing) was operating from KMFR to KMCC on 2026-08-26. SkyMeter detected a long landing rollout at Rogue Valley International Medford Airport (KMFR) on runway 32 at 01:09 UTC. Trace data at the event: 1305 ft AGL, 0 kt GS. Approach stability score: 62/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 16 kt wind, 10 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

    BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/5053 2026-08-14 02:15Z – 2026-08-29 04:00Z SFC–11,000 ft

    15NM N KLAMATH FALLS, OR, Friday, August 14, 2026 through Saturday, August 29, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5067 2026-08-14 02:15Z – 2026-08-27 04:00Z SFC–11,000 ft

    15NM NW RENO, NV, Friday, August 14, 2026 through Thursday, August 27, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5242 2026-08-15 23:15Z – 2026-08-29 04:00Z SFC–9,500 ft

    15NM NW RENO, NV, Saturday, August 15, 2026 through Saturday, August 29, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5897 2026-08-18 14:00Z – 2026-08-31 02:00Z SFC–7,500 ft

    15NM NW RENO, NV, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6958 2026-08-21 04:00Z – 2026-09-03 04:00Z SFC–11,000 ft

    15NM N KLAMATH FALLS, OR, Friday, August 21, 2026 through Thursday, September 3, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7113 2026-08-22 20:30Z – 2026-09-05 03:00Z SFC–11,500 ft

    1NM W RENO, NV, Saturday, August 22, 2026 through Saturday, September 5, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7127 2026-08-23 05:30Z – 2026-09-06 03:00Z SFC–11,500 ft

    1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7283 2026-08-23 16:00Z – 2026-09-06 03:00Z SFC–11,500 ft

    1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7609 2026-08-24 23:37Z – 2026-09-07 03:00Z SFC–8,000 ft

    15NM NE ALTURAS, CA, Monday, August 24, 2026 through Monday, September 7, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7708 2026-08-25 13:13Z – 2026-09-08 03:00Z SFC–8,000 ft

    15NM NE ALTURAS, CA, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7667 2026-08-25 14:00Z – 2026-08-31 04:00Z SFC–11,500 ft

    1NM W RENO, NV, Tuesday, August 25, 2026 through Monday, August 31, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7989 2026-08-25 22:30Z – 2026-09-08 03:00Z SFC–11,000 ft

    14NM NE CEDARVILLE, CA, Tuesday, August 25, 2026 through Tuesday, September 8, 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
  • 1305 ft AGL at event
  • 0 kt ground speed
  • 0 fpm vertical
  • Approach stability 62/100
  • 16 kt wind
  • 10 kt crosswind component
  • 16,093 m visibility
  • KMFR 170453Z AUTO 08004KT 10SM CLR 16/11 A3001 RMK AO2 RAE0359 SLP159 P0000 T01560111

Flight context

  • TKR912
  • BC Aircraft Leasing
  • DC10
  • KMFR → KMCC
  • 2026-08-26 01:09 UTC
  • KMFR runway 32

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