Unstable approach — N797ML
KNTD · 272026-07-27 23:47 UTC· KIDA → KNTD· SPITZER HELICOPTER LLC· BE20
N797ML (Spitzer Helicopter) was operating from KIDA to KNTD on 2026-07-27. SkyMeter detected a low approach-stability score at Point Mugu Naval Air Station (Naval Base Ventura Co) (KNTD) on runway 27 at 23:47 UTC. Trace data at the event: 1118 ft AGL, 143 kt GS. Approach stability score: 26/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, 3 kt crosswind component, 11,265 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)- HAZARDS6/6100 2026-07-16 14:00Z – 2026-07-30 04:00Z SFC–10,000 ft
41NM SE BURNS, OR, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/6221 2026-07-16 17:58Z – 2026-07-30 04:00Z SFC–12,000 ft
9NM SE DUGWAY, UT, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/6358 2026-07-17 13:00Z – 2026-07-31 04:00Z SFC–12,000 ft
9NM SE DUGWAY, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6359 2026-07-17 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft
5NM E BEAVER, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6569 2026-07-18 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft
5NM E BEAVER, UT, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/7909 2026-07-22 18:11Z – 2026-08-08 04:00Z SFC–12,500 ft
20NM N INDEPENDENCE, CA, Wednesday, July 22, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8323 2026-07-23 23:15Z – 2026-08-05 05:00Z SFC–10,000 ft
95NM SE BURNS, OR, Thursday, July 23, 2026 through Wednesday, August 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/8435 2026-07-24 18:00Z – 2026-08-07 04:00Z SFC–10,000 ft
44NM SW BURNS, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC
View FAA NOTAM → - HAZARDS6/8460 2026-07-24 18:30Z – 2026-08-08 05:00Z SFC–10,000 ft
95NM SE BURNS, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8481 2026-07-24 22:00Z – 2026-08-08 05:00Z SFC–11,500 ft
57NM SE BURNS, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8546 2026-07-25 17:15Z – 2026-08-09 05:00Z SFC–10,000 ft
10NM NW BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8552 2026-07-25 17:30Z – 2026-08-09 04:00Z SFC–10,000 ft
95NM SE BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8553 2026-07-25 17:30Z – 2026-08-09 04:00Z SFC–11,500 ft
44NM SE BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8556 2026-07-25 19:00Z – 2026-08-09 05:00Z SFC–10,000 ft
10NM NW BURNS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8654 2026-07-26 16:00Z – 2026-08-10 05:00Z SFC–11,500 ft
36NM E BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8761 2026-07-26 16:30Z – 2026-08-09 05:00Z SFC–11,500 ft
50NM SE BURNS, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8762 2026-07-26 17:00Z – 2026-08-10 05:00Z SFC–10,000 ft
95NM SE BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8784 2026-07-26 18:45Z – 2026-08-10 05:00Z SFC–10,000 ft
44NM SW BURNS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8875 2026-07-27 14:00Z – 2026-08-04 05:00Z SFC–13,000 ft
60NM NE FALLON, NV, Monday, July 27, 2026 through Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/8928 2026-07-27 14:00Z – 2026-08-05 04:00Z SFC–12,500 ft
14NM NE AUSTIN, NV, Monday, July 27, 2026 through Wednesday, August 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9354 2026-07-27 22:15Z – 2026-08-10 05:00Z SFC–10,000 ft
26NM S BURNS, OR, Monday, July 27, 2026 through Monday, August 10, 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 27
- 1118 ft AGL at event
- 143 kt ground speed
- 0 fpm vertical
- Approach stability 26/100
- 11 kt wind
- 3 kt crosswind component
- 11,265 m visibility
- KNTD 162355Z 26010KT 7SM BKN040 23/16 A2995 RMK AO2 SLP143 T02330161 10250 20228 56009 $
Flight context
- N797ML
- Spitzer Helicopter
- BE20
- KIDA → KNTD
- 2026-07-27 23:47 UTC
- KNTD runway 27
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