Return to field — N334AX
KNTD · 212026-07-01 21:22 UTC· KNTD → KNTD· HUNTER AVIATION INTERNATIONAL INC· HUNT
N334AX (Hunter Aviation International) had departed KNTD on 2026-07-01. SkyMeter detected a return to field at Point Mugu Naval Air Station (Naval Base Ventura Co) (KNTD) on runway 21 at 21:22 UTC. Peak cruise altitude FL251, turnaround area near Coronado, US. Approach stability score: 76/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 0 kt wind, 11,265 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4189 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7265 2026-06-12 21:07Z – 2026-07-16 06:29Z SFC–400 ft
Manhattan Beach, CA
View FAA NOTAM → - HAZARDS6/9814 2026-06-29 14:00Z – 2026-07-04 02:00Z SFC–200 ft
LONG BEACH, CA, Monday, June 29, 2026 through Saturday, July 4, 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
- 25177 ft AGL at event
- 529 kt ground speed
- 0 fpm vertical
- Approach stability 76/100
- 0 kt wind
- 0 kt crosswind component
- 11,265 m visibility
- KNTD 181255Z AUTO 02003KT 7SM CLR 14/12 A3006 RMK AO2 SLP180 T01390122 PWINO CHINO S VISNO S $
Flight context
- N334AX
- Hunter Aviation International
- HUNT
- KNTD → KNTD
- 2026-07-01 21:22 UTC
- KNTD runway 21
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