Long landing rollout — FDX1423
KHHR · 252026-06-16 16:59 UTC· KSEA → KHHR· FEDERAL EXPRESS CORP· B77L
FDX1423 (Federal Express) was operating from KSEA to KHHR on 2026-06-16. SkyMeter detected a long landing rollout at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 16:59 UTC. Trace data at the event: 137 ft AGL, 7 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 4 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/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 → - 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 → - HAZARDS6/8214 2026-06-14 17:34Z – 2026-06-17 07:00Z SFC–400 ft
3.8NM NW TRACY, CA, Sunday, June 14, 2026 through Wednesday, June 17, 2026 UTC
View FAA NOTAM → - HAZARDS6/8221 2026-06-14 20:07Z – 2026-06-28 03:00Z SFC–6,000 ft
22NM SE RICHLAND, WA, Sunday, June 14, 2026 through Sunday, June 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/8252 2026-06-15 04:35Z – 2026-06-26 04:00Z SFC–5,500 ft
12NM NE PASCO, WA, Monday, June 15, 2026 through Friday, June 26, 2026 UTC
View FAA NOTAM → - HAZARDS6/8253 2026-06-15 15:00Z – 2026-06-30 05:00Z SFC–6,000 ft
3NM W BENTON CITY, WA, Monday, June 15, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/8503 2026-06-15 21:15Z – 2026-06-20 04:00Z SFC–6,500 ft
20NM S YAKIMA, WA, Monday, June 15, 2026 through Saturday, June 20, 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
- 137 ft AGL at event
- 7 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KHHR 182153Z 26010G18KT 10SM CLR 24/15 A3000 RMK AO2 SLP159 T02390150 $
Flight context
- FDX1423
- Federal Express
- B77L
- KSEA → KHHR
- 2026-06-16 16:59 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