Return to field — JAS302

KBJC

2026-07-16 00:00 UTC· KBJC → KBJC· FREEDOM 105 LLC· GA6C

▶ Replay 📊 Analyse

JAS302 (Freedom 105) had departed KBJC on 2026-07-16. SkyMeter detected a return to field at Rocky Mountain Metropolitan Airport (KBJC) at 00:00 UTC. Peak cruise altitude FL494, turnaround area near Rawlins, US. Approach stability score: 49/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/2597 2026-07-02 04:41Z – 2026-07-16 04:00Z SFC–15,000 ft

    4NM SW PUEBLO, CO, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/3801 2026-07-08 01:49Z – 2026-07-23 04:00Z SFC–15,000 ft

    1NM W PUEBLO, CO, Wednesday, July 8, 2026 through Thursday, July 23, 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

  • 49479 ft AGL at event
  • 540 kt ground speed
  • 0 fpm vertical
  • Approach stability 49/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • METAR KBJC 271547Z 17004KT 10SM SCT110 22/07 A3022

Flight context

  • JAS302
  • Freedom 105
  • GA6C
  • KBJC → KBJC
  • 2026-07-16 00:00 UTC
  • KBJC

All events on this flight

Return to field 00:00:17 UTC · KBJC · 49,479 ft AGL · 540 kt GS
Unstable approach 01:05:01 UTC · KBJC runway 12L · 6,721 ft AGL · 125 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· KBJC