Rejected takeoff — BOE352
KRNT · 162026-07-20 22:36 UTC· KRNT → ?· SOUTHWEST AIRLINES CO.· B38M
BOE352 (Southwest Airlines) had departed KRNT on 2026-07-20. SkyMeter detected a rejectedtakeoff at Renton Municipal Airport (KRNT) on runway 16 at 22:36 UTC. Trace data at the event: 3 ft AGL, 81 kt GS, 0 fpm vertical. METAR at the time reported 2 kt wind, 2 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4011 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4013 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Seattle, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4034 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/4560 2026-07-10 14:00Z – 2026-07-24 06:00Z SFC–7,500 ft
5NM SW OMAK, WA, Friday, July 10, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - SECURITY6/8073 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA
View FAA NOTAM → - SECURITY6/8074 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA
View FAA NOTAM → - SECURITY6/8080 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Seattle, WA
View FAA NOTAM → - SECURITY6/8081 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Bellevue, WA
View FAA NOTAM → - HAZARDS6/6309 2026-07-16 20:32Z – 2026-07-31 04:00Z SFC–7,000 ft
50NM SW COLVILLE, WA, Thursday, July 16, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6314 2026-07-16 21:42Z – 2026-07-31 04:00Z SFC–8,500 ft
12NM NW CLE ELUM, WA, Thursday, July 16, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6401 2026-07-17 04:01Z – 2026-07-31 04:00Z SFC–8,500 ft
12NM NW CLE ELUM, WA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6362 2026-07-17 15:00Z – 2026-07-31 03:00Z SFC–7,000 ft
50NM SW COLVILLE, WA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6571 2026-07-18 02:41Z – 2026-07-31 04:00Z SFC–3,500 ft
19NM S MOSES LAKE, WA, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6755 2026-07-19 15:30Z – 2026-08-02 04:00Z SFC–7,000 ft
50NM SW COLVILLE, WA, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC
View FAA NOTAM → - SECURITY6/6147 2026-07-19 16:00Z – 2026-07-24 04:00Z SFC–1,000 ft
Bellevue, WA, Sunday, July 19, 2026 through Thursday, July 23, 2026 Local
View FAA NOTAM → - HAZARDS6/6854 2026-07-20 01:18Z – 2026-08-04 03:00Z SFC–7,500 ft
34NM NW WENATCHEE, WA, Monday, July 20, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/6891 2026-07-20 15:00Z – 2026-08-04 04:00Z SFC–7,500 ft
34NM NW WENATCHEE, WA, Monday, July 20, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/7044 2026-07-20 18:15Z – 2026-08-04 04:00Z SFC–9,500 ft
34NM NW WENATCHEE, WA, Monday, July 20, 2026 through Tuesday, August 4, 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 16
- 3 ft AGL at event
- 81 kt ground speed
- 0 fpm vertical
- 2 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- METAR KRNT 160653Z AUTO 00000KT 10SM CLR 15/12 A3010 RMK AO2 SLP198 T01500117
Flight context
- BOE352
- Southwest Airlines
- B38M
- 2026-07-20 22:36 UTC
- KRNT 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