Unstable approach — JSX200

JSX200 (Delux Public Charter) was operating from KDAL to KLAS on 2026-08-04. SkyMeter detected a low approach-stability score at McCarran International Airport (KLAS) on runway 19R at 00:44 UTC. Trace data at the event: 3278 ft AGL, 145 kt GS. METAR at the time reported 16 kt wind, 4 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/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• HAZARDS6/9111 2026-07-28 14:00Z – 2026-08-10 03:00Z SFC–14,500 ft

  14NM N LOS ALAMOS, NM, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC

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

  13NM S SAFFORD, AZ, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0876 2026-08-02 14:00Z – 2026-08-09 02:00Z SFC–13,000 ft

  30NM NW ALBUQUERQUE, NM, Sunday, August 2, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1456 2026-08-03 23:57Z – 2026-08-04 13:00Z

  109 ELZABETH LN, TX, Monday, August 3, 2026 through Tuesday, August 4, 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