Long landing rollout — N462BM
KAWO · 342026-06-20 00:43 UTC· GW MATTHEWS AVIATION LLC· E50P
N462BM (GW Matthews Aviation) was inbound to KAWO on 2026-06-20. SkyMeter detected a long landing rollout at Arlington Municipal Airport (KAWO) on runway 34 at 00:43 UTC. Trace data at the event: 108 ft AGL, 3 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 9 kt wind, 7 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)- HAZARDS6/8503 2026-06-15 21:15Z – 2026-06-20 04:00Z SFC–6,500 ft
20NM S YAKIMA, WA, Monday, June 15, 2026 through Saturday, June 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/8961 2026-06-17 15:50Z – 2026-06-24 04:00Z SFC–7,500 ft
11NM NE YAKIMA, WA, Wednesday, June 17, 2026 through Wednesday, June 24, 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 34
- 108 ft AGL at event
- 3 kt ground speed
- 0 fpm vertical
- Approach stability 84/100
- 9 kt wind
- 7 kt crosswind component
- 16,093 m visibility
- METAR KAWO 172256Z AUTO 30004KT 10SM CLR 24/12 A3002 RMK AO2 SLP170 T02390117 $
Flight context
- N462BM
- GW Matthews Aviation
- E50P
- 2026-06-20 00:43 UTC
- KAWO runway 34
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