Unstable approach — GAF204

EDDV · 09C

2026-05-08 16:44 UTC· A400

GAF204 was inbound to EDDV on 2026-05-08. SkyMeter detected a low approach-stability score at Hannover Airport (EDDV) on runway 09C at 16:44 UTC. Trace data at the event: 1058 ft AGL, 232 kt GS. Approach stability score: 42/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, 9,994 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 09C
  • 1058 ft AGL at event
  • 232 kt ground speed
  • 0 fpm vertical
  • Approach stability 42/100
  • 5 kt wind
  • 2 kt crosswind component
  • 9,994 m visibility
  • EDDV 161650Z AUTO 27009KT 9999 -SHRA FEW///TCU 17/12 Q1013 TEMPO SHRA BKN020CB

Flight context

  • GAF204
  • A400
  • 2026-05-08 16:44 UTC
  • EDDV runway 09C

All events on this flight

Unstable approach 16:44:39 UTC · EDDV runway 09C · 1,058 ft AGL · 232 kt GS
Long landing rollout 16:54:03 UTC · EDDV runway 09C · 183 ft AGL · 0 kt GS
Unstable approach 16:44:39 UTC · EDDV runway 09C · 1,058 ft AGL · 232 kt GS
Long landing rollout 16:54:03 UTC · EDDV runway 09C · 183 ft AGL · 0 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· EDDV