Long landing rollout — EJA285
KRNT · 342026-07-20 21:09 UTC· KGEG → KRNT· NETJETS SALES INC· E545
EJA285 (Netjets Sales) was operating from KGEG to KRNT on 2026-07-20. SkyMeter detected a long landing rollout at Renton Municipal Airport (KRNT) on runway 34 at 21:09 UTC. Trace data at the event: 0 ft AGL, 13 kt GS, 0 fpm vertical. Approach stability score: 47/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 3 kt wind, 1 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/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 → - SECURITY6/8078 2026-07-07 16:07Z – 2026-07-21 06:59Z SFC–400 ft
Airway Heights, WA
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/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 → - 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 34
- 0 ft AGL at event
- 13 kt ground speed
- 0 fpm vertical
- Approach stability 47/100
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KRNT 302353Z 33008KT 10SM CLR 18/09 A3007 RMK AO2 SLP186 T01780094 10183 20139 56020
Flight context
- EJA285
- Netjets Sales
- E545
- KGEG → KRNT
- 2026-07-20 21:09 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