Unstable approach — C2010

PADQ · 25

2026-07-29 19:48 UTC· PADQ PADQ· C30J

C2010 was operating from PADQ to PADQ on 2026-07-29. SkyMeter detected a low approach-stability score at Kodiak Airport (PADQ) on runway 25 at 19:48 UTC. Trace data at the event: 1032 ft AGL, 135 kt GS. Approach stability score: 32/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 5 kt wind, 2 kt crosswind component, 3,219 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.

Pilot review data

  • Runway 25
  • 1032 ft AGL at event
  • 135 kt ground speed
  • 0 fpm vertical
  • Approach stability 32/100
  • 5 kt wind
  • 2 kt crosswind component
  • 3,219 m visibility
  • PADQ 122353Z 06011KT 2SM RA BR BKN008 OVC013 12/12 A3021 RMK AO2 SLP231 P0012 60017 T01220117 10133 20117 58007 $

Flight context

  • C2010
  • C30J
  • PADQ → PADQ
  • 2026-07-29 19:48 UTC
  • PADQ runway 25

All events on this flight

Unstable approach 19:48:25 UTC · PADQ runway 25 · 1,032 ft AGL · 135 kt GS
Unstable approach 19:48:25 UTC · PADQ runway 25 · 1,032 ft AGL · 135 kt GS
Unstable approach 19:48:25 UTC · PADQ runway 26 · 1,032 ft AGL · 135 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· PADQ