Return to field — N765AT

KVNY · 16R

2026-03-24 15:30 UTC· KVNY KVNY· SAPPHIRE NO5 LLC· B722

N765AT (Sapphire NO5) had departed KVNY on 2026-03-24. SkyMeter detected a return to field at Van Nuys Airport (KVNY) on runway 16R at 15:30 UTC. Peak cruise altitude FL184, turnaround area near Lakeview, US. Approach stability score: 64/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 0 kt wind, 16,093 m visibility. 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 16R
  • 18455 ft AGL at event
  • 391 kt ground speed
  • 0 fpm vertical
  • Approach stability 64/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KVNY 211751Z 15005KT 10SM SCT023 BKN043 22/15 A2997 RMK AO2 SLP140 T02170150 10217 20189 51003 $

Flight context

  • N765AT
  • Sapphire NO5
  • B722
  • KVNY → KVNY
  • 2026-03-24 15:30 UTC
  • KVNY runway 16R

All events on this flight

Return to field 15:30:27 UTC · KVNY runway 16R · 18,455 ft AGL · 391 kt GS
Go-around 17:47:21 UTC · KCNO runway 08R · 959 ft AGL · 143 kt GS
Go-around 17:47:21 UTC · KCNO runway 08R · 959 ft AGL · 143 kt GS
Go-around 16:59:54 UTC · KVNY runway 34L · 879 ft AGL · 162 kt GS
Go-around 17:47:21 UTC · KVNY runway 34L · 959 ft AGL · 143 kt GS

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· KVNY