Unstable approach — SWA930
KDEN · 252026-06-30 18:38 UTC· KDAL → KDEN· SOUTHWEST AIRLINES CO· B38M
SWA930 (Southwest Airlines) was operating from KDAL to KDEN on 2026-06-30. SkyMeter detected a low approach-stability score at Denver International Airport (KDEN) on runway 25 at 18:38 UTC. Trace data at the event: 6496 ft AGL, 164 kt GS. Approach stability score: 33/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 12 kt wind, 10 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/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z
OKLAHOMA CITY, 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/3997 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NORMAN, 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/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/4022 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
OKLAHOMA CITY, OK, 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/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Fort Worth, TX
View FAA NOTAM → - HAZARDS6/1775 2026-06-30 06:00Z – 2026-07-14 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Tuesday, June 30, 2026 through Tuesday, July 14, 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 25
- 6496 ft AGL at event
- 164 kt ground speed
- 0 fpm vertical
- Approach stability 33/100
- 12 kt wind
- 10 kt crosswind component
- 16,093 m visibility
- KDEN 080453Z 22006KT 10SM FEW150 14/03 A3017 RMK AO2 SLP159 T01390033
Flight context
- SWA930
- Southwest Airlines
- B38M
- KDAL → KDEN
- 2026-06-30 18:38 UTC
- KDEN runway 25
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