Long landing rollout — SWA193
W48 · 162026-07-27 17:08 UTC· KMCO → W48· UMB BANK NA TRUSTEE· B738
SWA193 (UMB Bank NA) was operating from KMCO to W48 on 2026-07-27. SkyMeter detected a long landing rollout at Essex Skypark Airport (W48) on runway 16 at 17:08 UTC. Trace data at the event: 147 ft AGL, 8 kt GS, 0 fpm vertical. Approach stability score: 46/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 1 kt wind. 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)- HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - SECURITY6/8418 2026-07-27 12:30Z – 2026-08-01 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, July 27, 2026 through Saturday, August 1, 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 16
- 147 ft AGL at event
- 8 kt ground speed
- 0 fpm vertical
- Approach stability 46/100
- 1 kt wind
- 0 kt crosswind component
Flight context
- SWA193
- UMB Bank NA
- B738
- KMCO → W48
- 2026-07-27 17:08 UTC
- W48 runway 16
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