Speed exceedance — LFO73X

2026-06-25 10:04 UTC· EDVE EDVE· F2TH

LFO73X was operating from EDVE to EDVE on 2026-06-25. SkyMeter detected a speed exceedance at 10:04 UTC. Trace data at the event: 24120 ft AGL, 498 kt GS. Approach stability score: 83/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 6 kt wind, 5 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

  • 24120 ft AGL at event
  • 498 kt ground speed
  • 0 fpm vertical
  • Approach stability 83/100
  • 6 kt wind
  • 5 kt crosswind component

Flight context

  • LFO73X
  • F2TH
  • EDVE → EDVE
  • 2026-06-25 10:04 UTC

All events on this flight

Speed exceedance 10:04:39 UTC · · 24,120 ft AGL · 498 kt GS
Speed exceedance 10:09:53 UTC · · 22,647 ft AGL · 482 kt GS
Speed exceedance 10:47:46 UTC · · 26,822 ft AGL · 544 kt GS
EmergencyDescent 11:15:09 UTC · · 41,302 ft AGL · 456 kt GS
Upset 11:15:57 UTC · · 30,721 ft AGL · 475 kt GS
Speed exceedance 10:04:39 UTC · · 24,120 ft AGL · 498 kt GS
Speed exceedance 10:09:53 UTC · · 22,647 ft AGL · 482 kt GS
Speed exceedance 10:47:46 UTC · · 26,822 ft AGL · 544 kt GS
EmergencyDescent 11:15:09 UTC · · 41,302 ft AGL · 456 kt GS
Upset 11:15:57 UTC · · 30,721 ft AGL · 475 kt GS
Speed exceedance 10:04:39 UTC · · 24,120 ft AGL · 498 kt GS
Speed exceedance 10:09:53 UTC · · 22,647 ft AGL · 482 kt GS
Speed exceedance 10:47:46 UTC · · 26,822 ft AGL · 544 kt GS
EmergencyDescent 11:15:09 UTC · · 41,302 ft AGL · 456 kt GS
Upset 11:15:57 UTC · · 30,721 ft AGL · 475 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