Return to field — N328AX
KNTD2026-07-15 17:36 UTC· KNTD → KNTD· HUNTER AVIATION INTERNATIONAL INC· HUNT
N328AX (Hunter Aviation International) had departed KNTD on 2026-07-15. SkyMeter detected a return to field at Point Mugu Naval Air Station (Naval Base Ventura Co) (KNTD) at 17:36 UTC. Peak cruise altitude FL353, turnaround area near Los Osos, 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)- SECURITY6/4192 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4197 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
GOLETA, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7842 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Montecito, CA
View FAA NOTAM → - SECURITY6/7841 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft
Goleta, CA
View FAA NOTAM → - SECURITY6/7843 2026-07-03 16:07Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA
View FAA NOTAM → - SECURITY6/7847 2026-07-03 16:07Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA
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
- 35305 ft AGL at event
- 511 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 12,875 m visibility
- KNTD 170355Z 26004KT 8SM FEW036 18/16 A2999 RMK AO2 SLP158 T01830161 $
Flight context
- N328AX
- Hunter Aviation International
- HUNT
- KNTD → KNTD
- 2026-07-15 17:36 UTC
- KNTD
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