Long landing rollout — LXJ324
KRYY · 092026-07-21 17:29 UTC· KISM → KRYY· BOARDWALK AUTO GROUP LLC, BANCINSURANCE CORP, HAY LEWIS III, NIC· E545
LXJ324 (Boardwalk Auto Group) was operating from KISM to KRYY on 2026-07-21. SkyMeter detected a long landing rollout at Cobb County-Mc Collum Field (KRYY) on runway 09 at 17:29 UTC. Trace data at the event: 1040 ft AGL, 0 kt GS. Approach stability score: 61/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 5 kt wind, 5 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/6747 2026-07-20 12:30Z – 2026-07-24 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, July 20, 2026 through Friday, July 24, 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
- 1040 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 61/100
- 5 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KRYY 162150Z AUTO 10008KT 10SM CLR 32/19 A3030 RMK T03200190 MADISHF
Flight context
- LXJ324
- Boardwalk Auto Group
- E545
- KISM → KRYY
- 2026-07-21 17:29 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