Unstable approach — JTL939

JTL939 (MCH Aviation) was operating from KSAT to KLAS on 2026-07-12. SkyMeter detected a low approach-stability score at McCarran International Airport (KLAS) on runway 19L at 16:41 UTC. Trace data at the event: 3281 ft AGL, 138 kt GS. Approach stability score: 57/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 10 kt wind, 8 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/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft

  Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

  SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z

  MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Mesa, AZ

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

  Mesa, AZ

  View FAA NOTAM →
• HAZARDS6/1322 2026-06-29 03:00Z – 2026-07-13 16:00Z SFC–10,500 ft

  13NM SW FLAGSTAFF, AZ, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1323 2026-06-29 16:00Z – 2026-07-13 03:00Z SFC–10,500 ft

  13NM SW FLAGSTAFF, AZ, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1728 2026-06-30 03:00Z – 2026-07-13 16:00Z SFC–8,500 ft

  13NM SW FLAGSTAFF, AZ, Tuesday, June 30, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2561 2026-07-02 16:00Z – 2026-07-15 03:00Z SFC–12,000 ft

  13NM SW FLAGSTAFF, AZ, Thursday, July 2, 2026 through Wednesday, July 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2884 2026-07-04 17:45Z – 2026-07-18 03:00Z SFC–13,800 ft

  35NM NW SILVER CITY, NM, Saturday, July 4, 2026 through Saturday, July 18, 2026 UTC

  View FAA NOTAM →
• 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/3016 2026-07-06 14:00Z – 2026-07-20 04:00Z SFC–11,000 ft

  7NM SW FLAGSTAFF, AZ, Monday, July 6, 2026 through Monday, July 20, 2026 UTC

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

  7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3341 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–8,500 ft

  9NM S FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

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

  7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6820 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

  San Antonio, TX

  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