Return to field — TKR15
K4SD · 082026-08-11 22:21 UTC· K4SD → K4SD· NEPTUNE AVIATION SERVICES· B462
TKR15 (Neptune Aviation Services) had departed K4SD on 2026-08-11. SkyMeter detected a return to field at Reno-Stead Airport (K4SD) on runway 08 at 22:21 UTC. Peak altitude 10,095 ft, turnaround area near Spanish Springs, US. Approach stability score: 51/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. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/3128 2026-08-09 14:45Z – 2026-08-23 04:00Z SFC–11,000 ft
15NM NW RENO, NV, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - 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/3606 2026-08-10 21:45Z – 2026-08-24 04:00Z SFC–9,500 ft
22NM NE 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 →
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 08
- 10095 ft AGL at event
- 255 kt ground speed
- 0 fpm vertical
- Approach stability 51/100
- 0 kt wind
- 0 kt crosswind component
Flight context
- TKR15
- Neptune Aviation Services
- B462
- K4SD → K4SD
- 2026-08-11 22:21 UTC
- K4SD runway 08
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