Ideas

On occasion the icon will blend in with the map and be difficult to see

Problem: Pilots forget to turn Watch on before flying or off after landing, causing missed SAR coverage and false-positive SOS alerts that disrupt operations. Desired outcome: Pilots receive timely push notifications prompting Watch activation at ...

We would like to have an automatic way to send the flight (KML and CSV) to the pilot/student, when the flight is completed.

Pilots keep hitting SOS accidentally, could Spidertracks consider moving this away from the WATCH button perhaps underneath mark 4, less of a chance of pilots hitting the wrong one.

For workflow and productivity, it would be good to have the keypad App option in the bottom menu. Our pilots are using Spidertxt, the keypad option and flying a plane and don't need to be digging through menus.

Problem: On the mobile app Home page, all users — including pilots and, where they have access, clients — can see fleet-wide flight activity (hours and distance for every aircraft). In larger operations, exposing these operational totals to everyo...

Problem: On Flight History, aircraft selection currently sits in the table header, where it reads as a table utility rather than the primary way to choose which flights are shown. Desired outcome: Make aircraft filtering as discoverable and consis...

Problem: The current Admin/Member model is too coarse. Organisations cannot tailor what individual users or groups can see and do — for example, decoupling Insights access from full Admin rights, restricting contract pilots from operational dashbo...

Problem: The navigation assistant only supports simple point-to-point routes, which limits its usefulness for helicopter operations (frequent short hops to random sites) and fixed-wing ops requiring flight vectoring within corridors. Desired outco...