Long landing rollout — JTZ623
KROA · 342026-06-28 19:34 UTC· NICHOLAS SERVICES LLC· CL35
JTZ623 (Nicholas Services) was inbound to KROA on 2026-06-28. SkyMeter detected a long landing rollout at Roanoke–Blacksburg Regional Airport (KROA) on runway 34 at 19:34 UTC. Trace data at the event: 1095 ft AGL, 16 kt GS. Approach stability score: 88/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. 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/3970 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 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 34
- 1095 ft AGL at event
- 16 kt ground speed
- 0 fpm vertical
- Approach stability 88/100
- 5 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KROA 181354Z 27006KT 10SM FEW040 28/21 A3019 RMK AO2 SLP210 T02780206
Flight context
- JTZ623
- Nicholas Services
- CL35
- 2026-06-28 19:34 UTC
- KROA runway 34
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