Long landing rollout — AAL2290
KHHR · 252026-05-18 04:29 UTC· KMIA → KHHR· BANK OF UTAH TRUSTEE· A21N
AAL2290 (Bank of Utah) was operating from KMIA to KHHR on 2026-05-18. SkyMeter detected a long landing rollout at Jack Northrop Field Hawthorne Municipal Airport (KHHR) on runway 25 at 04:29 UTC. Trace data at the event: 137 ft AGL, 5 kt GS, 0 fpm vertical. METAR at the time reported 3 kt wind, 2 kt crosswind component, 12,875 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/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 Local
View FAA NOTAM → - 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 → - SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft
OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local
View FAA NOTAM → - SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - 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/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft
SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - HAZARDS6/9663 2026-05-12 13:00Z – 2026-05-26 03:00Z SFC–10,500 ft
38NM NW SILVER CITY, NM, Tuesday, May 12, 2026 through Tuesday, May 26, 2026 UTC
View FAA NOTAM → - HAZARDS6/9795 2026-05-12 17:22Z – 2026-05-25 23:59Z SFC–10,000 ft
BROWNSVILLE, TX, Tuesday, May 12, 2026 through Monday, May 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/9916 2026-05-13 12:00Z – 2026-05-22 01:30Z SFC–2,000 ft
27NM E OF WAYCROSS, GA, Wednesday, May 13, 2026 through Friday, May 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/9917 2026-05-13 12:00Z – 2026-05-22 01:30Z SFC–2,000 ft
18NM S OF HOMERVILLE, GA, Wednesday, May 13, 2026 through Friday, May 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/0618 2026-05-15 13:00Z – 2026-05-28 04:00Z SFC–13,500 ft
22NM NE RUIDOSO, NM, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/1015 2026-05-18 00:28Z – 2026-06-01 04:00Z SFC–15,500 ft
22NM NE RUIDOSO, NM, Monday, May 18, 2026 through Monday, June 1, 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
- 5 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 2 kt crosswind component
- 12,875 m visibility
- KHHR 201253Z AUTO 00000KT 8SM OVC020 21/16 A2993 RMK AO2 SLP134 T02110161 $
Flight context
- AAL2290
- Bank of Utah
- A21N
- KMIA → KHHR
- 2026-05-18 04:29 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