Unstable approach — ASP875

ASP875 (Airsprint) was operating from KCOE to KHND on 2026-07-27. SkyMeter detected a low approach-stability score at Henderson Executive Airport (KHND) on runway 17R at 17:23 UTC. Trace data at the event: 3594 ft AGL, 138 kt GS. Approach stability score: 45/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 11 kt wind, 6 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/6858 2026-07-20 14:00Z – 2026-08-04 04:00Z SFC–13,000 ft

  5NM N HAILEY, ID, Monday, July 20, 2026 through Tuesday, August 4, 2026 UTC

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

  4NM NE BOISE, ID, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8489 2026-07-25 01:45Z – 2026-08-08 04:00Z SFC–10,000 ft

  14NM NW MISSOULA, MT, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

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

  32NM NE MCCALL, ID, Saturday, July 25, 2026 through Friday, August 7, 2026 UTC

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

  32NM NE MCCALL, ID, Saturday, July 25, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8496 2026-07-25 14:00Z – 2026-08-08 04:00Z SFC–10,000 ft

  14NM NW MISSOULA, MT, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8582 2026-07-26 14:00Z – 2026-08-09 05:00Z SFC–8,500 ft

  43NM NE BAKER CITY, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8762 2026-07-26 17:00Z – 2026-08-10 05:00Z SFC–10,000 ft

  95NM SE BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8874 2026-07-27 11:00Z – 2026-08-09 05:00Z SFC–12,000 ft

  32NM NE MCCALL, ID, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8876 2026-07-27 11:00Z – 2026-08-09 05:00Z SFC–12,000 ft

  32NM NE MCCALL, ID, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8877 2026-07-27 12:00Z – 2026-08-10 02:00Z SFC–7,000 ft

  8NM NE BOISE, ID, Monday, July 27, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8872 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–11,000 ft

  14NM NW MISSOULA, MT, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC

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

  14NM NE AUSTIN, NV, Monday, July 27, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8883 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–11,000 ft

  23NM SE HAMILTON, MT, Monday, July 27, 2026 through Sunday, August 9, 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