Speed exceedance — GTI338

2026-02-06 19:57 UTC· KLAX → ?· UMB BANK NA TRUSTEE· B77L

▶ Replay 📊 Analyse

GTI338 (UMB Bank NA) had departed KLAX on 2026-02-06. SkyMeter detected a speed exceedance at 19:57 UTC. Trace data at the event: 27926 ft AGL, 381 kt GS. METAR at the time reported 22 kt wind, 13 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 →
  • SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft

    Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 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

  • 27926 ft AGL at event
  • 381 kt ground speed
  • 0 fpm vertical
  • 22 kt wind
  • 13 kt crosswind component

Flight context

  • GTI338
  • UMB Bank NA
  • B77L
  • 2026-02-06 19:57 UTC

All events on this flight

Speed exceedance 19:57:20 UTC · · 27,926 ft AGL · 381 kt GS
Speed exceedance 19:57:27 UTC · · 28,025 ft AGL · 381 kt GS
Speed exceedance 19:57:20 UTC · · 27,926 ft AGL · 381 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