Unstable approach — EJM134

EJM134 (Peno Bottom Aircraft) was operating from KRBD to KBJC on 2026-06-29. SkyMeter detected a low approach-stability score at Rocky Mountain Metropolitan Airport (KBJC) on runway 30R at 00:49 UTC. Trace data at the event: 6727 ft AGL, 163 kt GS. METAR at the time reported 12 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/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z

  STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• SECURITY6/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z

  OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

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

  Stillwater, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  NORMAN, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  IRVING, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4025 2026-06-01 05:00Z – 2026-07-21 04:59Z

  DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9124 2026-06-18 14:00Z – 2026-07-01 04:00Z SFC–15,000 ft

  10NM N LOS ALAMOS, NM, Thursday, June 18, 2026 through Wednesday, July 1, 2026 UTC

  View FAA NOTAM →
• 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 →
• HAZARDS6/0608 2026-06-25 13:00Z – 2026-07-09 03:00Z SFC–14,000 ft

  15NM W LOS ALAMOS, NM, Thursday, June 25, 2026 through Thursday, July 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1156 2026-06-28 14:00Z – 2026-07-12 03:00Z SFC–12,500 ft

  32NM NW TAOS, NM, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1169 2026-06-28 14:00Z – 2026-07-12 03:00Z SFC–12,500 ft

  32NM NW TAOS, NM, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1295 2026-06-29 00:10Z – 2026-06-29 12:00Z SFC–17,000 ft

  8NM SW LEADVILLE, CO, Monday, June 29, 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.

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