Unstable approach — AAY33

AAY33 (Sunrise Asset Management) was operating from KLAS to KBZN on 2026-08-06. SkyMeter detected a low approach-stability score at Gallatin Field (KBZN) on runway 30 at 21:44 UTC. Trace data at the event: 5505 ft AGL, 150 kt GS. Approach stability score: 57/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 8 kt wind, 4 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.

• HAZARDS6/0722 2026-08-01 13:00Z – 2026-08-14 04:00Z SFC–14,000 ft

  9NM S ELY, NV, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0718 2026-08-01 14:00Z – 2026-08-15 03:00Z SFC–12,500 ft

  36NM SW BUTTE, MT, Saturday, August 1, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0725 2026-08-01 14:00Z – 2026-08-14 04:00Z SFC–9,500 ft

  17NM NE IDAHO FALLS, ID, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0881 2026-08-02 13:00Z – 2026-08-16 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Sunday, August 2, 2026 through Sunday, August 16, 2026 UTC

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

  39NM SW BUTTE, MT, Sunday, August 2, 2026 through Monday, August 17, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1038 2026-08-03 13:00Z – 2026-08-16 04:00Z SFC–14,000 ft

  9NM S ELY, NV, Monday, August 3, 2026 through Sunday, August 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1466 2026-08-04 02:39Z – 2026-08-17 14:00Z SFC–9,500 ft

  17NM NE IDAHO FALLS, ID, Tuesday, August 4, 2026 through Monday, August 17, 2026 UTC

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

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

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

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

  View FAA NOTAM →
• HAZARDS6/1474 2026-08-04 14:00Z – 2026-08-18 04:00Z SFC–13,000 ft

  34NM SW BUTTE, MT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1465 2026-08-05 04:00Z – 2026-08-17 14:00Z SFC–9,500 ft

  17NM NE IDAHO FALLS, ID, Wednesday, August 5, 2026 through Monday, August 17, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1960 2026-08-05 12:00Z – 2026-08-18 04:00Z SFC–9,500 ft

  17NM NE IDAHO FALLS, ID, Wednesday, August 5, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1961 2026-08-05 13:00Z – 2026-08-19 04:00Z SFC–14,000 ft

  9NM S ELY, NV, Wednesday, August 5, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2313 2026-08-05 20:36Z – 2026-08-20 04:00Z SFC–13,000 ft

  34NM SW BUTTE, MT, Wednesday, August 5, 2026 through Thursday, August 20, 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