Long landing rollout — THT8

KHHR · 25

2026-05-28 17:22 UTC· NTAA → KHHR· B789

▶ Replay 📊 Analyse

THT8 was operating from NTAA to KHHR on 2026-05-28. SkyMeter detected a long landing rollout at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 17:22 UTC. Trace data at the event: 101 ft AGL, 7 kt GS, 0 fpm vertical. METAR at the time reported 3 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)
  • HAZARDS6/2573 2026-05-25 15:00Z – 2026-06-06 03:00Z SFC–8,000 ft

    32NM SW SANTA BARBARA, CA, Monday, May 25, 2026 through Saturday, June 6, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2830 2026-05-25 15:45Z – 2026-06-11 16:00Z SFC–5,000 ft

    GARDEN GROVE, CA, Monday, May 25, 2026 through Thursday, June 11, 2026 UTC

    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
  • 3 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KHHR 200953Z AUTO 00000KT 10SM OVC019 21/17 A2993 RMK AO2 SLP134 T02060167 $

Flight context

  • THT8
  • B789
  • NTAA → KHHR
  • 2026-05-28 17:22 UTC
  • KHHR runway 25

All events on this flight

Long landing rollout 17:22:06 UTC · KHHR runway 25 · 101 ft AGL · 7 kt GS
Long landing rollout 17:22:06 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