COOL11 was operating from KBAD to KIAB on 2026-07-18. SkyMeter detected a low approach-stability score at Mc Connell Air Force Base (KIAB) on runway 19L at 00:14 UTC. Trace data at the event: 2488 ft AGL, 214 kt GS. METAR at the time reported 11 kt wind, 2 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/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/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z
TULSA, 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/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/6840 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Mansfield, 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/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 19L
- 2488 ft AGL at event
- 214 kt ground speed
- 0 fpm vertical
- 11 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KIAB 160655Z AUTO 06006KT 10SM BKN170 22/21 A3008 RMK AO2 SLP173 T02230214 $
Flight context
- COOL11
- T38
- KBAD → KIAB
- 2026-07-18 00:14 UTC
- KIAB runway 19L
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