Ideas

The exported CSV from the Flight Explorer shall include ALL data including Altitude Terrain, AGL, AMSL Pitch, Roll and more.

Problem: The Fleet Manager admin pages (Aircraft & Settings, Locations Admin, Users & Permissions, etc.) currently work best on a desktop browser. Admins working in the field on a phone or tablet have a degraded experience for these tasks....

Problem: SOS cancellation today is only possible on Spider X — via the device's SOS button or a connected keypad. Not all customers have a keypad, can reach the device's install location, or have been trained on the cancel interaction in advance. ...

Problem: Operators flying in fire-affected regions cannot see active fire or smoke conditions inside Spidertracks and currently rely on external services during flight planning. Desired outcome: Pilots and dispatchers can view current fire and smo...

Wherever a mobile is paired with Spider or tags are used, we know persons onboard and can choose to filter results in the History tables to only show those relevant to the user.

Most of us use the Events as part of our SMS historical monitoring and mitigation through AHARS. This information should be listed in the events just like pitch or bank etc.

It would be easier and quicker than downloading the CSV data and opening it in a spreadsheet just to view a simple sum total, such as how many block hours in a selected date range.

Provide a manned (or AI) service that would receive and respond to SOS events appropriately, so that the customer does not have to fulfil this function. This includes escalation to emergency services as required and tracking all actions in the int...

We have people who need insight access but not necessarily admin access

Create an aggregate report showing volumes + counts, charted and mapped by day and aircraft. Enable export of raw data and reports to assist customers engaged in fire response to report through to their contractors as needed.