MAA3114 was inbound to KHHR on 2026-06-16. SkyMeter detected a long landing rollout at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 06:22 UTC. Trace data at the event: 78 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 61/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 5 kt wind, 2 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/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft
Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft
Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z
MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4182 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4183 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4198 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4201 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4202 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4203 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/5756 2026-06-05 14:00Z – 2026-06-19 04:00Z SFC–11,500 ft
3NM E NOGALES, AZ, Friday, June 5, 2026 through Friday, June 19, 2026 UTC
View FAA NOTAM → - SECURITY6/7265 2026-06-12 21:07Z – 2026-07-16 06:29Z SFC–400 ft
Manhattan Beach, CA
View FAA NOTAM → - HAZARDS6/8083 2026-06-13 17:14Z – 2026-06-27 05:00Z SFC–11,000 ft
10NM E TUCSON, AZ, Saturday, June 13, 2026 through Saturday, June 27, 2026 UTC
View FAA NOTAM → - SECURITY6/7934 2026-06-15 22:00Z – 2026-06-16 07:01Z SFC–3,000 ft
Los Angeles, CA, Monday, June 15, 2026 through Tuesday, June 16, 2026 Local
View FAA NOTAM → - HAZARDS6/8547 2026-06-16 02:03Z – 2026-06-30 03:00Z SFC–6,000 ft
3.1NM S CALIMESA, CA, Tuesday, June 16, 2026 through Tuesday, June 30, 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
- 78 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 61/100
- 5 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KHHR 182153Z 26010G18KT 10SM CLR 24/15 A3000 RMK AO2 SLP159 T02390150 $
Flight context
- MAA3114
- A332
- 2026-06-16 06:22 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