Long landing rollout — N549TG

KCPS · 05

2026-07-16 16:19 UTC· KPDK KCPS· SMALJ LLC· E50P

N549TG (Smalj) was operating from KPDK to KCPS on 2026-07-16. SkyMeter detected a long landing rollout at St Louis Downtown Airport (KCPS) on runway 05 at 16:19 UTC. Trace data at the event: 380 ft AGL, 10 kt GS, 0 fpm vertical. Approach stability score: 32/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 1 kt wind, 1 kt crosswind component, 12,875 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/3980 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3990 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4119 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4121 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4161 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/8212 2026-06-17 04:01Z – 2026-07-17 03:59Z SFC–400 ft

    Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7972 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Nashville, TN

    View FAA NOTAM →
  • SECURITY6/7967 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Nashville, TN

    View FAA NOTAM →
  • SECURITY6/7600 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft

    Chattanooga, TN

    View FAA NOTAM →
  • SECURITY6/7597 2026-07-08 16:07Z – 2026-07-21 03:59Z SFC–400 ft

    Marietta, GA

    View FAA NOTAM →
  • SECURITY6/7197 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft

    Louisville, KY

    View FAA NOTAM →
  • SECURITY6/7817 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

    St Louis, MO

    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 05
  • 380 ft AGL at event
  • 10 kt ground speed
  • 0 fpm vertical
  • Approach stability 32/100
  • 1 kt wind
  • 1 kt crosswind component
  • 12,875 m visibility
  • METAR KCPS 170253Z AUTO 14003KT 8SM CLR 24/23 A3023 RMK AO2 SLP232 T02390233 53012 $

Flight context

  • N549TG
  • Smalj
  • E50P
  • KPDK → KCPS
  • 2026-07-16 16:19 UTC
  • KCPS runway 05

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· KCPS