Unstable approach — JRE283

JRE283 (GPS 3) was operating from KVNY to KMRY on 2026-08-08. SkyMeter detected a low approach-stability score at Monterey Peninsula Airport (KMRY) on runway 28L at 23:14 UTC. Trace data at the event: 1369 ft AGL, 121 kt GS. METAR at the time reported 8 kt wind, 3 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/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

  BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

  SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

  View FAA NOTAM →
• HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft

  20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft

  20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8554 2026-07-26 12:00Z – 2026-08-10 03:00Z SFC–12,000 ft

  16NM W MONTICELLO, UT, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8945 2026-07-27 14:57Z – 2026-08-09 04:00Z SFC–5,500 ft

  SONORA, CA, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9881 2026-07-29 02:10Z – 2026-08-12 04:00Z SFC–13,500 ft

  25NM S BISHOP, CA, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0722 2026-08-01 13:00Z – 2026-08-14 04:00Z SFC–14,000 ft

  9NM S ELY, NV, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1038 2026-08-03 13:00Z – 2026-08-16 04:00Z SFC–14,000 ft

  9NM S ELY, NV, Monday, August 3, 2026 through Sunday, August 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1461 2026-08-04 12:00Z – 2026-08-18 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1464 2026-08-04 12:00Z – 2026-08-18 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1795 2026-08-04 20:57Z – 2026-08-18 04:00Z SFC–6,000 ft

  27NM NE STOCKTON, CA, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1961 2026-08-05 13:00Z – 2026-08-19 04:00Z SFC–14,000 ft

  9NM S ELY, NV, Wednesday, August 5, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2274 2026-08-05 19:25Z – 2026-08-15 04:00Z SFC–13,500 ft

  25NM S BISHOP, CA, Wednesday, August 5, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2433 2026-08-05 21:49Z – 2026-08-15 04:00Z SFC–6,000 ft

  27NM NE STOCKTON, CA, Wednesday, August 5, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2489 2026-08-06 02:15Z – 2026-08-19 04:00Z SFC–9,000 ft

  27NM S BAKERSFIELD, CA, Thursday, August 6, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2889 2026-08-07 19:58Z – 2026-08-21 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Friday, August 7, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2916 2026-08-08 01:45Z – 2026-08-15 05:00Z SFC–6,000 ft

  25NM S BAKERSFIELD, CA, Saturday, August 8, 2026 through Saturday, August 15, 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