Unstable approach — EJA731
KRNT · 342026-07-31 01:23 UTC· NETJETS SALES INC, LADD CHRISTIANE EDSWORTH AND LADD MARK, COAST· CL35
EJA731 (Netjets Sales) was inbound to KRNT on 2026-07-31. SkyMeter detected a low approach-stability score at Renton Municipal Airport (KRNT) on runway 34 at 01:23 UTC. Trace data at the event: 1104 ft AGL, 135 kt GS. Approach stability score: 41/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, 3 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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/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 → - HAZARDS6/8043 2026-07-23 02:01Z – 2026-08-05 04:00Z SFC–8,500 ft
19NM NW CLE ELUM, WA, Thursday, July 23, 2026 through Wednesday, August 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/8359 2026-07-24 14:00Z – 2026-08-07 05:00Z SFC–8,500 ft
26NM NW LEAVENWORTH, WA, Friday, July 24, 2026 through Friday, August 7, 2026 UTC
View FAA NOTAM → - HAZARDS6/8557 2026-07-25 19:30Z – 2026-08-09 05:00Z SFC–8,500 ft
26NM NW LEAVENWORTH, WA, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8653 2026-07-26 16:00Z – 2026-08-10 05:00Z SFC–13,500 ft
26NM NW LEAVENWORTH, WA, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8887 2026-07-27 14:00Z – 2026-08-10 05:00Z SFC–13,500 ft
26NM NW LEAVENWORTH, WA, Monday, July 27, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/8429 2026-07-30 18:00Z – 2026-08-02 23:59Z SFC–16,000 ft
SEATLE, WA, Thursday, July 30, 2026 through Sunday, August 2, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/8430 2026-07-30 20:00Z – 2026-08-02 22:20Z SFC–5,000 ft
SEATTLE, WA, Thursday, July 30, 2026 through Sunday, August 2, 2026 Local
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
- 1104 ft AGL at event
- 135 kt ground speed
- 0 fpm vertical
- Approach stability 41/100
- 3 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- METAR KRNT 170653Z AUTO 36004KT 10SM CLR 17/13 A3005 RMK AO2 SLP182 T01720133
Flight context
- EJA731
- Netjets Sales
- CL35
- 2026-07-31 01:23 UTC
- KRNT 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