Long landing rollout — JRE830

JRE830 (Ross Advisors) was inbound to K4T2 on 2026-07-19. SkyMeter detected a long landing rollout at Kenneth Copeland Airport (K4T2) on runway 35 at 17:09 UTC. Trace data at the event: 705 ft AGL, 10 kt GS. METAR at the time reported 5 kt wind, 2 kt crosswind component. 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/3705 2026-05-29 05:00Z – 2026-07-20 08:00Z SFC–400 ft

  DALLAS, TX, Friday, May 29, 2026 through Monday, July 20, 2026 Local

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

  ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  IRVING, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/6840 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft

  Mansfield, TX

  View FAA NOTAM →
• SECURITY6/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft

  Fort Worth, TX

  View FAA NOTAM →
• SECURITY6/4573 2026-07-14 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft

  Dallas, TX, Tuesday, July 14, 2026 through Sunday, July 19, 2026 Local

  View FAA NOTAM →
• SECURITY6/6841 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft

  Fort Worth, TX

  View FAA NOTAM →
• SECURITY6/6849 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft

  Irving, TX

  View FAA NOTAM →
• SECURITY6/6839 2026-07-17 23:07Z – 2026-07-21 04:59Z SFC–400 ft

  Arlington, TX

  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