Unstable approach — LXJ267

LXJ267 (Flexjet) was inbound to KTRK on 2026-08-07. SkyMeter detected a low approach-stability score at Truckee Tahoe Airport (KTRK) on runway 20 at 00:44 UTC. Trace data at the event: 6975 ft AGL, 122 kt GS. Approach stability score: 60/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 6 kt wind, 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/8487 2026-07-25 01:02Z – 2026-08-08 04:00Z SFC–10,500 ft

  12NM NE SUSANVILLE, CA, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9393 2026-07-28 14:00Z – 2026-08-11 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9879 2026-07-29 14:00Z – 2026-08-11 04:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0406 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0407 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 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