Currently, any new pilot requests are inserted into the controllers flightstrip at the top of the list. When it’s busy, a tag can rapidly move down the list as new calls come in. If you are trying to tap a particular blinking tag to respond to an aircraft, you can get the wrong aircraft if the order changes just before your finger touches the screen.
Here’s a suggestion that would eliminate that issue, while preserving other desirable attributes of the flightstrip.
Let’s think of the flightstrip as consisting of two blocks, the top block is where new Blinking requests are inserted, and below them are tags that have been responded to. Here’s how to manage those two…
When a new request comes in from a pilot, that request would be inserted at the bottom of the current set of blinking flightstrip tags. When a request is answered by the controller, it is moved just below the last blinking tag, or to the top of the non blinking tags.
This has many desirable results…
- the oldest blinking tag is at the top of the list, and doesn’t move as new requests come in,
- the pilot that received the most recent controller command is at the top of the non blinking tags.
- the tag at the bottom of the entire list is still the oldest, which is handy when you want to take care of people waiting the longest on ground.
A picture is worth a thousand words…
There’s still only one flightstrip. (Reference the pic below)
New pilot requests (yellow in the pic) that have not been responded to, are sorted with the oldest at the top of the block.
Tags that have been responded to (white in the pic) are sorted with the oldest at the bottom. (Have to think about sorting this with the oldest at the top)