Unstable approach — EJA877

EJA877 (Arbor Group AIR) was operating from KOKC to KMRY on 2026-09-01. SkyMeter detected a low approach-stability score at Monterey Peninsula Airport (KMRY) on runway 28L at 16:21 UTC. Trace data at the event: 1365 ft AGL, 125 kt GS. Approach stability score: 57/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 3 kt wind, 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.

• HAZARDS6/6216 2026-08-19 03:00Z – 2026-09-02 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Wednesday, August 19, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8070 2026-08-26 03:00Z – 2026-09-10 03:00Z SFC–8,500 ft

  8NM SE BIG SUR, CA, Wednesday, August 26, 2026 through Thursday, September 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8454 2026-08-26 21:15Z – 2026-09-09 03:00Z SFC–7,500 ft

  20NM SW KING CITY, CA, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8493 2026-08-27 13:00Z – 2026-09-10 03:00Z SFC–8,000 ft

  20NM SW KING CITY, CA, Thursday, August 27, 2026 through Thursday, September 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8502 2026-08-27 14:00Z – 2026-09-09 03:00Z SFC–15,000 ft

  48NM NW TAOS, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8590 2026-08-27 18:00Z – 2026-09-09 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8735 2026-08-28 13:00Z – 2026-09-13 03:00Z SFC–8,000 ft

  20NM SW KING CITY, CA, Friday, August 28, 2026 through Sunday, September 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8806 2026-08-28 15:04Z – 2026-09-12 03:00Z SFC–15,000 ft

  30NM W TAOS, NM, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8889 2026-08-28 23:25Z – 2026-09-12 04:00Z SFC–13,500 ft

  15NM SW LAS VEGAS, NM, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8902 2026-08-29 13:00Z – 2026-09-13 03:00Z SFC–8,500 ft

  20NM SW KING CITY, CA, Saturday, August 29, 2026 through Sunday, September 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9082 2026-08-29 13:00Z – 2026-09-12 04:00Z SFC–13,500 ft

  15NM SW LAS VEGAS, NM, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8870 2026-08-29 14:00Z – 2026-09-12 03:00Z SFC–15,000 ft

  30NM W TAOS, NM, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9187 2026-08-30 13:00Z – 2026-09-13 03:00Z SFC–8,500 ft

  20NM SW KING CITY, CA, Sunday, August 30, 2026 through Sunday, September 13, 2026 UTC

  View FAA NOTAM →
• VIP6/8925 2026-08-31 22:30Z – 2026-09-01 17:30Z SFC–4,999 ft

  LAS VEGAS, NV, Monday, August 31, 2026 through Tuesday, September 1, 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