Unstable approach — EJA200

EJA200 (Netjets Sales) was operating from KTEX to KAPC on 2026-06-20. SkyMeter detected a low approach-stability score at Napa County Airport (KAPC) on runway 19R at 20:40 UTC. Trace data at the event: 1136 ft AGL, 116 kt GS. METAR at the time reported 14 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 →
• SECURITY6/4167 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Seattle, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Renton, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/6225 2026-06-09 14:00Z – 2026-06-21 02:00Z SFC–10,500 ft

  31NM SW NEPHI, UT, Tuesday, June 9, 2026 through Sunday, June 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6608 2026-06-09 15:00Z – 2026-06-22 04:00Z SFC–11,500 ft

  13NM W NUCLA, CO, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6827 2026-06-09 17:15Z – 2026-06-22 02:00Z SFC–10,000 ft

  9NM SW TOOELE, UT, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6965 2026-06-10 14:00Z – 2026-06-22 03:00Z SFC–10,000 ft

  9NM SW TOOELE, UT, Wednesday, June 10, 2026 through Monday, June 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7478 2026-06-11 03:12Z – 2026-06-24 04:00Z SFC–11,500 ft

  20NM N NUCLA, CO, Thursday, June 11, 2026 through Wednesday, June 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7479 2026-06-11 03:19Z – 2026-06-24 04:00Z SFC–11,500 ft

  10NM NW NUCLA, CO, Thursday, June 11, 2026 through Wednesday, June 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8221 2026-06-14 20:07Z – 2026-06-28 03:00Z SFC–6,000 ft

  22NM SE RICHLAND, WA, Sunday, June 14, 2026 through Sunday, June 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8252 2026-06-15 04:35Z – 2026-06-26 04:00Z SFC–5,500 ft

  12NM NE PASCO, WA, Monday, June 15, 2026 through Friday, June 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8253 2026-06-15 15:00Z – 2026-06-30 05:00Z SFC–6,000 ft

  3NM W BENTON CITY, WA, Monday, June 15, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8549 2026-06-16 02:58Z – 2026-06-30 04:00Z SFC–12,000 ft

  12NM NE GRAND JUNCTION, CO, Tuesday, June 16, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8752 2026-06-16 20:30Z – 2026-06-23 04:00Z SFC–6,500 ft

  12NM NE PASCO, WA, Tuesday, June 16, 2026 through Tuesday, June 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8960 2026-06-17 15:23Z – 2026-07-01 06:00Z SFC–7,000 ft

  14NM SE OMAK, WA, Wednesday, June 17, 2026 through Wednesday, July 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8961 2026-06-17 15:50Z – 2026-06-24 04:00Z SFC–7,500 ft

  11NM NE YAKIMA, WA, Wednesday, June 17, 2026 through Wednesday, June 24, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9121 2026-06-18 13:00Z – 2026-07-01 05:00Z SFC–7,000 ft

  10NM SE PENDLETON, OR, Thursday, June 18, 2026 through Wednesday, July 1, 2026 UTC

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

  14NM SE OMAK, WA, Thursday, June 18, 2026 through Wednesday, July 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8821 2026-06-18 14:00Z – 2026-07-02 05:00Z SFC–7,500 ft

  34NM SE COEUR D'ALENE, ID, Thursday, June 18, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9120 2026-06-18 14:00Z – 2026-06-24 05:00Z SFC–7,000 ft

  34NM SW PULLMAN, WA, Thursday, June 18, 2026 through Wednesday, June 24, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/7982 2026-06-19 18:00Z – 2026-06-20 22:30Z SFC–17,999 ft

  Truckee, CA, Friday, June 19, 2026 through Saturday, June 20, 2026 UTC

  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 →

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