Unstable approach — S408

S408 (Aero Spray Inc DBA) was operating from KEUL to KLGD on 2026-08-04. SkyMeter detected a low approach-stability score at La Grande/Union County Airport (KLGD) on runway 35 at 22:38 UTC. Trace data at the event: 3774 ft AGL, 142 kt GS. Approach stability score: 24/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 9 kt wind, 5 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/8459 2026-07-24 18:00Z – 2026-08-08 04:00Z SFC–11,500 ft

  24NM E BAKER CITY, OR, Friday, July 24, 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/8654 2026-07-26 16:00Z – 2026-08-10 05:00Z SFC–11,500 ft

  36NM E BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8885 2026-07-27 05:00Z – 2026-08-10 05:00Z SFC–11,500 ft

  24NM E BAKER CITY, OR, Monday, July 27, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9227 2026-07-27 19:00Z – 2026-08-10 05:00Z SFC–11,500 ft

  24NM E BAKER CITY, OR, Monday, July 27, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9532 2026-07-28 15:45Z – 2026-08-11 05:00Z SFC–11,500 ft

  36NM E BURNS, OR, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

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

  36NM E BURNS, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0304 2026-07-30 00:15Z – 2026-08-12 05:00Z SFC–11,500 ft

  36NM E BURNS, OR, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0410 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–8,500 ft

  43NM NE BAKER CITY, OR, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0662 2026-08-01 03:00Z – 2026-08-10 03:00Z SFC–9,000 ft

  47NM SW MCCALL, ID, Saturday, August 1, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0869 2026-08-01 20:30Z – 2026-08-15 05:00Z SFC–11,500 ft

  24NM E BAKER CITY, OR, Saturday, August 1, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0892 2026-08-02 05:00Z – 2026-08-15 05:00Z SFC–11,500 ft

  45NM E BURNS, OR, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0899 2026-08-02 14:00Z – 2026-08-17 03:00Z SFC–9,000 ft

  47NM SW MCCALL, ID, Sunday, August 2, 2026 through Monday, August 17, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0943 2026-08-02 16:00Z – 2026-08-15 03:00Z SFC–9,000 ft

  47NM SW MCCALL, ID, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1467 2026-08-04 14:00Z – 2026-08-15 03:00Z SFC–9,000 ft

  47NM SW MCCALL, ID, Tuesday, August 4, 2026 through Saturday, August 15, 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