Return to field — TKR15

TKR15 (Neptune Aviation Services) had departed K4SD on 2026-08-23. SkyMeter detected a return to field at Reno-Stead Airport (K4SD) on runway 08 at 22:50 UTC. Peak altitude 8,752 ft, turnaround area near Lemmon Valley, US. METAR at the time reported 0 kt wind. Detection algorithm and known limitations: see SkyMeter methodology.

• HAZARDS6/3162 2026-08-10 04:00Z – 2026-08-24 04:00Z SFC–9,500 ft

  15NM NW RENO, NV, Monday, August 10, 2026 through Monday, August 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3717 2026-08-11 14:58Z – 2026-08-24 04:00Z SFC–9,500 ft

  15NM NW RENO, NV, Tuesday, August 11, 2026 through Monday, August 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4104 2026-08-12 04:00Z – 2026-08-25 04:00Z SFC–11,000 ft

  15NM NW RENO, NV, Wednesday, August 12, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5067 2026-08-14 02:15Z – 2026-08-27 04:00Z SFC–11,000 ft

  15NM NW RENO, NV, Friday, August 14, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5242 2026-08-15 23:15Z – 2026-08-29 04:00Z SFC–9,500 ft

  15NM NW RENO, NV, Saturday, August 15, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5897 2026-08-18 14:00Z – 2026-08-31 02:00Z SFC–7,500 ft

  15NM NW RENO, NV, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

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

  1NM W RENO, NV, Saturday, August 22, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7127 2026-08-23 05:30Z – 2026-09-06 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7283 2026-08-23 16:00Z – 2026-09-06 03:00Z SFC–11,500 ft

  1NM W RENO, NV, Sunday, August 23, 2026 through Sunday, September 6, 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