Speed exceedance — HMR21

2026-08-11 06:48 UTC· OJMF OJ38· AT8T

HMR21 was operating from OJMF to OJ38 on 2026-08-11. SkyMeter detected a speed exceedance at 06:48 UTC. Trace data at the event: 14764 ft AGL, 293 kt GS. Approach stability score: 27/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 6 kt wind, 6 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

  • 14764 ft AGL at event
  • 293 kt ground speed
  • 0 fpm vertical
  • Approach stability 27/100
  • 6 kt wind
  • 6 kt crosswind component

Flight context

  • HMR21
  • AT8T
  • OJMF → OJ38
  • 2026-08-11 06:48 UTC

All events on this flight

Speed exceedance 06:48:30 UTC · · 14,764 ft AGL · 293 kt GS
Speed exceedance 06:49:51 UTC · · 15,055 ft AGL · 258 kt GS
Speed exceedance 06:51:12 UTC · · 15,082 ft AGL · 281 kt GS
Speed exceedance 06:52:00 UTC · · 14,797 ft AGL · 288 kt GS
Speed exceedance 06:58:51 UTC · · 14,680 ft AGL · 253 kt GS
Speed exceedance 07:01:01 UTC · · 14,776 ft AGL · 253 kt GS
Speed exceedance 07:02:04 UTC · · 12,600 ft AGL · 258 kt GS
Speed exceedance 07:04:14 UTC · · 12,748 ft AGL · 283 kt GS
Speed exceedance 07:04:56 UTC · · 12,812 ft AGL · 294 kt GS
Speed exceedance 07:06:19 UTC · · 13,015 ft AGL · 325 kt GS
Speed exceedance 07:07:00 UTC · · 12,705 ft AGL · 321 kt GS
Speed exceedance 07:10:05 UTC · · 12,842 ft AGL · 274 kt GS
Speed exceedance 07:13:10 UTC · · 12,686 ft AGL · 299 kt GS
Speed exceedance 07:14:02 UTC · · 12,884 ft AGL · 256 kt GS
Speed exceedance 07:17:34 UTC · · 14,180 ft AGL · 291 kt GS
Speed exceedance 07:18:39 UTC · · 14,081 ft AGL · 337 kt GS
Speed exceedance 07:19:58 UTC · · 14,280 ft AGL · 307 kt GS
Speed exceedance 07:22:33 UTC · · 13,329 ft AGL · 255 kt GS
Speed exceedance 07:27:15 UTC · · 13,967 ft AGL · 272 kt GS
Speed exceedance 07:27:47 UTC · · 13,980 ft AGL · 291 kt GS
Speed exceedance 07:29:03 UTC · · 12,330 ft AGL · 322 kt GS
Speed exceedance 07:35:33 UTC · · 14,154 ft AGL · 296 kt GS
Speed exceedance 07:38:00 UTC · · 13,920 ft AGL · 295 kt GS
Speed exceedance 07:40:09 UTC · · 14,375 ft AGL · 256 kt GS
Speed exceedance 07:41:01 UTC · · 14,578 ft AGL · 278 kt GS
Speed exceedance 07:44:01 UTC · · 13,688 ft AGL · 265 kt GS
Speed exceedance 07:46:00 UTC · · 13,799 ft AGL · 252 kt GS
Speed exceedance 07:48:49 UTC · · 10,817 ft AGL · 317 kt GS
Speed exceedance 07:49:36 UTC · · 7,515 ft AGL · 279 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