Long landing rollout — STY543
KNY2 · 282026-08-12 16:51 UTC· KSRQ → KNY2· ALTIUS AVIATION LLC, BERWYN PROPERTIES LLC· LJ60
STY543 (Altius Aviation) was operating from KSRQ to KNY2 on 2026-08-12. SkyMeter detected a long landing rollout at Camillus Airport (KNY2) on runway 28 at 16:51 UTC. Trace data at the event: 419 ft AGL, 9 kt GS, 0 fpm vertical. METAR at the time reported 7 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/0879 2026-08-06 12:00Z – 2026-08-14 20:00Z SFC–2,000 ft
Laurel, MD, Thursday, August 6, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - VIP6/2748 2026-08-08 14:00Z – 2026-08-16 22:00Z SFC–4,999 ft
THURMONT, MD, Saturday, August 8, 2026 through Sunday, August 16, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/2788 2026-08-12 13:54Z – 2026-08-12 18:46Z SFC–180 ft
Cape Canaveral, FL, Wednesday, August 12, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/2789 2026-08-12 13:54Z – 2026-08-12 18:46Z SFC–180 ft
Cape Canaveral, FL, Wednesday, August 12, 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 28
- 419 ft AGL at event
- 9 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 1 kt crosswind component
Flight context
- STY543
- Altius Aviation
- LJ60
- KSRQ → KNY2
- 2026-08-12 16:51 UTC
- KNY2 runway 28
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