Long landing rollout — JRE844

KF45 · 08L

2026-07-09 19:54 UTC· FE5344 LLC· C56X

▶ Replay 📊 Analyse

JRE844 (Fe5344) was inbound to KF45 on 2026-07-09. SkyMeter detected a long landing rollout at North Palm Beach County General Aviation Airport (KF45) on runway 08L at 19:54 UTC. Trace data at the event: 19 ft AGL, 17 kt GS, 0 fpm vertical. Approach stability score: 50/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 10 kt wind, 6 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/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7880 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7881 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/2665 2026-07-07 12:30Z – 2026-07-11 06:00Z SFC–2,500 ft

    MAYPORT, FL, Tuesday, July 7, 2026 through Saturday, July 11, 2026 Local

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

    Palm Beach Gardens, FL

    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 08L
  • 19 ft AGL at event
  • 17 kt ground speed
  • 0 fpm vertical
  • Approach stability 50/100
  • 10 kt wind
  • 6 kt crosswind component
  • 16,093 m visibility
  • METAR KF45 180235Z AUTO 21003KT 10SM OVC023 26/25 A3007 RMK AO2 LTG DSNT SE

Flight context

  • JRE844
  • Fe5344
  • C56X
  • 2026-07-09 19:54 UTC
  • KF45 runway 08L

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