Long landing rollout — TKR168

KRIR · 24

2026-07-16 02:34 UTC· KSBD → KRIR· AERO-FLITE INC· RJ85

▶ Replay 📊 Analyse

TKR168 (Aero-Flite) was operating from KSBD to KRIR on 2026-07-16. SkyMeter detected a long landing rollout at Flabob Airport (KRIR) on runway 24 at 02:34 UTC. Trace data at the event: 1118 ft AGL, 5 kt GS. METAR at the time reported 3 kt wind, 2 kt crosswind component. 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/4183 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4202 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4203 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7820 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft

    San Diego, CA

    View FAA NOTAM →
  • SECURITY6/7821 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft

    San Diego, CA

    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 24
  • 1118 ft AGL at event
  • 5 kt ground speed
  • 0 fpm vertical
  • 3 kt wind
  • 2 kt crosswind component

Flight context

  • TKR168
  • Aero-Flite
  • RJ85
  • KSBD → KRIR
  • 2026-07-16 02:34 UTC
  • KRIR runway 24

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· KRIR