Go-around — N765AT
KTRM · 302026-03-23 17:12 UTC· KVNY → KTRM· SAPPHIRE NO5 LLC· B722
N765AT (Sapphire NO5) was operating from KVNY to KTRM on 2026-03-23. SkyMeter detected a go-around at Jacqueline Cochran Regional Airport (KTRM) on runway 30 at 17:12 UTC. Trace data at the event: 810 ft AGL, 189 kt GS. Approach stability score: 62/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, 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 30
- 810 ft AGL at event
- 189 kt ground speed
- 0 fpm vertical
- Approach stability 62/100
- 6 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KTRM 211752Z AUTO 31009KT 10SM CLR 32/13 A2979 RMK AO2 SLP091 60000 T03170133 10317 20250 58002
Flight context
- N765AT
- Sapphire NO5
- B722
- KVNY → KTRM
- 2026-03-23 17:12 UTC
- KTRM runway 30
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