Long landing rollout — AAL2066

AAL2066 (American Airlines) was operating from KORD to KSFB on 2026-06-20. SkyMeter detected a long landing rollout at Orlando Sanford International Airport (KSFB) on runway 09R at 19:09 UTC. Trace data at the event: 95 ft AGL, 25 kt GS, 0 fpm vertical. METAR at the time reported 5 kt wind, 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.

• 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/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4118 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  CARMEL, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4128 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4119 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4121 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Nashville, TN, 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 →
• SECURITY6/8583 2026-06-19 04:01Z – 2026-06-21 03:59Z SFC–1,000 ft

  Atlanta, GA, Friday, June 19, 2026 through Saturday, June 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/8964 2026-06-19 21:00Z – 2026-06-21 22:00Z SFC–400 ft

  Cincinati, OH, Friday, June 19, 2026 through Sunday, June 21, 2026 Local

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/8284 2026-06-19 21:30Z – 2026-06-21 04:30Z SFC–400 ft

  Chicago, IL, Friday, June 19, 2026 through Sunday, June 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/9261 2026-06-20 13:30Z – 2026-06-20 19:00Z SFC–400 ft

  COLUMBUS, OH, Saturday, June 20, 2026 Local

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8270 2026-06-20 19:00Z – 2026-06-21 21:00Z SFC–16,000 ft

  Columbus, OH, Saturday, June 20, 2026 through Sunday, June 21, 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.

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