Unstable approach — COOL29

KDLF · 31C

2026-01-14 20:01 UTC· KAFW → KDLF· T38

COOL29 was operating from KAFW to KDLF on 2026-01-14. SkyMeter detected a low approach-stability score at Laughlin Air Force Base (KDLF) on runway 31C at 20:01 UTC. Trace data at the event: 2146 ft AGL, 210 kt GS. Approach stability score: 31/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 13 kt wind, 7 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.

Pilot review data

  • Runway 31C
  • 2146 ft AGL at event
  • 210 kt ground speed
  • 0 fpm vertical
  • Approach stability 31/100
  • 13 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • SPECI KDLF 261024Z AUTO 12005KT 10SM FEW025 OVC080 28/21 A2994 RMK AO2 LTG DSNT N RAE24 SLP123 $

Flight context

  • COOL29
  • T38
  • KAFW → KDLF
  • 2026-01-14 20:01 UTC
  • KDLF runway 31C

All events on this flight

Unstable approach 20:01:27 UTC · KDLF runway 31C · 2,146 ft AGL · 210 kt GS
Long landing rollout 20:04:38 UTC · KDLF runway 31C · 1,099 ft AGL · 10 kt GS
Unstable approach 19:54:40 UTC · KDLF runway 31R · 2,084 ft AGL · 252 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· KDLF