Speed exceedance — APX11

2026-08-10 06:35 UTC· OJMF OJ38· AT8T

APX11 was operating from OJMF to OJ38 on 2026-08-10. SkyMeter detected a speed exceedance at 06:35 UTC. Trace data at the event: 13923 ft AGL, 263 kt GS. Approach stability score: 37/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, 4 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

  • 13923 ft AGL at event
  • 263 kt ground speed
  • 0 fpm vertical
  • Approach stability 37/100
  • 4 kt wind
  • 4 kt crosswind component

Flight context

  • APX11
  • AT8T
  • OJMF → OJ38
  • 2026-08-10 06:35 UTC

All events on this flight

Speed exceedance 06:35:44 UTC · · 13,923 ft AGL · 263 kt GS
Speed exceedance 06:37:22 UTC · · 14,057 ft AGL · 295 kt GS
Speed exceedance 06:38:46 UTC · · 15,230 ft AGL · 280 kt GS
Speed exceedance 06:39:32 UTC · · 14,183 ft AGL · 284 kt GS
Speed exceedance 06:40:27 UTC · · 14,939 ft AGL · 277 kt GS
Speed exceedance 06:43:09 UTC · · 14,937 ft AGL · 263 kt GS
Speed exceedance 06:43:41 UTC · · 14,406 ft AGL · 300 kt GS
Speed exceedance 06:46:19 UTC · · 14,959 ft AGL · 329 kt GS
Speed exceedance 06:47:10 UTC · · 14,655 ft AGL · 331 kt GS
Speed exceedance 06:49:12 UTC · · 14,879 ft AGL · 303 kt GS
Speed exceedance 06:50:27 UTC · · 14,909 ft AGL · 257 kt GS
Speed exceedance 06:53:18 UTC · · 14,949 ft AGL · 308 kt GS
Speed exceedance 06:54:00 UTC · · 14,917 ft AGL · 308 kt GS
Speed exceedance 06:58:14 UTC · · 15,068 ft AGL · 273 kt GS
Speed exceedance 06:59:16 UTC · · 15,030 ft AGL · 299 kt GS
Speed exceedance 07:02:22 UTC · · 14,820 ft AGL · 274 kt GS
Speed exceedance 07:05:53 UTC · · 14,949 ft AGL · 335 kt GS
Speed exceedance 07:06:41 UTC · · 14,833 ft AGL · 335 kt GS
Speed exceedance 07:07:22 UTC · · 15,261 ft AGL · 290 kt GS
Speed exceedance 07:08:21 UTC · · 15,158 ft AGL · 253 kt GS
Speed exceedance 07:10:03 UTC · · 14,885 ft AGL · 284 kt GS
Speed exceedance 07:12:04 UTC · · 14,690 ft AGL · 292 kt GS
Speed exceedance 07:12:45 UTC · · 15,171 ft AGL · 258 kt GS
Speed exceedance 07:17:46 UTC · · 14,386 ft AGL · 330 kt GS
Speed exceedance 07:18:41 UTC · · 13,767 ft AGL · 308 kt GS
Speed exceedance 07:19:38 UTC · · 13,667 ft AGL · 301 kt GS
Speed exceedance 07:24:56 UTC · · 13,768 ft AGL · 252 kt GS
Speed exceedance 07:25:32 UTC · · 13,444 ft AGL · 267 kt GS
Speed exceedance 07:27:48 UTC · · 11,327 ft AGL · 320 kt GS
Speed exceedance 07:28:34 UTC · · 11,006 ft AGL · 291 kt GS
Speed exceedance 07:29:31 UTC · · 10,573 ft AGL · 279 kt GS
Speed exceedance 07:30:45 UTC · · 6,864 ft AGL · 276 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