Unstable approach — TROY314
KNZY · 292026-07-23 17:50 UTC· KCXO → KNZY· DEPARTMENT OF HOMELAND SECURITY· B350
TROY314 (Department of Homeland Security) was operating from KCXO to KNZY on 2026-07-23. SkyMeter detected a low approach-stability score at North Island Naval Air Station-Halsey Field (KNZY) on runway 29 at 17:50 UTC. Trace data at the event: 1138 ft AGL, 152 kt GS. Approach stability score: 44/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 8 kt wind, 3 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/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft
Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft
Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft
SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/2652 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - HAZARDS6/6155 2026-07-16 16:00Z – 2026-07-23 23:00Z SFC–1,500 ft
0NM W INGRAM, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6156 2026-07-16 16:09Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM SE KERRVILLE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6217 2026-07-16 18:17Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM W INGRAM, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6218 2026-07-16 18:17Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM SE KERRVILLE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6186 2026-07-17 13:00Z – 2026-07-30 03:00Z SFC–11,000 ft
21NM NE DOUGLAS, AZ, Friday, July 17, 2026 through Thursday, July 30, 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 29
- 1138 ft AGL at event
- 152 kt ground speed
- 0 fpm vertical
- Approach stability 44/100
- 8 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KNZY 162252Z 26010KT 10SM FEW020 24/16 A2995 RMK AO2 SLP142 T02390156 $
Flight context
- TROY314
- Department of Homeland Security
- B350
- KCXO → KNZY
- 2026-07-23 17:50 UTC
- KNZY runway 29
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