Long landing rollout — AAY1785

N43 · 18

2026-05-31 17:37 UTC· KMCO N43· ALLEGIANT AIR LLC· A320

AAY1785 (Allegiant AIR) was operating from KMCO to N43 on 2026-05-31. SkyMeter detected a long landing rollout at Braden Airpark (N43) on runway 18 at 17:37 UTC. Trace data at the event: 374 ft AGL, 12 kt GS, 0 fpm vertical. Approach stability score: 46/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 9 kt wind, 7 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)
  • SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft

    Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 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 18
  • 374 ft AGL at event
  • 12 kt ground speed
  • 0 fpm vertical
  • Approach stability 46/100
  • 9 kt wind
  • 7 kt crosswind component

Flight context

  • AAY1785
  • Allegiant AIR
  • A320
  • KMCO → N43
  • 2026-05-31 17:37 UTC
  • N43 runway 18

All events on this flight

Long landing rollout 17:37:49 UTC · N43 runway 18 · 374 ft AGL · 12 kt GS
Long landing rollout 17:37:49 UTC · N43 runway 18 · 374 ft AGL · 12 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· N43