Long landing rollout — EJA402
KHHR · 252026-05-26 00:41 UTC· KRNO → KHHR· NETJETS SALES INC, DEXTER AVIATION LLC, HAPPY BEANER LLC· E55P
EJA402 (Netjets Sales) was operating from KRNO to KHHR on 2026-05-26. SkyMeter detected a long landing rollout at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 00:41 UTC. Trace data at the event: 72 ft AGL, 2 kt GS, 0 fpm vertical. METAR at the time reported 14 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/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 → - HAZARDS6/1359 2026-05-18 20:54Z – 2026-05-31 16:00Z SFC–6,000 ft
3NM S SIMI VALLEY, CA, Monday, May 18, 2026 through Sunday, May 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/1376 2026-05-19 02:58Z – 2026-05-31 15:00Z SFC–6,000 ft
3NM S SIMI VALLEY, CA, Tuesday, May 19, 2026 through Sunday, May 31, 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
- 72 ft AGL at event
- 2 kt ground speed
- 0 fpm vertical
- 14 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KHHR 201053Z AUTO 12003KT 10SM OVC017 21/17 A2991 RMK AO2 SLP128 T02110167 $
Flight context
- EJA402
- Netjets Sales
- E55P
- KRNO → KHHR
- 2026-05-26 00:41 UTC
- KHHR runway 25
All events on this flight
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