Return to field — VIPER3

KNTD · 21

2026-05-28 21:28 UTC· KNTD → KNTD· HUNTER AVIATION INTERNATIONAL INC· HUNT

▶ Replay 📊 Analyse

VIPER3 (Hunter Aviation International) had departed KNTD on 2026-05-28. SkyMeter detected a return to field at Point Mugu Naval Air Station (Naval Base Ventura Co) (KNTD) on runway 21 at 21:28 UTC. Peak cruise altitude FL242, turnaround area near La Jolla, US. METAR at the time reported 0 kt wind, 12,875 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 →
  • HAZARDS6/2830 2026-05-25 15:45Z – 2026-06-11 16:00Z SFC–5,000 ft

    GARDEN GROVE, CA, Monday, May 25, 2026 through Thursday, June 11, 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.

Pilot review data

  • Runway 21
  • 24243 ft AGL at event
  • 473 kt ground speed
  • 0 fpm vertical
  • 0 kt wind
  • 0 kt crosswind component
  • 12,875 m visibility
  • KNTD 182355Z 26009KT 8SM FEW020 23/16 A2999 RMK AO2 SLP156 T02330161 10244 20233 56014 VISNO S $

Flight context

  • VIPER3
  • Hunter Aviation International
  • HUNT
  • KNTD → KNTD
  • 2026-05-28 21:28 UTC
  • KNTD runway 21

All events on this flight

Return to field 21:28:06 UTC · KNTD runway 21 · 24,243 ft AGL · 473 kt GS
Go-around 23:48:24 UTC · KNTD runway 27 · 527 ft AGL · 162 kt GS
Go-around 23:48:24 UTC · KNTD runway 27 · 527 ft AGL · 162 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· KNTD