Return to field — N30VJ
KHND · 17L2026-07-19 00:00 UTC· KHND → KHND· JESSCONN CHARTERS LLC· SF50
N30VJ (Jessconn Charters) had departed KHND on 2026-07-19. SkyMeter detected a return to field at Henderson Executive Airport (KHND) on runway 17L at 00:00 UTC. Peak cruise altitude FL321, turnaround area near Enterprise, US. 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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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 →
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 17L
- 32138 ft AGL at event
- 326 kt ground speed
- 0 fpm vertical
- Approach stability 26/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- METAR KHND 152356Z 20019G24KT 10SM CLR 36/13 A2983 RMK AO2 PK WND 19026/2346 SLP086 T03560133 10367 20328 56022 $
Flight context
- N30VJ
- Jessconn Charters
- SF50
- KHND → KHND
- 2026-07-19 00:00 UTC
- KHND runway 17L
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