Long landing rollout — ASA485

KHHR · 25

2026-06-03 15:13 UTC· KSEA KHHR· WILMINGTON TRUST CO TRUSTEE· B738

ASA485 (Wilmington Trust) was operating from KSEA to KHHR on 2026-06-03. SkyMeter detected a long landing rollout at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 15:13 UTC. Trace data at the event: 111 ft AGL, 14 kt GS, 0 fpm vertical. Approach stability score: 60/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. 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)
  • SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

    BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

    SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

    View FAA NOTAM →
  • 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 →
  • SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

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

    Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    GOLETA, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Santa Clara, CA, Monday, June 1, 2026 through Monday, July 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 25
  • 111 ft AGL at event
  • 14 kt ground speed
  • 0 fpm vertical
  • Approach stability 60/100
  • 3 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KHHR 200550Z AUTO 30004KT 10SM OVC015 21/17 A2992 RMK T02100170 MADISHF

Flight context

  • ASA485
  • Wilmington Trust
  • B738
  • KSEA → KHHR
  • 2026-06-03 15:13 UTC
  • KHHR runway 25

All events on this flight

Long landing rollout 15:13:25 UTC · KHHR runway 25 · 111 ft AGL · 14 kt GS
Long landing rollout 15:13:25 UTC · KHHR runway 25 · 111 ft AGL · 14 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