Unstable approach — N67TW

I72 · 36

2026-07-07 00:18 UTC· KFTW → I72· TW EQUIPMENT LEASING INC· C680

N67TW (TW Equipment Leasing) was operating from KFTW to I72 on 2026-07-07. SkyMeter detected a low approach-stability score at Westfield Airport (I72) on runway 36 at 00:18 UTC. Trace data at the event: 2038 ft AGL, 146 kt GS. METAR at the time reported 6 kt wind, 2 kt crosswind component. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z

    STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

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

    Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

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

    Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kansas City, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    PRAIRIE VILLAGE, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    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/7972 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Nashville, TN

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

    Riverside, MO

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

    Nashville, TN

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

    Kansas City, MO

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

    Frisco, TX

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

    Lawrence, KS

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

    Lawrence, KS

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

    Kansas City, MO, Monday, July 6, 2026 through Monday, July 6, 2026 Local

    View FAA NOTAM →
  • SECURITY6/2370 2026-07-06 16:00Z – 2026-07-07 01:00Z SFC–3,000 ft

    DALLAS, TX, Monday, July 6, 2026 through Monday, July 6, 2026 Local

    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 36
  • 2038 ft AGL at event
  • 146 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 2 kt crosswind component

Flight context

  • N67TW
  • TW Equipment Leasing
  • C680
  • KFTW → I72
  • 2026-07-07 00:18 UTC
  • I72 runway 36

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· I72