Unstable approach — N165EA

2Q5 · 24

2026-08-10 20:38 UTC· KRNO 2Q5· MAHAN RYAN· PIAT

N165EA (Mahan Ryan) was operating from KRNO to 2Q5 on 2026-08-10. SkyMeter detected a low approach-stability score at Parker Carson Airport (2Q5) on runway 24 at 20:38 UTC. Trace data at the event: 5459 ft AGL, 83 kt GS. Approach stability score: 26/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 9 kt wind, 1 kt crosswind component. 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.

Pilot review data

  • Runway 24
  • 5459 ft AGL at event
  • 83 kt ground speed
  • 0 fpm vertical
  • Approach stability 26/100
  • 9 kt wind
  • 1 kt crosswind component

Flight context

  • N165EA
  • Mahan Ryan
  • PIAT
  • KRNO → 2Q5
  • 2026-08-10 20:38 UTC
  • 2Q5 runway 24

All events on this flight

Unstable approach 20:38:17 UTC · 2Q5 runway 24 · 5,459 ft AGL · 83 kt GS
Long landing rollout 20:42:46 UTC · 2Q5 runway 24 · 4,396 ft AGL · 2 kt GS
Unstable approach 20:38:17 UTC · 2Q5 runway 24 · 5,459 ft AGL · 83 kt GS
Long landing rollout 20:42:46 UTC · 2Q5 runway 24 · 4,396 ft AGL · 2 kt GS

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· 2Q5