Long landing rollout — LXJ607
KHHR · 252026-07-18 01:34 UTC· CLINICAL VENTURES GROUP II LLC, SPYGLASS AIR LLC, CALI CLOUD LLC· E550
LXJ607 (Clinical Ventures Group II) was inbound to KHHR on 2026-07-18. SkyMeter detected a long landing rollout at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 01:34 UTC. Trace data at the event: 72 ft AGL, 0 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 1 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/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/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/7842 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Montecito, CA
View FAA NOTAM → - SECURITY6/7841 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft
Goleta, CA
View FAA NOTAM → - SECURITY6/7850 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft
Los Angeles, CA
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
- 0 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KHHR 172253Z 26012KT 10SM CLR 25/14 A3003 RMK AO2 SLP168 T02500139
Flight context
- LXJ607
- Clinical Ventures Group II
- E550
- 2026-07-18 01:34 UTC
- KHHR runway 25
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