Unstable approach — TKR102

KTWF · 26

2026-07-07 01:20 UTC· KBOI → KTWF· CORSAIR TWO LLC· MD87

▶ Replay 📊 Analyse

TKR102 (Corsair TWO) was operating from KBOI to KTWF on 2026-07-07. SkyMeter detected a low approach-stability score at Joslin Field Magic Valley Regional Airport (KTWF) on runway 26 at 01:20 UTC. Trace data at the event: 5196 ft AGL, 176 kt GS. Approach stability score: 35/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 5 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • 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 →
  • SECURITY6/4159 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

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

    View FAA NOTAM →
  • HAZARDS6/3570 2026-07-07 17:42Z – 2026-07-09 04:00Z SFC–9,500 ft

    4NM NE BOISE, ID, Tuesday, July 7, 2026 through Thursday, July 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.

Pilot review data

  • Runway 26
  • 5196 ft AGL at event
  • 176 kt ground speed
  • 0 fpm vertical
  • Approach stability 35/100
  • 5 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • KTWF 151953Z 05010KT 030V090 10SM CLR 28/09 A3016 RMK AO2 SLP154 T02830089

Flight context

  • TKR102
  • Corsair TWO
  • MD87
  • KBOI → KTWF
  • 2026-07-07 01:20 UTC
  • KTWF runway 26

All events on this flight

Unstable approach 01:20:26 UTC · KTWF runway 26 · 5,196 ft AGL · 176 kt GS
Unstable approach 01:20:26 UTC · KTWF runway 26 · 5,196 ft AGL · 176 kt GS
Unstable approach 01:20:26 UTC · KTWF runway 26 · 5,196 ft AGL · 176 kt GS
Unstable approach 01:20:26 UTC · KTWF runway 26 · 5,196 ft AGL · 176 kt GS

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

SkyMeter · trace data observed via ADS-B· KTWF