Speed exceedance — N529KG

2026-04-02 22:52 UTC· KBMG KMHT· CAPSTONE MANAGEMENT LLC· F2TH

N529KG (Capstone Management) was operating from KBMG to KMHT on 2026-04-02. SkyMeter detected a speed exceedance at 22:52 UTC. Trace data at the event: 25393 ft AGL, 551 kt GS. Approach stability score: 83/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 7 kt wind, 5 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/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

    NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 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

  • 25393 ft AGL at event
  • 551 kt ground speed
  • 0 fpm vertical
  • Approach stability 83/100
  • 7 kt wind
  • 5 kt crosswind component

Flight context

  • N529KG
  • Capstone Management
  • F2TH
  • KBMG → KMHT
  • 2026-04-02 22:52 UTC

All events on this flight

Speed exceedance 22:52:15 UTC · · 25,393 ft AGL · 551 kt GS
Speed exceedance 22:52:15 UTC · · 25,393 ft AGL · 551 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