Long landing rollout — MXY744

8NC8 · 32

2026-08-07 12:42 UTC· KRSW 8NC8· BREEZE AVIATION GROUP INC· BCS3

MXY744 (Breeze Aviation Group) was operating from KRSW to 8NC8 on 2026-08-07. SkyMeter detected a long landing rollout at Lake Ridge Aero Park Airport (8NC8) on runway 32 at 12:42 UTC. Trace data at the event: 383 ft AGL, 5 kt GS, 0 fpm vertical. METAR at the time reported 5 kt wind, 3 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0929 2026-08-03 12:30Z – 2026-08-08 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, August 3, 2026 through Saturday, August 8, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/2145 2026-08-07 12:00Z – 2026-08-07 14:00Z SFC–2,000 ft

    BARTOW, FL, Friday, August 7, 2026 UTC

    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
  • 5 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 3 kt crosswind component

Flight context

  • MXY744
  • Breeze Aviation Group
  • BCS3
  • KRSW → 8NC8
  • 2026-08-07 12:42 UTC
  • 8NC8 runway 32

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