Unstable approach — LXJ560
KAPC · 19R2026-07-06 22:12 UTC· KCOS → KAPC· FLEXJET LLC, KANWAR RAHUL, EDGEWOOD PARTNERS INSURANCE CENTER, E· CL35
LXJ560 (Flexjet) was operating from KCOS to KAPC on 2026-07-06. SkyMeter detected a low approach-stability score at Napa County Airport (KAPC) on runway 19R at 22:12 UTC. Trace data at the event: 1143 ft AGL, 149 kt GS. Approach stability score: 45/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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/4061 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local
View FAA NOTAM → - SECURITY6/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
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/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/1053 2026-06-27 14:00Z – 2026-07-11 04:00Z SFC–15,000 ft
21NM NW BLANDING, UT, Saturday, June 27, 2026 through Saturday, July 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/1130 2026-06-28 06:00Z – 2026-07-12 04:00Z SFC–12,500 ft
22NM N CORTEZ, CO, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1178 2026-06-28 13:31Z – 2026-07-13 04:00Z SFC–17,000 ft
2NM N OURAY, CO, Sunday, June 28, 2026 through Monday, July 13, 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 → - HAZARDS6/1310 2026-06-29 12:00Z – 2026-07-13 04:00Z SFC–17,000 ft
2NM N OURAY, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1324 2026-06-29 12:00Z – 2026-07-13 05:00Z SFC–13,000 ft
18NM N CORTEZ, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1416 2026-06-29 14:37Z – 2026-07-14 04:00Z SFC–13,500 ft
15NM NW CAÑON CITY, CO, Monday, June 29, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/1775 2026-06-30 06:00Z – 2026-07-14 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/1778 2026-06-30 14:00Z – 2026-07-13 04:00Z SFC–16,000 ft
16NM W MONTICELLO, UT, Tuesday, June 30, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/2312 2026-07-01 04:00Z – 2026-07-15 04:00Z SFC–14,000 ft
20NM W WALSENBURG, CO, Wednesday, July 1, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/2597 2026-07-02 04:41Z – 2026-07-16 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/2594 2026-07-02 13:00Z – 2026-07-15 04:00Z SFC–12,000 ft
23NM S PANACA, NV, Thursday, July 2, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/2595 2026-07-02 14:00Z – 2026-07-13 05:00Z SFC–12,000 ft
12NM N PIOCHE, NV, Thursday, July 2, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/2593 2026-07-02 14:00Z – 2026-07-13 05:00Z SFC–12,000 ft
12NM N PIOCHE, NV, Thursday, July 2, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/2667 2026-07-02 15:00Z – 2026-07-16 05:00Z SFC–13,000 ft
18NM N CORTEZ, CO, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/2812 2026-07-03 02:53Z – 2026-07-17 04:00Z SFC–17,000 ft
1NM N OURAY, CO, Friday, July 3, 2026 through Friday, July 17, 2026 UTC
View FAA NOTAM → - HAZARDS6/2600 2026-07-03 12:00Z – 2026-07-16 05:00Z SFC–13,000 ft
18NM N CORTEZ, CO, Friday, July 3, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - SECURITY6/7984 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft
Oakland, CA
View FAA NOTAM → - HAZARDS6/3021 2026-07-06 14:00Z – 2026-07-19 04:00Z SFC–16,000 ft
16NM W MONTICELLO, UT, Monday, July 6, 2026 through Sunday, July 19, 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.
Pilot review data
- Runway 19R
- 1143 ft AGL at event
- 149 kt ground speed
- 0 fpm vertical
- Approach stability 45/100
- 14 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- METAR KAPC 051554Z 00000KT 10SM CLR 19/15 A2996 RMK AO2 SLP137 T01890150
Flight context
- LXJ560
- Flexjet
- CL35
- KCOS → KAPC
- 2026-07-06 22:12 UTC
- KAPC runway 19R
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