Return to field — TKR162

KCOE · 24

2026-07-23 19:27 UTC· KCOE → KCOE· AERO-FLITE INC· RJ85

▶ Replay 📊 Analyse

TKR162 (Aero-Flite) had departed KCOE on 2026-07-23. SkyMeter detected a return to field at Coeur D'Alene - Pappy Boyington Field (KCOE) on runway 24 at 19:27 UTC. Peak altitude 15,350 ft, turnaround area near Deer Park, US. 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
  • 15350 ft AGL at event
  • 317 kt ground speed
  • 0 fpm vertical
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KCOE 161356Z AUTO 03010KT 10SM CLR 10/07 A3017 RMK AO2 SLP233 T01000072 PNO $

Flight context

  • TKR162
  • Aero-Flite
  • RJ85
  • KCOE → KCOE
  • 2026-07-23 19:27 UTC
  • KCOE runway 24

All events on this flight

Return to field 19:27:35 UTC · KCOE runway 24 · 15,350 ft AGL · 317 kt GS
Go-around 20:24:19 UTC · KCOE runway 24 · 2,437 ft AGL · 119 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· KCOE