LXJ567 (Flexjet) was operating from KNUQ to KMRY on 2026-06-29. SkyMeter detected a go-around at Monterey Peninsula Airport (KMRY) on runway 28L at 03:09 UTC. Trace data at the event: 381 ft AGL, 119 kt GS, 0 fpm vertical. METAR at the time reported 7 kt wind, 7 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

    San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    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 28L
  • 381 ft AGL at event
  • 119 kt ground speed
  • 0 fpm vertical
  • 7 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • KMRY 171754Z 33005KT 10SM BKN044 19/11 A3014 RMK AO2 SLP218 T01940111 10194 20139 53011

Flight context

  • LXJ567
  • Flexjet
  • CL35
  • KNUQ → KMRY
  • 2026-06-29 03:09 UTC
  • KMRY runway 28L

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

SkyMeter · trace data observed via ADS-B· KMRY