Unstable approach — EJA214

EJA214 (Netjets Sales) was operating from KBOI to KLAS on 2026-08-31. SkyMeter detected a low approach-stability score at McCarran International Airport (KLAS) on runway 19R at 19:04 UTC. Trace data at the event: 3267 ft AGL, 140 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 11 kt wind, 6 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/6067 2026-08-18 18:15Z – 2026-09-01 02:00Z SFC–11,000 ft

  52NM NE FALLON, NV, Tuesday, August 18, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7121 2026-08-23 03:30Z – 2026-09-05 04:00Z SFC–10,000 ft

  60NM SW MOUNTAIN HOME, ID, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7655 2026-08-25 14:00Z – 2026-09-01 04:00Z SFC–11,000 ft

  7NM N WELLS, NV, Tuesday, August 25, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7898 2026-08-25 19:45Z – 2026-09-01 04:00Z SFC–13,000 ft

  7NM E WINNEMUCCA, NV, Tuesday, August 25, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8111 2026-08-26 02:30Z – 2026-09-09 04:00Z SFC–10,000 ft

  60NM SW MOUNTAIN HOME, ID, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8238 2026-08-26 15:00Z – 2026-09-02 03:00Z SFC–13,000 ft

  7NM E WINNEMUCCA, NV, Wednesday, August 26, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8332 2026-08-26 17:45Z – 2026-09-05 04:00Z SFC–11,000 ft

  51NM NE FALLON, NV, Wednesday, August 26, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8467 2026-08-26 23:45Z – 2026-09-02 03:00Z SFC–10,500 ft

  62NM NE WINNEMUCCA, NV, Wednesday, August 26, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8474 2026-08-27 00:30Z – 2026-09-04 03:00Z SFC–13,000 ft

  37NM N WINNEMUCCA, NV, Thursday, August 27, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8492 2026-08-27 01:45Z – 2026-09-04 03:00Z SFC–8,000 ft

  16NM SW BOISE, ID, Thursday, August 27, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8507 2026-08-27 03:15Z – 2026-09-05 03:00Z SFC–11,000 ft

  51NM NE FALLON, NV, Thursday, August 27, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8588 2026-08-27 18:00Z – 2026-09-09 03:00Z SFC–10,500 ft

  62NM NE WINNEMUCCA, NV, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8676 2026-08-27 23:15Z – 2026-09-10 03:00Z SFC–13,000 ft

  37NM N WINNEMUCCA, NV, Thursday, August 27, 2026 through Thursday, September 10, 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