CYO975 (ATI JET) was operating from 61FD to KBLM on 2026-05-17. SkyMeter detected a speed exceedance at 17:17 UTC. Trace data at the event: 12320 ft AGL, 379 kt GS. Approach stability score: 73/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 2 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/9056 2026-05-11 11:00Z – 2026-05-18 02:00Z SFC–400 ft
Newtown Square, PA, Monday, May 11, 2026 through Sunday, May 17, 2026 Local
View FAA NOTAM → - SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft
Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local
View FAA NOTAM → - VIP6/0904 2026-05-17 14:30Z – 2026-05-17 23:59Z SFC–9,999 ft
Sterling, VA, Sunday, May 17, 2026 Local
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
- 12320 ft AGL at event
- 379 kt ground speed
- 0 fpm vertical
- Approach stability 73/100
- 2 kt wind
- 2 kt crosswind component
Flight context
- CYO975
- ATI JET
- LJ60
- 61FD → KBLM
- 2026-05-17 17:17 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