Long landing rollout — N125DW
KRAS · 122026-07-20 13:08 UTC· KRBD → KRAS· GULF SOUTH MANAGEMENT INC· C525
N125DW (Gulf South Management) was operating from KRBD to KRAS on 2026-07-20. SkyMeter detected a long landing rollout at Mustang Beach Airport (KRAS) on runway 12 at 13:08 UTC. Trace data at the event: 13 ft AGL, 0 kt GS, 0 fpm vertical. METAR at the time reported 11 kt wind, 11 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/3999 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4000 2026-06-01 05:00Z – 2026-07-21 04:59Z
MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/6840 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Mansfield, TX
View FAA NOTAM → - SECURITY6/6839 2026-07-17 23:07Z – 2026-07-21 04:59Z SFC–400 ft
Arlington, TX
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 12
- 13 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 11 kt wind
- 11 kt crosswind component
- 16,093 m visibility
- METAR KRAS 160435Z AUTO 13009KT 10SM CLR 30/26 A3007 RMK AO2 T02970256
Flight context
- N125DW
- Gulf South Management
- C525
- KRBD → KRAS
- 2026-07-20 13:08 UTC
- KRAS runway 12
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