NtoM is a concept of operations which pursues the
feasibility, from a human factors perspective, of having a single pilot/aircrew controlling
several remotely piloted aircraft systems at once in non-segregated airspace. To meet such
feasibility, this multitasking must be safe and not interfere with the job of the air
traffic controllers due to delays or errors associated with parallel piloting. To that end,
a set of measures at several levels is suggested, which includes workload prediction and
balance, pilot activity monitoring, and a special emphasis on interface usability and the
pilot’s situational awareness.
The concept relies greatly on the exploitation of the potential of Controller-Pilot Data
Link Communications (CPDLC), anticipating future widespread implementation and full use.
Some of these features could also be leveraged for the one-to-one pilot-aircraft scenario,
as they constitute extra safety measures, like an orderly handover procedure or the
management in the event of a detected pilot incapacitation or a breach of orders.
Example of flight assignations. The use of CPDLC is optional.
As a collateral benefit, it would allow for an optimization of the human resources of
the airline, providing a way to schedule or assign the flight or parts of it to the pilots
considering their particular skills to leverage, keep or train them.
Another key piece of the whole system is the implementation of the CPDLC display, designed
to provide a guided, quick and intuitive interface. It has been designed keeping in mind a
future, more complex and rich use of this technology, for which the current displays and
software menus fall short in usability, as these are prepared for the small set of messages
elements currently in use. On its own, the display could be a valuable tool for the
training of the CPDLC message set and procedures.
More info: mfas
1. Dynamic representation of the workload in the face of an speed change.
2. Dynamic representation of the workload in the face of a direct to
execution.
3. When the reply to some specific elements can be automated, the pilot is released
from that task.
4. Situations where the WILCO is considered implicit and automatically sent.
5. Representation of mixed dialogues.
6. Message composition.
7. Verbal composition to support background communications.
8. Examples of candidate events to be monitored.
9. Different reminders depending on the task and the urgency associated.
10. Procedure for the transfer of control.
