GRZLY39 was operating from KSNS to KNKX on 2026-03-09. SkyMeter detected a go-around at Miramar Marine Corps Air Station - Mitscher Field (KNKX) on runway 24R at 20:10 UTC. Trace data at the event: 838 ft AGL, 120 kt GS. Approach stability score: 77/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 7 kt wind, 3 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)- SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft
Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 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 24R
- 838 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 77/100
- 7 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KNKX 221255Z 00000KT 10SM OVC029 20/16 A2992 RMK AO2 SLP125 T02000156
Flight context
- GRZLY39
- C560
- KSNS → KNKX
- 2026-03-09 20:10 UTC
- KNKX runway 24R
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