Unstable approach — TKR101

TKR101 (Corsair TWO) was inbound to KBOI on 2026-08-26. SkyMeter detected a low approach-stability score at Boise Air Terminal/Gowen Field (KBOI) on runway 28L at 20:49 UTC. Trace data at the event: 3923 ft AGL, 149 kt GS. METAR at the time reported 9 kt wind, 2 kt crosswind component, 14,484 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/4111 2026-08-12 05:00Z – 2026-08-27 05:00Z SFC–10,000 ft

  104NM SE BURNS, OR, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC

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

  33NM N BOISE, ID, Thursday, August 13, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5073 2026-08-14 14:00Z – 2026-08-28 04:00Z SFC–12,500 ft

  33NM N BOISE, ID, Friday, August 14, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7121 2026-08-23 03:30Z – 2026-09-05 04:00Z SFC–10,000 ft

  60NM SW MOUNTAIN HOME, ID, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8111 2026-08-26 02:30Z – 2026-09-09 04:00Z SFC–10,000 ft

  60NM SW MOUNTAIN HOME, ID, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8402 2026-08-26 18:45Z – 2026-08-29 04:00Z SFC–11,000 ft

  104NM SE BURNS, OR, Wednesday, August 26, 2026 through Saturday, August 29, 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