Unstable approach — EJA801

EJA801 (Netjets Sales) was operating from KIAD to KBJC on 2026-07-24. SkyMeter detected a low approach-stability score at Rocky Mountain Metropolitan Airport (KBJC) on runway 12L at 21:52 UTC. Trace data at the event: 6736 ft AGL, 140 kt GS. Approach stability score: 55/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 6 kt wind, 4 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/5841 2026-07-16 13:00Z – 2026-07-27 05:59Z SFC–400 ft

  Cheyenne, WY, Thursday, July 16, 2026 through Sunday, July 26, 2026 Local

  View FAA NOTAM →
• SECURITY6/7851 2026-07-23 17:00Z – 2026-07-27 04:59Z SFC–400 ft

  Westfield, IN, Thursday, July 23, 2026 through Sunday, July 26, 2026 Local

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/6521 2026-07-23 21:30Z – 2026-07-26 04:00Z SFC–400 ft

  cincinnati, OH, Thursday, July 23, 2026 through Sunday, July 26, 2026 UTC

  View FAA NOTAM →
• SECURITY6/8361 2026-07-24 13:00Z – 2026-07-27 04:59Z SFC–400 ft

  Westfield, IN, Friday, July 24, 2026 through Sunday, July 26, 2026 Local

  View FAA NOTAM →
• VIP6/8360 2026-07-24 19:00Z – 2026-07-26 23:00Z SFC–4,999 ft

  Middleburg, VA, Friday, July 24, 2026 through Sunday, July 26, 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.

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