Speed exceedance — N797PG

N797PG (Endless Aviation) was inbound to MWCR on 2026-07-07. SkyMeter detected a speed exceedance at 22:35 UTC. Trace data at the event: 26170 ft AGL, 507 kt GS. Approach stability score: 79/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 13 kt wind, 12 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.

• SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/0299 2026-06-26 04:00Z – 2026-10-18 03:59Z SFC–5,000 ft

  Key West, FL, Friday, June 26, 2026 through Saturday, October 17, 2026 Local

  View FAA NOTAM →
• SECURITY6/7880 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

  Tampa, FL

  View FAA NOTAM →
• SECURITY6/7881 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

  Tampa, FL

  View FAA NOTAM →
• SECURITY6/2665 2026-07-07 12:30Z – 2026-07-11 06:00Z SFC–2,500 ft

  MAYPORT, FL, Tuesday, July 7, 2026 through Saturday, July 11, 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.

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