Return to field — N701JS

KABQ · 03

2026-06-25 15:06 UTC· KABQ → KABQ· REGISTRATION PENDING· C25B

▶ Replay 📊 Analyse

N701JS (Registration Pending) had departed KABQ on 2026-06-25. SkyMeter detected a return to field at Albuquerque International Sunport (KABQ) on runway 03 at 15:06 UTC. Peak cruise altitude FL454, turnaround area near San Carlos, MX. Approach stability score: 65/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. 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 →
  • HAZARDS6/9456 2026-06-21 13:00Z – 2026-07-05 04:00Z SFC–12,000 ft

    40NM SE ALBUQUERQUE, NM, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0466 2026-06-24 16:30Z – 2026-06-30 03:00Z SFC–13,000 ft

    50NM E ALBUQUERQUE, NM, Wednesday, June 24, 2026 through Tuesday, June 30, 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 03
  • 45423 ft AGL at event
  • 382 kt ground speed
  • 0 fpm vertical
  • Approach stability 65/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KABQ 160452Z 08018G24KT 10SM BKN110 BKN200 22/14 A3023 RMK AO2 PK WND 09027/0428 RAE51 SLP160 P0000 T02170139

Flight context

  • N701JS
  • Registration Pending
  • C25B
  • KABQ → KABQ
  • 2026-06-25 15:06 UTC
  • KABQ runway 03

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