Long landing rollout — EJA562
KLSE · 182026-07-19 19:53 UTC· KGRB → KSWF· NETJETS SALES INC, CHAPMAN FIELD LLC, FIS INC, MEH PSG LLC, TCT · C68A
EJA562 (Netjets Sales) was operating from KGRB to KSWF on 2026-07-19. SkyMeter detected a long landing rollout at La Crosse Municipal Airport (KLSE) on runway 18 at 19:53 UTC. Trace data at the event: 643 ft AGL, 0 kt GS. Approach stability score: 54/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 4 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)- SECURITY6/5591 2026-07-15 17:00Z – 2026-07-20 04:59Z SFC–400 ft
Hammond, IN, Wednesday, July 15, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/5201 2026-07-19 17:00Z – 2026-07-20 04:30Z SFC–400 ft
madison, WI, Sunday, July 19, 2026 through Monday, July 20, 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 18
- 643 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 54/100
- 4 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KLSE 162053Z 13005KT 10SM CLR 23/12 A3028 RMK AO2 SLP251 T02330117 58017
Flight context
- EJA562
- Netjets Sales
- C68A
- KGRB → KSWF
- 2026-07-19 19:53 UTC
- KLSE runway 18
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