Mobile

Hello. Re. iOS Fleet Manager app. I can activate a Custom Layer in Map view, but when I switch to the tracking view, the layer is no longer visible and the layer button is no longer present, so I can’t add the layer in that view. Please add the ab...

We've had numerous issues stemming from the app automatically connecting to the last flown aircraft, particularly when the pilot is now in a different aircraft. The problem is most prevalent in the mornings when multiple pilots are starting at the...

Problem: Today only one device can be paired to a Spider, so a flight's Spidertxt thread is visible to a single crew member. Multi-pilot crews and medical/EMS teams operating from the same aircraft don't share visibility of inbound or outbound mes...

Being logged out every 6 months causes frustration as pilots have to log back in. It would be good to have the ability to choose own log out time - 3 months / 6 months or 1 year / Never.

Problem Ground staff at tour operations have no way to be automatically alerted when an aircraft is approaching on its return leg. They must watch the map or rely on someone at a desk to call them. Desired outcome Ground crew receive a push notifi...

Able to be set/edited by pilots via app Able to be acked by ops team Shows in Flying page, sorted by remaining time Expired SAR time triggers SOS response framework

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

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

Watch assignment, acceptance, transfers, check-in timers and acknowledgements.

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