Core

Please make it possible to delete Spidertext messages.

Our company uses contract agents to turn our aircraft at destinations that are small and remote all over the State of Alaska. Some days are very busy, and we often run extra flights that are not scheduled. This sometimes can cause Dispatch to forg...

Current Tracks Download only has a capability of 2500 lines or tracks. For large aircraft fleet like ours, this only gets us 5-6 months worth of data/Flight History. This should be increased to 10,000 Tracks/Lines of Data or at the very least 5000...

Would be very useful to us, and I would think other large fleets accounts, to be able to have a column in reporting that identifies Fixed Wing vs Rotary Wing, specifically when we are looking at things like flight hours.

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>...

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 ...

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...

Direction markers, such as barbs, should be on each aircraft track. This provides situational awareness of the direction of flight when viewing assets on the map.

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.

FDI map on the Map Views would be extremely helpful for firefighting operators. We currently use Windy for this.