Long landing rollout — SWA300
US-11532 · 352026-06-15 20:40 UTC· KSMF → ?· SOUTHWEST AIRLINES CO· B737
SWA300 (Southwest Airlines) had departed KSMF on 2026-06-15. SkyMeter detected a long landing rollout at US-11532 (US-11532) on runway 35 at 20:40 UTC. Trace data at the event: 915 ft AGL, 11 kt GS. METAR at the time reported 6 kt wind, 4 kt crosswind component. 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/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft
SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local
View FAA NOTAM → - SECURITY6/4189 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4192 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4197 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
GOLETA, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/8214 2026-06-14 17:34Z – 2026-06-17 07:00Z SFC–400 ft
3.8NM NW TRACY, CA, Sunday, June 14, 2026 through Wednesday, June 17, 2026 UTC
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 35
- 915 ft AGL at event
- 11 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 4 kt crosswind component
Flight context
- SWA300
- Southwest Airlines
- B737
- 2026-06-15 20:40 UTC
- US-11532 runway 35
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