Unstable approach — N458MC

KTPL · 15

2026-06-30 00:16 UTC· KSTL → KTPL· MCLANE COMPANY INC· C68A

N458MC (McLane) was operating from KSTL to KTPL on 2026-06-30. SkyMeter detected a low approach-stability score at Draughon Miller Central Texas Regional Airport (KTPL) on runway 15 at 00:16 UTC. Trace data at the event: 1774 ft AGL, 166 kt GS. METAR at the time reported 15 kt wind, 1 kt crosswind component, 16,093 m visibility. 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/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/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/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/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/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 →

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
  • 1774 ft AGL at event
  • 166 kt ground speed
  • 0 fpm vertical
  • 15 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KTPL 080951Z AUTO 32005KT 10SM CLR A2998 RMK AO2 SLPNO FZRANO $

Flight context

  • N458MC
  • McLane
  • C68A
  • KSTL → KTPL
  • 2026-06-30 00:16 UTC
  • KTPL runway 15

All events on this flight

Unstable approach 00:16:22 UTC · KTPL runway 15 · 1,774 ft AGL · 166 kt GS
Unstable approach 00:16:22 UTC · KTPL runway 16 · 1,774 ft AGL · 166 kt GS

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