LET6250 was operating from KBRO to KLAS on 2026-08-13. SkyMeter detected a low approach-stability score at McCarran International Airport (KLAS) on runway 19R at 21:42 UTC. Trace data at the event: 3283 ft AGL, 159 kt GS. Approach stability score: 53/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 12 kt wind, 1 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/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/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/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/2435 2026-08-06 13:00Z – 2026-08-20 04:00Z SFC–13,500 ft
13NM N SANTA FE, NM, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2747 2026-08-07 12:00Z – 2026-08-14 03:00Z SFC–14,000 ft
24NM SE ALBUQUERQUE, NM, Friday, August 7, 2026 through Friday, August 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/2842 2026-08-07 14:30Z – 2026-08-21 04:00Z SFC–13,500 ft
13NM N SANTA FE, NM, Friday, August 7, 2026 through Friday, August 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/3075 2026-08-08 19:30Z – 2026-08-22 04:00Z SFC–12,000 ft
28NM NE LAS VEGAS, NM, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/3712 2026-08-11 14:00Z – 2026-08-25 04:00Z SFC–8,000 ft
18NM SW PRESCOTT, AZ, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/4586 2026-08-12 21:50Z – 2026-08-13 21:50Z SFC–20 ft
YOUNGSPORT, TX, Wednesday, August 12, 2026 through Thursday, August 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/4962 2026-08-13 18:15Z – 2026-08-20 18:00Z SFC–2,000 ft
YOUNGSPORT, TX, Thursday, August 13, 2026 through Thursday, August 20, 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
- 3283 ft AGL at event
- 159 kt ground speed
- 0 fpm vertical
- Approach stability 53/100
- 12 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KLAS 161456Z 15006KT 10SM FEW200 28/12 A2995 RMK AO2 SLP114 T02780117 51015
Flight context
- LET6250
- CL60
- KBRO → KLAS
- 2026-08-13 21:42 UTC
- KLAS 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