Unstable approach — N88CH

N88CH (BAM) was inbound to KBOI on 2026-07-10. SkyMeter detected a low approach-stability score at Boise Air Terminal/Gowen Field (KBOI) on runway 28L at 02:05 UTC. Trace data at the event: 3924 ft AGL, 135 kt GS. METAR at the time reported 6 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.

• SECURITY6/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  17NM NE WINNEMUCCA, NV, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7869 2026-07-09 11:07Z – 2026-07-21 05:59Z SFC–400 ft

  Meridian, ID

  View FAA NOTAM →
• SECURITY6/7871 2026-07-09 11:07Z – 2026-07-21 05:59Z SFC–400 ft

  Boise, ID

  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 →

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