Unstable approach — LXJ546

LXJ546 (Flexjet) was inbound to KAPC on 2026-08-05. SkyMeter detected a low approach-stability score at Napa County Airport (KAPC) on runway 19R at 22:49 UTC. Trace data at the event: 1137 ft AGL, 130 kt GS. Approach stability score: 53/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 5 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/8435 2026-07-24 18:00Z – 2026-08-07 04:00Z SFC–10,000 ft

  44NM SW BURNS, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8460 2026-07-24 18:30Z – 2026-08-08 05:00Z SFC–10,000 ft

  95NM SE BURNS, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8481 2026-07-24 22:00Z – 2026-08-08 05:00Z SFC–11,500 ft

  57NM SE BURNS, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8487 2026-07-25 01:02Z – 2026-08-08 04:00Z SFC–10,500 ft

  12NM NE SUSANVILLE, CA, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8552 2026-07-25 17:30Z – 2026-08-09 04:00Z SFC–10,000 ft

  95NM SE BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8553 2026-07-25 17:30Z – 2026-08-09 04:00Z SFC–11,500 ft

  44NM SE BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8761 2026-07-26 16:30Z – 2026-08-09 05:00Z SFC–11,500 ft

  50NM SE BURNS, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8762 2026-07-26 17:00Z – 2026-08-10 05:00Z SFC–10,000 ft

  95NM SE BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8784 2026-07-26 18:45Z – 2026-08-10 05:00Z SFC–10,000 ft

  44NM SW BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9354 2026-07-27 22:15Z – 2026-08-10 05:00Z SFC–10,000 ft

  26NM S BURNS, OR, Monday, July 27, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9397 2026-07-28 01:03Z – 2026-08-11 04:00Z SFC–5,000 ft

  9NM NW GRASS VALLEY, CA, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9393 2026-07-28 14:00Z – 2026-08-11 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9532 2026-07-28 15:45Z – 2026-08-11 05:00Z SFC–11,500 ft

  36NM E BURNS, OR, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9891 2026-07-29 05:00Z – 2026-08-12 05:00Z SFC–11,500 ft

  36NM E BURNS, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9893 2026-07-29 05:15Z – 2026-08-12 05:00Z SFC–10,000 ft

  95NM SE BURNS, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9879 2026-07-29 14:00Z – 2026-08-11 04:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0304 2026-07-30 00:15Z – 2026-08-12 05:00Z SFC–11,500 ft

  36NM E BURNS, OR, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0406 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0407 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0417 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–10,000 ft

  34NM S BURNS, OR, Thursday, July 30, 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/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/1972 2026-08-05 15:00Z – 2026-08-18 05:00Z SFC–10,000 ft

  44NM SW BURNS, OR, Wednesday, August 5, 2026 through Tuesday, August 18, 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 →

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