Unstable approach — AXEL90

AXEL90 (Lasai Aviation II) was inbound to KLAS on 2026-08-21. SkyMeter detected a low approach-stability score at McCarran International Airport (KLAS) on runway 19R at 17:31 UTC. Trace data at the event: 3276 ft AGL, 126 kt GS. METAR at the time reported 8 kt wind, 8 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.

• SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• HAZARDS6/2768 2026-08-07 14:00Z – 2026-08-22 04:00Z SFC–12,500 ft

  8NM SW RIFLE, CO, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2913 2026-08-08 14:00Z – 2026-08-22 04:00Z SFC–12,500 ft

  10NM SW RIFLE, CO, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2914 2026-08-08 14:00Z – 2026-08-22 04:00Z SFC–6,500 ft

  8NM W RIFLE, CO, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3080 2026-08-08 22:15Z – 2026-08-22 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3097 2026-08-09 13:00Z – 2026-08-23 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3679 2026-08-11 12:00Z – 2026-08-25 08:00Z SFC–16,500 ft

  1NM NE OURAY, CO, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3659 2026-08-11 13:00Z – 2026-08-24 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Tuesday, August 11, 2026 through Monday, August 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3712 2026-08-11 14:00Z – 2026-08-25 04:00Z SFC–8,000 ft

  18NM SW PRESCOTT, AZ, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4085 2026-08-12 04:00Z – 2026-08-25 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Wednesday, August 12, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5474 2026-08-17 07:41Z – 2026-08-22 00:15Z SFC–5,000 ft

  IMPERIAL, CA, Monday, August 17, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5463 2026-08-17 13:00Z – 2026-08-30 04:00Z SFC–13,000 ft

  20NM NE SALT LAKE CITY, UT, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5937 2026-08-18 13:00Z – 2026-08-31 03:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6712 2026-08-20 00:53Z – 2026-08-22 04:00Z SFC–14,500 ft

  8NM N ASPEN, CO, Thursday, August 20, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6728 2026-08-20 13:00Z – 2026-08-27 03:00Z SFC–14,500 ft

  8NM N ASPEN, CO, Thursday, August 20, 2026 through Thursday, August 27, 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.

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