Long landing rollout — N750CK

KRYY · 09

2026-08-29 19:24 UTC· KFLL KRYY· MN AIRCRAFT LLC· C650

N750CK (MN Aircraft) was operating from KFLL to KRYY on 2026-08-29. SkyMeter detected a long landing rollout at Cobb County-Mc Collum Field (KRYY) on runway 09 at 19:24 UTC. Trace data at the event: 958 ft AGL, 12 kt GS. METAR at the time reported 9 kt wind, 3 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)
  • SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/2698 2026-01-19 09:00Z – 2026-12-18 21:00Z SFC–5,000 ft

    VIEQUES, PR, Monday, January 19, 2026 through Friday, December 18, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/0299 2026-06-26 04:00Z – 2026-10-18 03:59Z SFC–5,000 ft

    Key West, FL, Friday, June 26, 2026 through Saturday, October 17, 2026 Local

    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 09
  • 958 ft AGL at event
  • 12 kt ground speed
  • 0 fpm vertical
  • 9 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • KRYY 161450Z AUTO 00000KT 10SM SCT030 26/21 A3041 RMK T02600210 MADISHF

Flight context

  • N750CK
  • MN Aircraft
  • C650
  • KFLL → KRYY
  • 2026-08-29 19:24 UTC
  • KRYY runway 09

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