Long landing rollout — N96TE

KPDK · 21L

2026-05-31 23:15 UTC· FLCR EXPRESS LLC, WESTWARD BOUND LLC· C56X

N96TE (Flcr Express) was inbound to KPDK on 2026-05-31. SkyMeter detected a long landing rollout at DeKalb Peachtree Airport (KPDK) on runway 21L at 23:15 UTC. Trace data at the event: 980 ft AGL, 14 kt GS. METAR at the time reported 7 kt wind, 7 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/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft

    Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/3292 2026-05-27 17:20Z – 2026-06-10 00:15Z SFC–2,000 ft

    22NM SW TALLAHASSEE, FL, Wednesday, May 27, 2026 through Wednesday, June 10, 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 21L
  • 980 ft AGL at event
  • 14 kt ground speed
  • 0 fpm vertical
  • 7 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • KPDK 161653Z 00000KT 10SM SCT036 29/20 A3037 RMK AO2 SLP266 T02890200

Flight context

  • N96TE
  • Flcr Express
  • C56X
  • 2026-05-31 23:15 UTC
  • KPDK runway 21L

All events on this flight

Long landing rollout 23:15:59 UTC · KPDK runway 21L · 980 ft AGL · 14 kt GS
Long landing rollout 23:15:59 UTC · KPDK runway 21L · 980 ft AGL · 14 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· KPDK