Long landing rollout — ENY3429

ENY3429 (American Airlines) was operating from KDFW to K6S8 on 2026-07-22. SkyMeter detected a long landing rollout at Laurel Municipal Airport (K6S8) on runway 14 at 18:52 UTC. Trace data at the event: 3553 ft AGL, 11 kt GS. METAR at the time reported 4 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.

• HAZARDS6/3801 2026-07-08 01:49Z – 2026-07-23 04:00Z SFC–15,000 ft

  1NM W PUEBLO, CO, Wednesday, July 8, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4199 2026-07-09 02:00Z – 2026-07-23 05:00Z SFC–13,000 ft

  18NM N CORTEZ, CO, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4561 2026-07-10 04:00Z – 2026-07-24 04:00Z SFC–16,500 ft

  19NM NE OURAY, CO, Friday, July 10, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4562 2026-07-10 12:00Z – 2026-07-24 05:00Z SFC–17,000 ft

  3NM W LEADVILLE, CO, Friday, July 10, 2026 through Friday, July 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5152 2026-07-13 04:00Z – 2026-07-27 04:00Z SFC–15,000 ft

  14NM S STEAMBOAT SPRINGS, CO, Monday, July 13, 2026 through Monday, July 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5450 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft

  19NM NE OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5451 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft

  1NM N OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5875 2026-07-15 04:00Z – 2026-07-30 04:00Z SFC–12,000 ft

  19NM SW MEEKER, CO, Wednesday, July 15, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5876 2026-07-15 04:00Z – 2026-07-30 04:00Z SFC–13,500 ft

  7NM SE STEAMBOAT SPRINGS, CO, Wednesday, July 15, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• SECURITY6/5841 2026-07-16 13:00Z – 2026-07-27 05:59Z SFC–400 ft

  Cheyenne, WY, Thursday, July 16, 2026 through Sunday, July 26, 2026 Local

  View FAA NOTAM →
• HAZARDS6/6360 2026-07-17 04:00Z – 2026-07-30 04:00Z SFC–15,000 ft

  9NM SW PUEBLO, CO, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6395 2026-07-17 12:00Z – 2026-07-30 04:00Z SFC–13,000 ft

  14NM N CORTEZ, CO, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6876 2026-07-20 13:00Z – 2026-08-03 04:00Z SFC–16,000 ft

  7NM SW DEL NORTE, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6894 2026-07-20 14:02Z – 2026-08-03 04:00Z SFC–12,500 ft

  12NM NW CRAIG, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6900 2026-07-20 14:42Z – 2026-08-03 04:00Z SFC–13,500 ft

  11NM SW KREMMLING, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7220 2026-07-21 04:00Z – 2026-08-04 04:00Z SFC–12,000 ft

  19NM SW MEEKER, CO, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7221 2026-07-21 04:00Z – 2026-08-04 04:00Z SFC–13,500 ft

  7NM SE STEAMBOAT SPRINGS, CO, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7702 2026-07-22 13:08Z – 2026-08-05 04:00Z SFC–11,500 ft

  11NM SW CRAIG, CO, Wednesday, July 22, 2026 through Wednesday, August 5, 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.

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