Unstable approach — PRE90

KBJC · 12L

2026-07-06 19:25 UTC· CYYC → KBJC· BANK OF UTAH TRUSTEE· F900

PRE90 (Bank of Utah) was operating from CYYC to KBJC on 2026-07-06. SkyMeter detected a low approach-stability score at Rocky Mountain Metropolitan Airport (KBJC) on runway 12L at 19:25 UTC. Trace data at the event: 6727 ft AGL, 156 kt GS. Approach stability score: 58/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 7 kt wind, 5 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/4164 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

    Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4167 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

    Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/9985 2026-06-23 13:54Z – 2026-07-07 15:00Z SFC–11,000 ft

    27NM SW PROVO, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0276 2026-06-24 15:00Z – 2026-07-07 04:00Z SFC–10,500 ft

    4NM SW SALT LAKE CITY, UT, Wednesday, June 24, 2026 through Tuesday, July 7, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0613 2026-06-25 13:00Z – 2026-07-08 03:00Z SFC–14,500 ft

    27NM SW JACKSON, WY, Thursday, June 25, 2026 through Wednesday, July 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1019 2026-06-26 23:25Z – 2026-07-08 04:00Z SFC–11,000 ft

    27NM SW PROVO, UT, Friday, June 26, 2026 through Wednesday, July 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1072 2026-06-27 14:12Z – 2026-07-10 04:00Z SFC–11,000 ft

    27NM SW PROVO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/1144 2026-06-28 14:00Z – 2026-07-11 04:00Z SFC–11,000 ft

    27NM SW PROVO, UT, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/2268 2026-07-01 13:00Z – 2026-07-14 03:00Z SFC–14,500 ft

    27NM SE JACKSON, WY, Wednesday, July 1, 2026 through Tuesday, July 14, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/7864 2026-07-03 15:07Z – 2026-07-21 05:59Z SFC–400 ft

    Sandy, UT

    View FAA NOTAM →
  • SECURITY6/7862 2026-07-03 16:07Z – 2026-07-21 05:59Z SFC–400 ft

    Salt Lake City, UT

    View FAA NOTAM →
  • SECURITY6/3018 2026-07-06 14:00Z – 2026-07-10 23:00Z SFC–400 ft

    Provo, UT, Monday, July 6, 2026 through Friday, July 10, 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 12L
  • 6727 ft AGL at event
  • 156 kt ground speed
  • 0 fpm vertical
  • Approach stability 58/100
  • 7 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • KBJC 070455Z AUTO 36006KT 10SM CLR 22/M01 A3020 RMK AO2

Flight context

  • PRE90
  • Bank of Utah
  • F900
  • CYYC → KBJC
  • 2026-07-06 19:25 UTC
  • KBJC runway 12L

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