New: Flight Ops Messaging (25 Feb)
Flight Operations Messaging introduces structured, aircraft-centric communication between flight crew and operations teams. Messages are grouped by aircraft and persist with it, supporting coordinated flight following and operational oversight. The feature is available in both web and mobile applications.
This feature is rolling out to all customers through February and is included in all core subscriptions.
What's New
Crew members are automatically associated with the aircraft conversation based on flight activity. Crew member identity and connection status is visible to the Ops Team.
Clear conversation orientation is achieved through message attribution and layout difference between crew and ground support messages
Channel mute and unmute supports flight follower roster and handover workflows
Message history is retained for audit and operational review
Custom Quick Message Templates
Operations teams can now create and use predefined quick messages to:
- Standardise common communications
- Improve response speed
- Reduce repetitive typing
Up to 8 messages can be defined per Organisation for Crew, and up to 8 for the Ops Team.
To learn more about this new feature, and for assistance with getting setup, see our KB page here.
Bug Fixes and Minor Improvements
-
Flight Ops messaging
Status of crew connection is now shown in both Flying page and Spidertxt conversation panes. (5th Mar)
Status include awaiting connection, connected (with name), connection disruption, and disconnected (time last seen). (5th Mar)
Muted channel unread message bubbles are now gray instead of blue. (13th Mar)
-
Flying page
Fixed navigation menu rendering artifact (affected only Safari) (13th Jan)
-
Notifications
Fixed RoC/RoD notifications to specify rate in feet per minute (31st Mar)
Comments
0 comments
Article is closed for comments.