HSH-1006 - The 100 Nautical Mile Constraint as a Feature

Living Document Notice
Published 2026-09-14. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.

The 100 Nautical Mile Constraint as a Feature

Summary

Mainstream geospatial interfaces encourage infinite panning and global exploration. Web maps invite users to zoom continuously from an international flight corridor down to an individual runway taxiway, dragging viewport boundaries across continents. While technically impressive, unbounded viewports require heavy spatial indexing trees, continuous vector tile streaming, and aggressive client-side memory caching. More importantly, global maps detach observers from their immediate physical surroundings.

Hushwire adopts an intentional design constraint: a rigid, non-negotiable operational radius of 100 nautical miles (NM) centered around a single local origin. By bounding the observation window, the software achieves deterministic memory ceilings, eliminates vector tile overhead, and transforms the application from a generic global tracker into an authentic ambient observatory. This dispatch analyzes the computational advantages, spatial partitioning mechanics, and cognitive focus created by the 100 NM boundary.

The Architectural Weight of Unbounded Maps

Displaying global flight telemetry requires substantial software machinery. At any given moment, between 12,000 and 18,000 commercial and private aircraft occupy global airspace. Serving this dataset to a browser with pan-and-zoom functionality demands:

1. Hierarchical Spatial Indexing: R-trees, Quadtrees, or Geohash clusters must be constantly recalculated on both client and server to prevent rendering tens of thousands of off-screen DOM nodes or canvas sprites.
2. Dynamic Tile Streaming: As users pan across coordinates, the client must fetch, unpack, and decode Mapbox Vector Tiles (MVT) or raster imagery, consuming hundreds of megabytes of RAM.
3. Complex Viewport Math: Projection transformations (such as Web Mercator to screen pixels) must continuously re-project every contact during user pan gestures.

When deployed on a dedicated secondary monitor or a low-power dashboard device (such as a Raspberry Pi or thin client), unbounded mapping engines inevitably degrade:

Unbounded Global Viewport ──► Ingest 15,000 Aircraft ──► Quadtree Rebuild
                                                                  │
                                                       High CPU / GC Churn
                                                                  │
                                                                  ▼
Memory Leaks over 24h ◄── Vector Tile Fetch Churn ◄── Frame Drops & Stutter

The Mathematics of the 100 NM Bounding Circle

One nautical mile is standardized as exactly 1,852 meters. A circle with a 100 NM radius covers:

$R=100\times 1,852\text{ m}=185.2\text{ km}$

$\text{Area}=\pi R^2=\pi \times (185.2{)}^2\approx 107,756{\text{ km}}^2$

This geometric boundary holds distinct properties for aviation telemetry:

• Line-of-Sight Alignment: Due to the curvature of the Earth, a terrestrial receiver at sea level has a theoretical radio horizon of approximately 140 to 180 NM for aircraft at high altitude (35,000 feet). A 100 NM radius cleanly encapsulates the high-fidelity line-of-sight zone where terrestrial ADS-B receivers experience minimal signal degradation.
• Bounded Target Cardinality: Even within the world’s most congested terminal radar approach control areas (such as London, New York, or Tokyo), the maximum number of airborne targets within 100 NM rarely exceeds 180 to 250 aircraft during peak traffic hours.
• Deterministic Resource Envelope: Instead of handling unpredictable arrays of thousands of aircraft, Hushwire allocates a fixed-size TypedArray of 256 contact slots. Allocation is performed once at startup; runtime memory growth is zero.

Spatial Partitioning and Fast Radius Culling

To query only relevant targets without burning database CPU, the edge worker translates the origin coordinate and 100 NM radius into a fast bounding box pre-filter, followed by a precise Great Circle distance check:

$\Delta \varphi =\frac{100}{60}=1.6667^{\circ }$

$\Delta \lambda =\frac{100}{60\cdot \cos ({\varphi }_{origin})}$

export interface GeoPoint {
  lat: number;
  lon: number;
}
 
export function isWithinOperationalRange(origin: GeoPoint, target: GeoPoint, maxNm: number = 100): boolean {
  // 1. Fast bounding box rejection
  const dLatDeg = maxNm / 60.0;
  if (Math.abs(target.lat - origin.lat) > dLatDeg) {
    return false;
  }
 
  const radOriginLat = (origin.lat * Math.PI) / 180;
  const cosLat = Math.cos(radOriginLat);
  const dLonDeg = cosLat > 0.001 ? maxNm / (60.0 * cosLat) : maxNm / 60.0;
  
  if (Math.abs(target.lon - origin.lon) > dLonDeg) {
    return false;
  }
 
  // 2. Haversine calculation for spherical precision
  const dLat = ((target.lat - origin.lat) * Math.PI) / 180;
  const dLon = ((target.lon - origin.lon) * Math.PI) / 180;
  const lat1 = (origin.lat * Math.PI) / 180;
  const lat2 = (target.lat * Math.PI) / 180;
 
  const a = Math.sin(dLat / 2) * Math.sin(dLat / 2) +
            Math.cos(lat1) * Math.cos(lat2) *
            Math.sin(dLon / 2) * Math.sin(dLon / 2);
 
  const c = 2 * Math.atan2(Math.sqrt(a), Math.sqrt(1 - a));
  const distanceNm = (6371 * c) / 1.852; // Earth radius in km converted to NM
 
  return distanceNm <= maxNm;
}

By discarding out-of-bounds aircraft before JSON serialization at the edge, client payload sizes remain minimal and predictable regardless of global traffic conditions.

Comparative Architecture Matrix

Metric	Pan-and-Zoom Web Map	Hushwire 100 NM Bounded Scope
Spatial Scope	Global (0 to 20,000 km)	Fixed Circular Horizon (100 NM / 185 km)
Tile Engine	Mapbox GL / Leaflet / OpenLayers	Zero tiles; pure local Canvas polar coordinate grid
Active Target Count	5,000 to 18,000 objects	25 to 180 objects
Client Memory (RAM)	280 MB to 750 MB	22 MB to 34 MB steady state
Startup Time to First Paint	2.8 to 4.5 seconds	Under 150 milliseconds
24-Hour Memory Leak Risk	High (DOM recycling, tile caches)	None (fixed TypedArray ring buffer)

Cognitive Focus: The Sky Above Your Roof

Beyond computational efficiency, the 100 NM limit alters the human relationship with the tool. A global map invites passive browsing: following transoceanic flights across time zones or inspecting foreign airports. It functions as entertainment media.

In contrast, an instrument locked to a 100 NM radius grounds the user in their immediate physical geography:

1. Sensory Corroboration: When a low-altitude cargo transport rumbles overhead, the observer looks up at the screen and immediately identifies the aircraft, altitude, and heading. The digital display connects to physical sound and sight.
2. Pattern Recognition: Over weeks of unmonitored operation, the observer internalizes local approach corridors, regional weather diversions, and regular medical helicopter routes.
3. Absence of UI Fatigue: Because there are no zoom controls, panning gestures, or layer toggles to adjust, the instrument requires zero maintenance. It sits quietly on a desk, doing one thing reliably.

---

• Directus Target: hushwire
• Garden Source Reference: Operational Range Specs, Spatial Data Partitioning, MOC - Fleet Operations, MOC - Bosun PKM Tools