Long landing rollout — XSR325
2M1 · 032026-07-11 13:47 UTC· KMKC → 2M1· EXECUTIVE AIRSHARE LLC, RIVIERE ENERGY LLC, KNSSE LLC, L&E LLC, · E55P
XSR325 (Executive Airshare) was operating from KMKC to 2M1 on 2026-07-11. SkyMeter detected a long landing rollout at Harry S Truman Regional Airport (2M1) on runway 03 at 13:47 UTC. Trace data at the event: 1000 ft AGL, 0 kt GS. METAR at the time reported 4 kt wind, 1 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/4151 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4162 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7650 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO
View FAA NOTAM → - SECURITY6/3215 2026-07-09 05:01Z – 2026-07-12 04:59Z SFC–1,000 ft
Kansas City, MO, Thursday, July 9, 2026 through Saturday, July 11, 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 03
- 1000 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 1 kt crosswind component
Flight context
- XSR325
- Executive Airshare
- E55P
- KMKC → 2M1
- 2026-07-11 13:47 UTC
- 2M1 runway 03
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