EmergencyDescent — SWA2567
2026-09-04 21:54 UTC· KAUS → KABQ· SOUTHWEST AIRLINES CO· B737
SWA2567 (Southwest Airlines) was operating from KAUS to KABQ on 2026-09-04. SkyMeter detected a emergencydescent at 21:54 UTC. Trace data at the event: 33622 ft AGL, 420 kt GS. Approach stability score: 63/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 10 kt wind, 9 kt crosswind component. 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 → - HAZARDS6/7128 2026-08-23 13:00Z – 2026-09-06 03:00Z SFC–14,500 ft
26NM NE RUIDOSO, NM, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/7422 2026-08-24 14:30Z – 2026-09-08 05:00Z SFC–12,500 ft
26NM NE RUIDOSO, NM, Monday, August 24, 2026 through Tuesday, September 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8092 2026-08-26 00:25Z – 2026-09-09 23:45Z SFC–6,200 ft
1NM NE EVANT, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8102 2026-08-26 02:25Z – 2026-09-09 02:00Z SFC–5,500 ft
1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8069 2026-08-26 14:00Z – 2026-09-09 04:00Z SFC–14,000 ft
26NM SE ALBUQUERQUE, NM, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8445 2026-08-26 20:55Z – 2026-09-09 02:00Z SFC–5,500 ft
1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8453 2026-08-26 21:02Z – 2026-09-08 00:45Z SFC–6,200 ft
1NM NE EVANT, TX, Wednesday, August 26, 2026 through Tuesday, September 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8829 2026-08-28 15:45Z – 2026-09-11 02:00Z SFC–5,500 ft
4NM NW MINERAL WELLS, TX, Friday, August 28, 2026 through Friday, September 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/8888 2026-08-28 23:05Z – 2026-09-12 03:00Z SFC–14,000 ft
28NM SE ALBUQUERQUE, NM, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/9129 2026-08-29 15:15Z – 2026-09-12 02:00Z SFC–5,500 ft
4NM NW MINERAL WELLS, TX, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/9211 2026-08-30 11:30Z – 2026-09-13 02:00Z SFC–5,500 ft
4NM NW MINERAL WELLS, TX, Sunday, August 30, 2026 through Sunday, September 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/9244 2026-08-30 20:00Z – 2026-09-06 02:00Z SFC–6,000 ft
12NM NW ROCKSPRINGS, TX, Sunday, August 30, 2026 through Sunday, September 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/9262 2026-08-31 13:00Z – 2026-09-15 02:00Z SFC–6,000 ft
12NM NW ROCKSPRINGS, TX, Monday, August 31, 2026 through Tuesday, September 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/9626 2026-09-01 02:00Z – 2026-09-15 02:00Z SFC–5,500 ft
4NM NW MINERAL WELLS, TX, Tuesday, September 1, 2026 through Tuesday, September 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/0920 2026-09-04 14:00Z – 2026-09-18 02:00Z SFC–5,500 ft
4NM NW MINERAL WELLS, TX, Friday, September 4, 2026 through Friday, September 18, 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
- 33622 ft AGL at event
- 420 kt ground speed
- 0 fpm vertical
- Approach stability 63/100
- 10 kt wind
- 9 kt crosswind component
Flight context
- SWA2567
- Southwest Airlines
- B737
- KAUS → KABQ
- 2026-09-04 21:54 UTC
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