Long landing rollout — SWB80
KVQQ · 27L2026-01-19 21:39 UTC· KRIV → KVQQ· WILMINGTON TRUST CO TRUSTEE· K35R
SWB80 (Wilmington Trust) was operating from KRIV to KVQQ on 2026-01-19. SkyMeter detected a long landing rollout at Cecil Airport (KVQQ) on runway 27L at 21:39 UTC. Trace data at the event: 82 ft AGL, 9 kt GS, 0 fpm vertical. Approach stability score: 84/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 4 kt wind, 12,875 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/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 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 27L
- 82 ft AGL at event
- 9 kt ground speed
- 0 fpm vertical
- Approach stability 84/100
- 4 kt wind
- 0 kt crosswind component
- 12,875 m visibility
- METAR KVQQ 261050Z 00000KT 8SM CLR 12/12 A2996
Flight context
- SWB80
- Wilmington Trust
- K35R
- KRIV → KVQQ
- 2026-01-19 21:39 UTC
- KVQQ runway 27L
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