Return to field — N850TC
KPTK · 27R2026-08-23 20:59 UTC· KPTK → KPTK· TAUBMAN CO LLC· F2TH
N850TC (Taubman) had departed KPTK on 2026-08-23. SkyMeter detected a return to field at Oakland County International Airport (KPTK) on runway 27R at 20:59 UTC. Peak cruise altitude FL388, turnaround area near Kane, US. Approach stability score: 81/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. 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)- SECURITY6/5076 2026-08-19 15:00Z – 2026-08-30 22:00Z SFC–1,000 ft
Williamsport, PA, Wednesday, August 19, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - SECURITY6/5424 2026-08-21 22:00Z – 2026-08-27 03:59Z SFC–400 ft
East Rutherford, NJ, Friday, August 21, 2026 through Wednesday, August 26, 2026 Local
View FAA NOTAM → - SECURITY6/5426 2026-08-23 21:00Z – 2026-08-24 03:00Z SFC–1,000 ft
Williamsport, PA, Sunday, August 23, 2026 through Sunday, August 23, 2026 Local
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 27R
- 38810 ft AGL at event
- 499 kt ground speed
- 0 fpm vertical
- Approach stability 81/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KPTK 160653Z AUTO 00000KT 10SM BKN026 BKN120 20/19 A3020 RMK AO2 SLP224 T02000189
Flight context
- N850TC
- Taubman
- F2TH
- KPTK → KPTK
- 2026-08-23 20:59 UTC
- KPTK runway 27R
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