BLZR278 was operating from KNQI to KMAF on 2026-07-20. SkyMeter detected a low approach-stability score at Midland International Airport (KMAF) on runway 22 at 13:55 UTC. Trace data at the event: 3948 ft AGL, 442 kt GS. Approach stability score: 19/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 10 kt wind, 6 kt crosswind component, 11,265 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/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/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/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 → - HAZARDS6/6155 2026-07-16 16:00Z – 2026-07-23 23:00Z SFC–1,500 ft
0NM W INGRAM, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6156 2026-07-16 16:09Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM SE KERRVILLE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6157 2026-07-16 16:15Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM NW BOERNE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6158 2026-07-16 16:23Z – 2026-07-23 23:00Z SFC–1,500 ft
3NM SW UVALDE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6217 2026-07-16 18:17Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM W INGRAM, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6218 2026-07-16 18:17Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM SE KERRVILLE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6528 2026-07-17 19:40Z – 2026-07-24 05:00Z SFC–1,500 ft
CRYSTAL CITY, TX, Friday, July 17, 2026 through Friday, July 24, 2026 UTC
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 22
- 3948 ft AGL at event
- 442 kt ground speed
- 0 fpm vertical
- Approach stability 19/100
- 10 kt wind
- 6 kt crosswind component
- 11,265 m visibility
- KMAF 161753Z 15018G24KT 7SM CLR 32/16 A3023 RMK AO2 SLP187 T03170156 10317 20228 58001
Flight context
- BLZR278
- HAWK
- KNQI → KMAF
- 2026-07-20 13:55 UTC
- KMAF runway 22
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