Long landing rollout — AAL2671
KHRT · 182026-06-27 17:02 UTC· KCLT → KHRT· UMB BANK NA TRUSTEE· A320
AAL2671 (UMB Bank NA) was operating from KCLT to KHRT on 2026-06-27. SkyMeter detected a long landing rollout at Hurlburt Field (KHRT) on runway 18 at 17:02 UTC. Trace data at the event: 88 ft AGL, 23 kt GS, 0 fpm vertical. METAR at the time reported 8 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)- SECURITY6/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3980 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3990 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3998 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/8212 2026-06-17 04:01Z – 2026-07-17 03:59Z SFC–400 ft
Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/0677 2026-06-27 15:30Z – 2026-06-28 06:59Z SFC–400 ft
Clemson, SC, Saturday, June 27, 2026 through Sunday, June 28, 2026 UTC
View FAA NOTAM → - SECURITY6/0294 2026-06-27 17:00Z – 2026-06-28 05:00Z SFC–3,000 ft
Atlanta, GA, Saturday, June 27, 2026 through Sunday, June 28, 2026 Local
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 18
- 88 ft AGL at event
- 23 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KHRT 181455Z 08008KT 10SM CLR 29/20 A3014 RMK AO2A SLP204 T02890195 50007 $
Flight context
- AAL2671
- UMB Bank NA
- A320
- KCLT → KHRT
- 2026-06-27 17:02 UTC
- KHRT runway 18
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