Include Spider X Blocks on/off events in the AFF data feed
Problem: The AFF (Aircraft Flight Following) data feed carries engine and takeoff/landing events from the Spider X digital flight log, but not blocks on/off events, so systems consuming the feed can't derive block times from it. Desired outcome: C...
See all aircraft tail numbers without zooming in when they overlap on the map
Problem: When several aircraft are close together on the map, their tail-number tags stack on top of each other, so users have to zoom right in to tell them apart. Desired outcome: Keep a wide view of the map and still read each aircraft's tail nu...
Show 'degraded latency' banner in Spidertxt messaging when known
The Spider Status view shows the 'tracking' health as a function of how many position reports are pending offload. Use this same metric to drive display of a banner when in Spidertxt message thread that shows "Communications delayed" so crew know ...
Per-user controls for concurrent sessions and aircraft view scope
Problem: Today there are no per-user controls for limiting how many simultaneous sessions a user can have, and visibility into aircraft data is largely all-or-nothing — admins can't restrict a user or group to only the current position of active a...
Deliver notifications in-app (mobile push and web) in addition to SMS and email
Problem: Flight event notifications are only delivered via SMS and email. Notifications aren't linked into the app and require app-switching to read. Desired outcome: Users can choose "in-app" as a notification delivery channel. On mobile this mea...
Having an additional "Time" field in the popup when clicking on an aircraft. Currently there is local (chosen) time, and UTC time, it would be useful to see the local time where the aircraft currently is flying as a third time field.
Reverse geocode 'unknown' flight log locations to show 'nearby' place references
In concept, it would add the following as a 'location' reference when Airport or Custom codes were not found: If geo.locality within threshold → use “<d> <bearing> of <locality>” Else if geo.route within 2 km → “near <route>...