Long landing rollout — EJA231

KLNA · 10

2026-04-12 16:55 UTC· KTEB → KLNA· NETJETS SALES INC, 144 LLC, 7-ELEVEN INC, CALLAHAN BRIAN, CFHSEA· CL60

▶ Replay 📊 Analyse

EJA231 (Netjets Sales) was operating from KTEB to KLNA on 2026-04-12. SkyMeter detected a long landing rollout at Palm Beach County Park Airport (KLNA) on runway 10 at 16:55 UTC. Trace data at the event: 13 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 15 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)
  • SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 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 10
  • 13 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • 15 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • METAR KLNA 230315Z AUTO 00000KT 10SM SCT045 BKN070 OVC090 26/24 A2997 RMK AO2 T02600240

Flight context

  • EJA231
  • Netjets Sales
  • CL60
  • KTEB → KLNA
  • 2026-04-12 16:55 UTC
  • KLNA runway 10

All events on this flight

Long landing rollout 16:55:04 UTC · KLNA runway 10 · 13 ft AGL · 4 kt GS
Long landing rollout 16:55:04 UTC · KLNA runway 09 · 13 ft AGL · 4 kt GS
Long landing rollout 16:55:04 UTC · KLNA runway 10 · 13 ft AGL · 4 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· KLNA