Unstable approach — N604SG

N604SG (GAF Holdings) was operating from MT44 to KBDN on 2026-07-09. SkyMeter detected a low approach-stability score at Bend Municipal Airport (KBDN) on runway 17 at 19:52 UTC. Trace data at the event: 4530 ft AGL, 196 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 5 kt wind, 1 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/0606 2026-06-25 14:00Z – 2026-07-10 04:00Z SFC–10,000 ft

  37NM SW GRANGEVILLE, ID, Thursday, June 25, 2026 through Friday, July 10, 2026 UTC

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

  37NM SW GRANGEVILLE, ID, Thursday, June 25, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1022 2026-06-27 14:00Z – 2026-07-12 04:00Z SFC–10,000 ft

  37NM SW GRANGEVILLE, ID, Saturday, June 27, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1023 2026-06-27 14:00Z – 2026-07-12 04:00Z SFC–10,000 ft

  37NM SW GRANGEVILLE, ID, Saturday, June 27, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1247 2026-06-28 22:17Z – 2026-07-10 16:00Z SFC–5,500 ft

  7NM NW THE DALLES, OR, Sunday, June 28, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1675 2026-06-29 21:09Z – 2026-07-13 04:00Z SFC–6,000 ft

  75 ZSE AIRSPACE 13NM SE PASCO, WA, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1598 2026-06-30 15:00Z – 2026-07-11 23:00Z SFC–5,500 ft

  7NM NW THE DALLES, OR, Tuesday, June 30, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1787 2026-06-30 15:00Z – 2026-07-14 04:00Z SFC–6,000 ft

  13NM SE PASCO, WA, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2576 2026-07-02 13:00Z – 2026-07-16 02:00Z SFC–10,000 ft

  38NM SW GRANGEVILLE, ID, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2586 2026-07-02 13:00Z – 2026-07-16 02:00Z SFC–10,000 ft

  38NM SW GRANGEVILLE, ID, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2839 2026-07-03 22:52Z – 2026-07-11 03:00Z SFC–6,000 ft

  5NM NE THE DALLES, OR, Friday, July 3, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2989 2026-07-05 17:35Z – 2026-07-20 05:00Z SFC–7,000 ft

  15NM E PENDLETON, OR, Sunday, July 5, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3022 2026-07-06 14:00Z – 2026-07-20 05:00Z SFC–8,000 ft

  15NM E PENDLETON, OR, Monday, July 6, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4238 2026-07-09 13:00Z – 2026-07-23 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4242 2026-07-09 13:00Z – 2026-07-23 05:00Z SFC–11,000 ft

  25 NM NE JOHN DAY, OR, Thursday, July 9, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4239 2026-07-09 14:00Z – 2026-07-23 05:00Z SFC–11,500 ft

  20NM NW BAKER CITY, OR, Thursday, July 9, 2026 through Thursday, July 23, 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