Long landing rollout — ENG21

ENG21 (SJ Transportation Holdings) was operating from KSJT to KHOU on 2026-07-09. SkyMeter detected a long landing rollout at US-12019 (US-12019) on runway 16 at 20:01 UTC. Trace data at the event: 1292 ft AGL, 0 kt GS. Approach stability score: 78/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 11 kt wind, 10 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/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 →
• SECURITY6/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z

  OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

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

  NORMAN, OK, Monday, June 1, 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/4008 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

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

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

  FRISCO, 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/4022 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

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

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

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

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

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

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

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

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

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

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

  Houston, TX, Tuesday, June 9, 2026 through Sunday, July 19, 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/6843 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Frisco, TX

  View FAA NOTAM →
• SECURITY6/6844 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Frisco, TX

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

  Houston, TX

  View FAA NOTAM →
• SECURITY6/6783 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Houston, TX

  View FAA NOTAM →
• SECURITY6/6838 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

  Houston, 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