N124PM (MC AIR) was operating from KMOB to KMIA on 2026-05-13. SkyMeter detected a speed exceedance at 15:18 UTC. Trace data at the event: 11815 ft AGL, 337 kt GS. Approach stability score: 85/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 12 kt wind, 8 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft
OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local
View FAA NOTAM → - HAZARDS6/9917 2026-05-13 12:00Z – 2026-05-22 01:30Z SFC–2,000 ft
18NM S OF HOMERVILLE, GA, Wednesday, May 13, 2026 through Friday, May 22, 2026 UTC
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- 11815 ft AGL at event
- 337 kt ground speed
- 0 fpm vertical
- Approach stability 85/100
- 12 kt wind
- 8 kt crosswind component
Flight context
- N124PM
- MC AIR
- C550
- KMOB → KMIA
- 2026-05-13 15:18 UTC
All events on this flight
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