Return to field — TKR16

KABI · 17L

2026-08-30 16:21 UTC· KABI → KABI· NEPTUNE AVIATION SERVICES INC· B462

▶ Replay 📊 Analyse

TKR16 (Neptune Aviation Services) had departed KABI on 2026-08-30. SkyMeter detected a return to field at Abilene Regional Airport (KABI) on runway 17L at 16:21 UTC. Peak cruise altitude FL185, turnaround area near Paint Rock, US. Approach stability score: 38/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
  • 18565 ft AGL at event
  • 337 kt ground speed
  • 0 fpm vertical
  • Approach stability 38/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KABI 162052Z 14005G16KT 10SM CLR 37/10 A3014 RMK AO2 SLP176 T03670100 58019

Flight context

  • TKR16
  • Neptune Aviation Services
  • B462
  • KABI → KABI
  • 2026-08-30 16:21 UTC
  • KABI runway 17L

All events on this flight

Return to field 16:21:43 UTC · KABI runway 17L · 18,565 ft AGL · 337 kt GS
Unstable approach 17:44:25 UTC · KABI runway 17R · 2,888 ft AGL · 134 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