Long landing rollout — FFT1755

KHHR · 25

2026-05-08 00:36 UTC· WILMINGTON TRUST CO TRUSTEE· A321

▶ Replay 📊 Analyse

FFT1755 (Wilmington Trust) was inbound to KHHR on 2026-05-08. SkyMeter detected a long landing rollout at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 00:36 UTC. Trace data at the event: 101 ft AGL, 7 kt GS, 0 fpm vertical. METAR at the time reported 8 kt wind, 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/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft

    Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 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 25
  • 101 ft AGL at event
  • 7 kt ground speed
  • 0 fpm vertical
  • 8 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KHHR 210653Z AUTO 23003KT 10SM BKN025 20/16 A2994 RMK AO2 SLP136 T02000161 $

Flight context

  • FFT1755
  • Wilmington Trust
  • A321
  • 2026-05-08 00:36 UTC
  • KHHR runway 25

All events on this flight

Long landing rollout 00:36:07 UTC · KHHR runway 25 · 101 ft AGL · 7 kt GS
Long landing rollout 00:36:07 UTC · KHHR runway 25 · 101 ft AGL · 7 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· KHHR