JPXWatch

Published route usage: Echo (preferred), November, Sierra — East Hampton Airport (KJPX)

Helicopter Ops
0
Track-Classified
0(0%)
Echo (Preferred)
Not measured
no track data in this period
Non-Standard
Not measured
requires track data

0 flights (0%) classified from ADS-B GPS track data by matching against published waypoints. The Echo and Non-Standard figures above are measured from those flights only. Track coverage is near-complete from August 2025 and essentially absent before it. Non-Standard classification requires GPS track data.

Route classifications are based on available track data where present. Where track data is unavailable, operations are assigned a default corridor rather than classified from observation. Corridor overlap is a descriptive geometry measure, not a legal finding of route noncompliance.

Learn more about our methodology

Route Map

Map shows 0 flights with ADS-B track data. See route distribution below for all 0 operations.

Route Distribution

Loading charts...

Routes classified by comparing ADS-B tracks to published waypoints (Echo, November, Sierra). Operations without track data are assigned Echo by default and are not classified from observation. Source: East Hampton Town Airport, "Helicopter Arrival and Departure Routes," Rev. 4, 03/23/2026.

Flight data and GPS ground tracks via FlightAware AeroAPI. Built and maintained by Marc Frons, as an independent civic data project.