Unstable approach — N5341M

KBJC · 30L

2026-06-21 21:54 UTC· 199ML II LLC· C25B

N5341M (199ml II) was inbound to KBJC on 2026-06-21. SkyMeter detected a low approach-stability score at Rocky Mountain Metropolitan Airport (KBJC) on runway 30L at 21:54 UTC. Trace data at the event: 6727 ft AGL, 149 kt GS. Approach stability score: 26/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 9 kt wind, 9 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/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

    MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • 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/6827 2026-06-09 17:15Z – 2026-06-22 02:00Z SFC–10,000 ft

    9NM SW TOOELE, UT, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6965 2026-06-10 14:00Z – 2026-06-22 03:00Z SFC–10,000 ft

    9NM SW TOOELE, UT, Wednesday, June 10, 2026 through Monday, June 22, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9121 2026-06-18 13:00Z – 2026-07-01 05:00Z SFC–7,000 ft

    10NM SE PENDLETON, OR, Thursday, June 18, 2026 through Wednesday, July 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft

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

    View FAA NOTAM →
  • HAZARDS6/9461 2026-06-21 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft

    3.5NM SW SALT LAKE CITY, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

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

    27NM SW PROVO, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9504 2026-06-21 14:14Z – 2026-07-05 15:00Z SFC–10,500 ft

    10NM NE OGDEN, UT, Sunday, June 21, 2026 through Sunday, July 5, 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 30L
  • 6727 ft AGL at event
  • 149 kt ground speed
  • 0 fpm vertical
  • Approach stability 26/100
  • 9 kt wind
  • 9 kt crosswind component
  • 16,093 m visibility
  • KBJC 100355Z AUTO 12003KT 10SM CLR 21/M02 A2992 RMK AO2

Flight context

  • N5341M
  • 199ml II
  • C25B
  • 2026-06-21 21:54 UTC
  • KBJC runway 30L

All events on this flight

Unstable approach 21:54:07 UTC · KBJC runway 30L · 6,727 ft AGL · 149 kt GS
Unstable approach 21:54:07 UTC · KBJC runway 30L · 6,727 ft AGL · 149 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