Unstable approach — AAL513

KLOM · 06

2026-05-22 05:00 UTC· KLAX → KLOM· AMERICAN AIRLINES INC· A21N

▶ Replay 📊 Analyse

AAL513 (American Airlines) was operating from KLAX to KLOM on 2026-05-22. SkyMeter detected a low approach-stability score at Wings Field (KLOM) on runway 06 at 05:00 UTC. Trace data at the event: 1401 ft AGL, 130 kt GS. Approach stability score: 43/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 3 kt wind, 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)
  • SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft

    Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/0618 2026-05-15 13:00Z – 2026-05-28 04:00Z SFC–13,500 ft

    22NM NE RUIDOSO, NM, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0607 2026-05-15 14:00Z – 2026-05-28 04:00Z SFC–12,000 ft

    30NM SW NEPHI, UT, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft

    Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft

    19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1015 2026-05-18 00:28Z – 2026-06-01 04:00Z SFC–15,500 ft

    22NM NE RUIDOSO, NM, Monday, May 18, 2026 through Monday, June 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft

    5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1626 2026-05-19 22:38Z – 2026-06-02 04:00Z SFC–15,500 ft

    22NM NE RUIDOSO, NM, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2365 2026-05-22 00:28Z – 2026-05-22 06:00Z SFC–11,000 ft

    12NM S PRESCOTT, AZ, Friday, May 22, 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 06
  • 1401 ft AGL at event
  • 130 kt ground speed
  • 0 fpm vertical
  • Approach stability 43/100
  • 3 kt wind
  • 0 kt crosswind component
  • 11,265 m visibility
  • METAR KLOM 010315Z AUTO 00000KT 7SM SCT013 SCT036 OVC080 20/20 A3009 RMK AO2 T02040204

Flight context

  • AAL513
  • American Airlines
  • A21N
  • KLAX → KLOM
  • 2026-05-22 05:00 UTC
  • KLOM runway 06

All events on this flight

Unstable approach 05:00:18 UTC · KLOM runway 06 · 1,401 ft AGL · 130 kt GS
Long landing rollout 05:04:02 UTC · KLOM runway 06 · 9 ft AGL · 18 kt GS
Unstable approach 05:00:18 UTC · KLOM runway 06 · 1,401 ft AGL · 130 kt GS
Long landing rollout 05:04:02 UTC · KLOM runway 06 · 9 ft AGL · 18 kt GS

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

SkyMeter · trace data observed via ADS-B· KLOM