Long landing rollout — N51C

KASG · 36

2026-05-26 20:37 UTC· KTBR → KASG· FIVE ONE CHARLIE LLC· C25A

▶ Replay 📊 Analyse

N51C (Five ONE Charlie) was operating from KTBR to KASG on 2026-05-26. SkyMeter detected a long landing rollout at Springdale Municipal Airport (KASG) on runway 36 at 20:37 UTC. Trace data at the event: 1348 ft AGL, 3 kt GS. METAR at the time reported 4 kt wind, 3 kt crosswind component, 16,093 m visibility. 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/2036 2026-05-22 05:00Z – 2026-05-27 09:30Z SFC–17,999 ft

    Macon, GA, Friday, May 22, 2026 through Wednesday, May 27, 2026 Local

    View FAA NOTAM →
  • SECURITY6/2330 2026-05-23 05:00Z – 2026-05-27 09:30Z SFC–17,999 ft

    Macon, GA, Saturday, May 23, 2026 through Wednesday, May 27, 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 36
  • 1348 ft AGL at event
  • 3 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • METAR KASG 191548Z 22008G15KT 10SM CLR 31/21 A3008

Flight context

  • N51C
  • Five ONE Charlie
  • C25A
  • KTBR → KASG
  • 2026-05-26 20:37 UTC
  • KASG runway 36

All events on this flight

Long landing rollout 20:37:32 UTC · KASG runway 36 · 1,348 ft AGL · 3 kt GS
Long landing rollout 20:37:32 UTC · KASG runway 36 · 1,348 ft AGL · 3 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· KASG