Go-around — N253AL

KRNT · 34

2026-08-20 07:34 UTC· CORSAIR TWO LLC· LJ45

N253AL (Corsair TWO) was inbound to KRNT on 2026-08-20. SkyMeter detected a go-around at Renton Municipal Airport (KRNT) on runway 34 at 07:34 UTC. Trace data at the event: 1506 ft AGL, 151 kt GS. METAR at the time reported 2 kt wind, 1 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/5870 2026-08-17 22:30Z – 2026-08-21 04:00Z SFC–10,000 ft

    21NM S PORT ANGELES, WA, Monday, August 17, 2026 through Friday, August 21, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5939 2026-08-18 14:00Z – 2026-08-31 05:00Z SFC–10,000 ft

    21NM S PORT ANGELES, WA, Tuesday, August 18, 2026 through Monday, August 31, 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
  • 1506 ft AGL at event
  • 151 kt ground speed
  • 0 fpm vertical
  • 2 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • METAR KRNT 150753Z AUTO 00000KT 10SM BKN060 14/12 A3005 RMK AO2 SLP181 T01390122 402000128

Flight context

  • N253AL
  • Corsair TWO
  • LJ45
  • 2026-08-20 07:34 UTC
  • KRNT runway 34

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

SkyMeter · trace data observed via ADS-B· KRNT