Long landing rollout — MXY377

8NC8 · 32

2026-08-11 02:32 UTC· KALB → 8NC8· BREEZE AVIATION GROUP INC.· BCS3

▶ Replay 📊 Analyse

MXY377 (Breeze Aviation Group) was operating from KALB to 8NC8 on 2026-08-11. SkyMeter detected a long landing rollout at Lake Ridge Aero Park Airport (8NC8) on runway 32 at 02:32 UTC. Trace data at the event: 383 ft AGL, 0 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 1 kt crosswind component. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. 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 →
  • SECURITY6/0879 2026-08-06 12:00Z – 2026-08-14 20:00Z SFC–2,000 ft

    Laurel, MD, Thursday, August 6, 2026 through Friday, August 14, 2026 Local

    View FAA NOTAM →
  • VIP6/2748 2026-08-08 14:00Z – 2026-08-16 22:00Z SFC–4,999 ft

    THURMONT, MD, Saturday, August 8, 2026 through Sunday, August 16, 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

  • Runway 32
  • 383 ft AGL at event
  • 0 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 1 kt crosswind component

Flight context

  • MXY377
  • Breeze Aviation Group
  • BCS3
  • KALB → 8NC8
  • 2026-08-11 02:32 UTC
  • 8NC8 runway 32

All events on this flight

Long landing rollout 02:32:30 UTC · 8NC8 runway 32 · 383 ft AGL · 0 kt GS
Long landing rollout 02:32:30 UTC · 8NC8 runway 32 · 383 ft AGL · 0 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· 8NC8