Unstable approach — EJA534

EJA534 (Netjets Sales) was operating from KSLC to KAPC on 2026-06-28. SkyMeter detected a low approach-stability score at Napa County Airport (KAPC) on runway 19R at 18:07 UTC. Trace data at the event: 1146 ft AGL, 129 kt GS. Approach stability score: 52/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 8 kt wind, 1 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/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/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/9562 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft

  29NM NW TOOELE, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9582 2026-06-22 13:04Z – 2026-07-05 15:00Z SFC–10,500 ft

  29NM NW TOOELE, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9981 2026-06-23 13:28Z – 2026-07-07 15:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9985 2026-06-23 13:54Z – 2026-07-07 15:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0134 2026-06-23 17:52Z – 2026-07-07 04:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0416 2026-06-24 14:54Z – 2026-07-07 04:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Wednesday, June 24, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1019 2026-06-26 23:25Z – 2026-07-08 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Friday, June 26, 2026 through Wednesday, July 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1072 2026-06-27 14:12Z – 2026-07-10 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1074 2026-06-27 14:41Z – 2026-07-10 04:00Z SFC–11,000 ft

  7NM S SCIPIO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1144 2026-06-28 14:00Z – 2026-07-11 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1220 2026-06-28 16:15Z – 2026-07-11 04:00Z SFC–15,500 ft

  3NM E BEAVER, UT, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/0505 2026-06-28 17:00Z – 2026-06-28 21:00Z SFC–7,000 ft

  Sonoma, CA, Sunday, June 28, 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