Long landing rollout — CNS1
6B6 · 302026-07-24 21:17 UTC· KBKV → KPSM· SCHWARTZ ERIC S, KEITH D BEATY, PINK SANDS VENTURES LLC, CREWS G· PC24
CNS1 (Schwartz Eric S) was operating from KBKV to KPSM on 2026-07-24. SkyMeter detected a long landing rollout at Minute Man Air Field (6B6) on runway 30 at 21:17 UTC. Trace data at the event: 121 ft AGL, 16 kt GS, 0 fpm vertical. Approach stability score: 58/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, 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)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - VIP6/8360 2026-07-24 19:00Z – 2026-07-26 23:00Z SFC–4,999 ft
Middleburg, VA, Friday, July 24, 2026 through Sunday, July 26, 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 30
- 121 ft AGL at event
- 16 kt ground speed
- 0 fpm vertical
- Approach stability 58/100
- 5 kt wind
- 2 kt crosswind component
Flight context
- CNS1
- Schwartz Eric S
- PC24
- KBKV → KPSM
- 2026-07-24 21:17 UTC
- 6B6 runway 30
All events on this flight
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