Return to field — TKR104

K4SD

2026-08-27 01:13 UTC· K4SD → K4SD· CORSAIR TWO LLC· MD87

▶ Replay 📊 Analyse

TKR104 (Corsair TWO) had departed K4SD on 2026-08-27. SkyMeter detected a return to field at Reno-Stead Airport (K4SD) at 01:13 UTC. Peak altitude 11,952 ft, turnaround area near Fernley, US. Approach stability score: 32/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. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • 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 →
  • HAZARDS6/7667 2026-08-25 14:00Z – 2026-08-31 04:00Z SFC–11,500 ft

    1NM W RENO, NV, Tuesday, August 25, 2026 through Monday, August 31, 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

  • 11952 ft AGL at event
  • 356 kt ground speed
  • 0 fpm vertical
  • Approach stability 32/100
  • 0 kt wind
  • 0 kt crosswind component

Flight context

  • TKR104
  • Corsair TWO
  • MD87
  • K4SD → K4SD
  • 2026-08-27 01:13 UTC
  • K4SD

All events on this flight

Return to field 01:13:12 UTC · K4SD · 11,952 ft AGL · 356 kt GS
Unstable approach 01:56:19 UTC · K4SD runway 26 · 6,142 ft AGL · 165 kt GS
Unstable approach 01:56:19 UTC · K4SD runway 26 · 6,142 ft AGL · 165 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· K4SD