Unstable approach — N361DD
KHND · 17R2026-06-15 14:40 UTC· KERV → KHND· WECO WEST LLC· F900
N361DD (Weco West) was operating from KERV to KHND on 2026-06-15. SkyMeter detected a low approach-stability score at Henderson Executive Airport (KHND) on runway 17R at 14:40 UTC. Trace data at the event: 3586 ft AGL, 138 kt GS. Approach stability score: 45/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 2 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/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft
CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local
View FAA NOTAM → - 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/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/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z
MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/5756 2026-06-05 14:00Z – 2026-06-19 04:00Z SFC–11,500 ft
3NM E NOGALES, AZ, Friday, June 5, 2026 through Friday, June 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/6780 2026-06-10 13:00Z – 2026-06-22 04:00Z SFC–10,000 ft
14NM E FLAGSTAFF, AZ, Wednesday, June 10, 2026 through Monday, June 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/7863 2026-06-12 14:00Z – 2026-06-24 05:00Z SFC–14,000 ft
80NM N SILVER CITY, NM, Friday, June 12, 2026 through Wednesday, June 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/7894 2026-06-12 14:43Z – 2026-06-25 04:00Z SFC–14,000 ft
80NM N SILVER CITY, NM, Friday, June 12, 2026 through Thursday, June 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/8083 2026-06-13 17:14Z – 2026-06-27 05:00Z SFC–11,000 ft
10NM E TUCSON, AZ, Saturday, June 13, 2026 through Saturday, June 27, 2026 UTC
View FAA NOTAM → - HAZARDS6/8208 2026-06-14 13:47Z – 2026-06-27 05:00Z SFC–13,000 ft
38NM NE DOUGLAS, AZ, Sunday, June 14, 2026 through Saturday, June 27, 2026 UTC
View FAA NOTAM → - HAZARDS6/8228 2026-06-15 14:00Z – 2026-06-28 03:00Z SFC–13,000 ft
38NM NE DOUGLAS, AZ, Monday, June 15, 2026 through Sunday, June 28, 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 17R
- 3586 ft AGL at event
- 138 kt ground speed
- 0 fpm vertical
- Approach stability 45/100
- 2 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- METAR KHND 302356Z 00000KT 10SM CLR 32/01 A2982 RMK AO2 SLP088 T03220006 10328 20283 56006 $
Flight context
- N361DD
- Weco West
- F900
- KERV → KHND
- 2026-06-15 14:40 UTC
- KHND runway 17R
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