Long landing rollout — TEST
KVRB · 30L2026-07-06 14:08 UTC· KPNE → KHMZ· MUSTANG SALLY LLC· C680
TEST (Mustang Sally) was operating from KPNE to KHMZ on 2026-07-06. SkyMeter detected a long landing rollout at Vero Beach Regional Airport (KVRB) on runway 30L at 14:08 UTC. Trace data at the event: 22 ft AGL, 5 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 2 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/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3967 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PHILADELPHIA, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - 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/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4007 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6442 2026-06-10 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft
Philadelphia, PA, Wednesday, June 10, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/7169 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV
View FAA NOTAM → - VIP6/2833 2026-07-04 22:45Z – 2026-07-06 22:00Z SFC–4,999 ft
MIDDLEBURG, VA, Saturday, July 4, 2026 through Monday, July 6, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/1901 2026-07-06 10:03Z – 2026-07-06 14:55Z SFC–180 ft
Cape Canaveral, FL, Monday, July 6, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/1911 2026-07-06 10:03Z – 2026-07-06 14:55Z SFC–180 ft
Cape Canaveral, FL, Monday, July 6, 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
- 5 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KVRB 180553Z AUTO 08003KT 10SM FEW028 24/23 A3006 RMK AO2 SLP178 T02440233 10278 20244 58008
Flight context
- TEST
- Mustang Sally
- C680
- KPNE → KHMZ
- 2026-07-06 14:08 UTC
- KVRB runway 30L
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