Unstable approach — TROY328
KNZY · 292026-07-03 02:15 UTC· KNZY → KNZY· US DEPARTMENT OF HOMELAND SECURITY, US CUSTOMS & BORDER PROTECTI· B350
TROY328 (US Department of Homeland Security) was operating from KNZY to KNZY on 2026-07-03. SkyMeter detected a low approach-stability score at North Island Naval Air Station-Halsey Field (KNZY) on runway 29 at 02:15 UTC. Trace data at the event: 1137 ft AGL, 128 kt GS. Approach stability score: 39/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 11 kt wind, 2 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4182 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4183 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4198 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4201 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4202 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4203 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, 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 → - SECURITY6/7820 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, CA
View FAA NOTAM → - SECURITY6/7821 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft
San Diego, 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
- Runway 29
- 1137 ft AGL at event
- 128 kt ground speed
- 0 fpm vertical
- Approach stability 39/100
- 11 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KNZY 162052Z 23010KT 10SM FEW038 25/14 A2997 RMK AO2 SLP149 T02500139 58014 $
Flight context
- TROY328
- US Department of Homeland Security
- B350
- KNZY → KNZY
- 2026-07-03 02:15 UTC
- KNZY runway 29
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