Return to field — TKR107

KABI · 17L

2026-08-28 20:59 UTC· KABI → KABI· CORSAIR TWO LLC· MD87

▶ Replay 📊 Analyse

TKR107 (Corsair TWO) had departed KABI on 2026-08-28. SkyMeter detected a return to field at Abilene Regional Airport (KABI) on runway 17L at 20:59 UTC. Peak altitude 16,366 ft, turnaround area near San Angelo, US. Approach stability score: 27/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, 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/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

    SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 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 17L
  • 16366 ft AGL at event
  • 354 kt ground speed
  • 0 fpm vertical
  • Approach stability 27/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KABI 162152Z 15012G19KT 10SM CLR 38/09 A3013 RMK AO2 SLP172 T03780094

Flight context

  • TKR107
  • Corsair TWO
  • MD87
  • KABI → KABI
  • 2026-08-28 20:59 UTC
  • KABI runway 17L

All events on this flight

Return to field 20:59:20 UTC · KABI runway 17L · 16,366 ft AGL · 354 kt GS
Unstable approach 21:58:44 UTC · KABI runway 35R · 2,889 ft AGL · 146 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· KABI