Unstable approach — EJA433
KTKI · 362026-07-14 00:21 UTC· KLRD → KTKI· NETJETS SALES INC, ASSATEAGUE RESOURCES LLC, CAPITAL HOLDINGS 24· E55P
EJA433 (Netjets Sales) was operating from KLRD to KTKI on 2026-07-14. SkyMeter detected a low approach-stability score at Collin County Regional At Mc Kinney Airport (KTKI) on runway 36 at 00:21 UTC. Trace data at the event: 1673 ft AGL, 133 kt GS. METAR at the time reported 6 kt wind, 6 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/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/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/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/4097 2026-06-01 05:00Z – 2026-07-21 04:59Z
SAN ANTONIO, 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/6820 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
San Antonio, TX
View FAA NOTAM → - SECURITY6/6834 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
San Antonio, 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 36
- 1673 ft AGL at event
- 133 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- METAR KTKI 312353Z 15008KT 10SM CLR 36/16 A2993 RMK AO2 SLP126 T03610161 10378 20356 56011
Flight context
- EJA433
- Netjets Sales
- E55P
- KLRD → KTKI
- 2026-07-14 00:21 UTC
- KTKI 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