Long landing rollout — ELZ0005
KTRI · 272026-06-28 19:22 UTC· KPIT → KTRI· BALLATOR EQUIPMENT LEASING LLC· E35L
ELZ0005 (Ballator Equipment Leasing) was operating from KPIT to KTRI on 2026-06-28. SkyMeter detected a long landing rollout at Tri-Cities Regional TN/VA Airport (KTRI) on runway 27 at 19:22 UTC. Trace data at the event: 1535 ft AGL, 3 kt GS. Approach stability score: 42/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 8 kt wind, 4 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 →
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 27
- 1535 ft AGL at event
- 3 kt ground speed
- 0 fpm vertical
- Approach stability 42/100
- 8 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KTRI 181253Z 00000KT 10SM SCT018 SCT026 22/20 A3026 RMK AO2 SLP211 T02170200 $
Flight context
- ELZ0005
- Ballator Equipment Leasing
- E35L
- KPIT → KTRI
- 2026-06-28 19:22 UTC
- KTRI runway 27
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