Unstable approach — N5341M

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. 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.

• 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/6608 2026-06-09 15:00Z – 2026-06-22 04:00Z SFC–11,500 ft

  13NM W NUCLA, CO, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC

  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/7478 2026-06-11 03:12Z – 2026-06-24 04:00Z SFC–11,500 ft

  20NM N NUCLA, CO, Thursday, June 11, 2026 through Wednesday, June 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7479 2026-06-11 03:19Z – 2026-06-24 04:00Z SFC–11,500 ft

  10NM NW NUCLA, CO, Thursday, June 11, 2026 through Wednesday, June 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7811 2026-06-12 03:18Z – 2026-06-25 04:00Z SFC–12,500 ft

  29NM SE GLENWOOD SPRINGS, CO, Friday, June 12, 2026 through Thursday, June 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8549 2026-06-16 02:58Z – 2026-06-30 04:00Z SFC–12,000 ft

  12NM NE GRAND JUNCTION, CO, Tuesday, June 16, 2026 through Tuesday, June 30, 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.

All events on this flight

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