Unstable approach — LXJ368

LXJ368 (Tvpx ARS) was operating from KIXD to KBZN on 2026-08-10. SkyMeter detected a low approach-stability score at Gallatin Field (KBZN) on runway 30 at 23:28 UTC. Trace data at the event: 5492 ft AGL, 163 kt GS. Approach stability score: 53/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 5 kt wind, 3 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/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft

  33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

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

  19NM NW GRAND JUNCTION, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 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/1471 2026-08-04 14:00Z – 2026-08-19 04:00Z SFC–9,500 ft

  33NM SW BROADUS, MT, Tuesday, August 4, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2488 2026-08-06 14:00Z – 2026-08-20 05:00Z SFC–13,500 ft

  28NM W AFTON, WY, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• SECURITY6/1983 2026-08-07 06:01Z – 2026-08-17 05:59Z SFC–400 ft

  Sturgis, SD, Friday, August 7, 2026 through Sunday, August 16, 2026 Local

  View FAA NOTAM →
• HAZARDS6/2761 2026-08-07 14:00Z – 2026-08-22 03:30Z SFC–12,000 ft

  10NM SE LIVINGSTON, MT, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC

  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/2829 2026-08-07 14:00Z – 2026-08-22 03:30Z SFC–12,000 ft

  10NM SE LIVINGSTON, MT, 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/2917 2026-08-08 14:00Z – 2026-08-22 05:00Z SFC–13,500 ft

  20NM E AFTON, WY, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3139 2026-08-09 22:49Z – 2026-08-11 04:00Z SFC–16,000 ft

  13NM SE LANDER, WY, Sunday, August 9, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3161 2026-08-10 12:00Z – 2026-08-25 03:30Z SFC–16,000 ft

  13NM SE LANDER, WY, Monday, August 10, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3448 2026-08-10 17:26Z – 2026-08-12 04:00Z SFC–16,000 ft

  14NM SE LANDER, WY, Monday, August 10, 2026 through Wednesday, August 12, 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.

All events on this flight

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