Long landing rollout — N82EM

KTTS · 15

2026-08-21 16:08 UTC· KDCA → KTTS· JDI HOLDINGS LLC· GLEX

▶ Replay 📊 Analyse

N82EM (JDI Holdings) was operating from KDCA to KTTS on 2026-08-21. SkyMeter detected a long landing rollout at NASA Shuttle Landing Facility Airport (KTTS) on runway 15 at 16:08 UTC. Trace data at the event: 19 ft AGL, 7 kt GS, 0 fpm vertical. METAR at the time reported 5 kt wind, 5 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/5452 2026-08-17 12:30Z – 2026-08-22 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, August 17, 2026 through Saturday, August 22, 2026 Local

    View FAA NOTAM →
  • SPACE OPERATIONS6/5396 2026-08-21 14:57Z – 2026-08-21 19:39Z SFC–180 ft

    Cape Canaveral, FL, Friday, August 21, 2026 Local

    View FAA NOTAM →
  • SPACE OPERATIONS6/5397 2026-08-21 14:57Z – 2026-08-21 19:39Z SFC–180 ft

    Cape Canaveral, FL, Friday, August 21, 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 15
  • 19 ft AGL at event
  • 7 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • KTTS 162055Z AUTO 04012KT 10SM FEW029 OVC045 30/24 A3011 RMK AO2 DZB1955E03 SLP200 P0000 60000 T02990235 57014 $

Flight context

  • N82EM
  • JDI Holdings
  • GLEX
  • KDCA → KTTS
  • 2026-08-21 16:08 UTC
  • KTTS runway 15

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