Return to field — TKR102
KCOE · 242026-07-24 18:51 UTC· KCOE → KCOE· CORSAIR TWO LLC· MD87
TKR102 (Corsair TWO) had departed KCOE on 2026-07-24. SkyMeter detected a return to field at Coeur D'Alene - Pappy Boyington Field (KCOE) on runway 24 at 18:51 UTC. Peak altitude 11,975 ft, turnaround area near Deer Park, US. Approach stability score: 36/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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/6668 2026-07-18 16:29Z – 2026-07-31 05:00Z SFC–7,000 ft
SPOKANE, WA, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6811 2026-07-19 22:54Z – 2026-08-03 03:00Z SFC–7,000 ft
42NM NW SPOKANE, WA, Sunday, July 19, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/7610 2026-07-21 23:48Z – 2026-08-05 05:00Z SFC–7,000 ft
42NM NW SPOKANE, WA, Tuesday, July 21, 2026 through Wednesday, August 5, 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 24
- 11975 ft AGL at event
- 370 kt ground speed
- 0 fpm vertical
- Approach stability 36/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KCOE 161056Z AUTO 03012KT 10SM CLR 11/08 A3012 RMK AO2 SLP211 T01110078 PNO $
Flight context
- TKR102
- Corsair TWO
- MD87
- KCOE → KCOE
- 2026-07-24 18:51 UTC
- KCOE runway 24
All events on this flight
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