Return to field — TKR41

KABQ · 21

2026-06-21 00:04 UTC· KABQ → KABQ· NEPTUNE AVIATION SERVICES INC· B462

TKR41 (Neptune Aviation Services) had departed KABQ on 2026-06-21. SkyMeter detected a return to field at Albuquerque International Sunport (KABQ) on runway 21 at 00:04 UTC. Peak altitude 11,106 ft, turnaround area near Meadow Lake, US. Approach stability score: 43/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)
  • HAZARDS6/9420 2026-06-20 21:25Z – 2026-07-04 04:00Z SFC–12,000 ft

    40NM SE ALBUQUERQUE, NM, Saturday, June 20, 2026 through Saturday, July 4, 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 21
  • 11106 ft AGL at event
  • 317 kt ground speed
  • 0 fpm vertical
  • Approach stability 43/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KABQ 100652Z 12006KT 10SM CLR 16/06 A3008 RMK AO2 SLP116 T01560061 402500133

Flight context

  • TKR41
  • Neptune Aviation Services
  • B462
  • KABQ → KABQ
  • 2026-06-21 00:04 UTC
  • KABQ runway 21

All events on this flight

Return to field 00:04:48 UTC · KABQ runway 21 · 11,106 ft AGL · 317 kt GS
Unstable approach 00:30:30 UTC · KABQ runway 26 · 6,427 ft AGL · 175 kt GS
Unstable approach 00:30:30 UTC · KABQ runway 26 · 6,427 ft AGL · 175 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· KABQ