Unstable approach — EJA655

EJA655 (Netjets Sales) was inbound to KLAS on 2026-07-05. SkyMeter detected a low approach-stability score at McCarran International Airport (KLAS) on runway 19R at 17:33 UTC. Trace data at the event: 3265 ft AGL, 139 kt GS. Approach stability score: 59/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, 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.

• 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/1019 2026-06-26 23:25Z – 2026-07-08 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Friday, June 26, 2026 through Wednesday, July 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1070 2026-06-27 13:47Z – 2026-07-10 04:00Z SFC–15,500 ft

  3NM E BEAVER, UT, Saturday, June 27, 2026 through Friday, July 10, 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/1072 2026-06-27 14:12Z – 2026-07-10 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1074 2026-06-27 14:41Z – 2026-07-10 04:00Z SFC–11,000 ft

  7NM S SCIPIO, UT, Saturday, June 27, 2026 through Friday, July 10, 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/1132 2026-06-28 12:00Z – 2026-07-12 04:00Z SFC–12,000 ft

  12NM N GRAND JUNCTION, CO, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1131 2026-06-28 12:00Z – 2026-07-12 04:00Z SFC–12,000 ft

  25NM W GRAND JUNCTION, CO, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1138 2026-06-28 13:00Z – 2026-07-11 04:00Z SFC–12,000 ft

  5NM S SCIPIO, UT, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1137 2026-06-28 14:00Z – 2026-07-12 04:00Z SFC–15,500 ft

  21NM NW BLANDING, UT, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC

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

  27NM SW PROVO, UT, Sunday, June 28, 2026 through Saturday, July 11, 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/1335 2026-06-29 01:32Z – 2026-07-13 04:00Z SFC–12,000 ft

  6NM S SCIPIO, UT, 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/1334 2026-06-29 12:00Z – 2026-07-13 04:00Z SFC–12,000 ft

  25NM W GRAND JUNCTION, CO, Monday, June 29, 2026 through Monday, July 13, 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/2598 2026-07-02 04:42Z – 2026-07-16 04:00Z SFC–12,000 ft

  25NM W GRAND JUNCTION, 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/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/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/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/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 →
• HAZARDS6/2845 2026-07-04 00:10Z – 2026-07-17 04:00Z SFC–12,500 ft

  6NM S SCIPIO, UT, Saturday, July 4, 2026 through Friday, July 17, 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