Return to field — N946TS

N946TS (TSP Leasing) had departed KPSC on 2026-08-25. SkyMeter detected a return to field at Tri Cities Airport (KPSC) on runway 30 at 21:10 UTC. Peak cruise altitude FL378, turnaround area near Adams County, US. Approach stability score: 57/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

• HAZARDS6/4057 2026-08-11 22:45Z – 2026-08-26 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Tuesday, August 11, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4083 2026-08-12 00:30Z – 2026-08-26 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Wednesday, August 12, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4094 2026-08-12 02:00Z – 2026-08-27 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4363 2026-08-12 17:00Z – 2026-08-26 04:00Z SFC–12,500 ft

  33NM N BOISE, ID, Wednesday, August 12, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4725 2026-08-13 14:00Z – 2026-08-27 07:00Z SFC–9,000 ft

  24NM E PENDLETON, OR, Thursday, August 13, 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/4911 2026-08-13 15:00Z – 2026-08-28 04:00Z SFC–7,500 ft

  10NM W LEWISTON, ID, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4722 2026-08-13 15:00Z – 2026-08-27 04:00Z SFC–9,000 ft

  39NM NE PENDLETON, OR, Thursday, August 13, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4957 2026-08-13 17:30Z – 2026-08-28 04:00Z SFC–10,500 ft

  18NM NW JOHN DAY, OR, Thursday, August 13, 2026 through Friday, August 28, 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/5137 2026-08-15 04:00Z – 2026-08-27 15:00Z SFC–6,500 ft

  18NM NW JOHN DAY, OR, Saturday, August 15, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5460 2026-08-17 12:00Z – 2026-08-30 04:00Z SFC–10,500 ft

  9NM SW HAMILTON, MT, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6726 2026-08-20 03:15Z – 2026-09-03 04:00Z SFC–9,000 ft

  25NM E PENDLETON, OR, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6724 2026-08-20 13:00Z – 2026-09-03 03:30Z SFC–11,500 ft

  32NM NE BOISE, ID, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7116 2026-08-23 01:35Z – 2026-08-26 04:00Z SFC–12,500 ft

  18NM W BAKER CITY, OR, Sunday, August 23, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7118 2026-08-23 02:10Z – 2026-08-26 04:00Z SFC–12,500 ft

  18NM W BAKER CITY, OR, Sunday, August 23, 2026 through Wednesday, August 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7123 2026-08-23 14:00Z – 2026-09-05 04:00Z SFC–12,500 ft

  18NM W BAKER CITY, OR, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7124 2026-08-23 14:00Z – 2026-09-05 04:00Z SFC–12,500 ft

  18NM W BAKER CITY, OR, Sunday, August 23, 2026 through Saturday, September 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.

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