Long landing rollout — N440JT

KCFD · 15

2026-07-18 13:23 UTC· KTDW KCFD· J T AERO MANAGEMENT LLC· BE20

N440JT (J T Aero Management) was operating from KTDW to KCFD on 2026-07-18. SkyMeter detected a long landing rollout at Coulter Field (KCFD) on runway 15 at 13:23 UTC. Trace data at the event: 341 ft AGL, 2 kt GS, 0 fpm vertical. METAR at the time reported 7 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/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/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/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/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/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/6784 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft

    Denton, TX

    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.

Pilot review data

  • Runway 15
  • 341 ft AGL at event
  • 2 kt ground speed
  • 0 fpm vertical
  • 7 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • METAR KCFD 172235Z AUTO 09007KT 10SM CLR 35/19 A3013 RMK AO2 LTG DSNT S T03450187

Flight context

  • N440JT
  • J T Aero Management
  • BE20
  • KTDW → KCFD
  • 2026-07-18 13:23 UTC
  • KCFD runway 15

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

SkyMeter · trace data observed via ADS-B· KCFD