Long landing rollout — TEST
KVRB · 30L2026-06-20 16:28 UTC· KBCT → KVRB· MUSTANG SALLY LLC· C680
TEST (Mustang Sally) was operating from KBCT to KVRB on 2026-06-20. SkyMeter detected a long landing rollout at Vero Beach Regional Airport (KVRB) on runway 30L at 16:28 UTC. Trace data at the event: 22 ft AGL, 13 kt GS, 0 fpm vertical. Approach stability score: 66/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 4 kt wind, 1 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/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL, 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 30L
- 22 ft AGL at event
- 13 kt ground speed
- 0 fpm vertical
- Approach stability 66/100
- 4 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KVRB 181953Z 08006KT 10SM SCT018 28/24 A3003 RMK AO2 LTG DSNT SE AND S SLP167 T02780239
Flight context
- TEST
- Mustang Sally
- C680
- KBCT → KVRB
- 2026-06-20 16:28 UTC
- KVRB runway 30L
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