Speed exceedance — AMB317

2026-07-09 16:53 UTC· EHLE EDSB· LJ35

AMB317 was operating from EHLE to EDSB on 2026-07-09. SkyMeter detected a speed exceedance at 16:53 UTC. Trace data at the event: 16573 ft AGL, 413 kt GS. Approach stability score: 33/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 4 kt wind, 2 kt crosswind component. An overspeed flag is raised when observed indicated airspeed exceeds the aircraft type's published Vmo (maximum operating speed) or Mmo (maximum operating Mach). Compressibility-correction bugs were a major false-positive source on the E75L and CRJ9 fleets prior to April 2026; current flags use the corrected IAS calculation. Detection algorithm and known limitations: see SkyMeter methodology.

Pilot review data

  • 16573 ft AGL at event
  • 413 kt ground speed
  • 0 fpm vertical
  • Approach stability 33/100
  • 4 kt wind
  • 2 kt crosswind component

Flight context

  • AMB317
  • LJ35
  • EHLE → EDSB
  • 2026-07-09 16:53 UTC

All events on this flight

Speed exceedance 16:53:06 UTC · · 16,573 ft AGL · 413 kt GS
Unstable approach 16:59:20 UTC · EDSB runway 03 · 1,241 ft AGL · 148 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