Trainer
Steering an aircraft privately, making it speak, and starting an emergency.
These work for trainers only. On this server a trainer is anyone IVAO lists in its Training department, or anyone the operator has given trainer rights. Everyone else is told to write on the frequency instead, and nothing they wrote is flown.
Sit on a controller position of your own, one that does not get in the trainee's way, such as a neighbouring approach or centre sector. An observer position cannot write to aircraft.
| Command | Short | Pad signs | Pad digits | Meaning |
|---|---|---|---|---|
say <TEXT> | Trainers only, in the aircraft's private window: the aircraft says the rest of the line on the frequency of the controller who holds it | |||
emergency <KIND> [<VARIANT>] [in <MIN>] | Trainers only, in the aircraft's private window: start an emergency now, or after the given simulated minutes (1 to 60) | |||
emergency <KIND> [<VARIANT>] at <FIX> | Trainers only, in the aircraft's private window: start an emergency when the aircraft passes the fix | |||
emergency now | Trainers only: the next step of the running emergency happens now | |||
emergency pause | Trainers only: stop the emergency's clock; the aircraft keeps flying what it flies | |||
emergency resume | Trainers only: run the emergency's clock again | |||
emergency cancel | Trainers only: end the emergency | |||
emergency status | Trainers only: what is running, for how long, and what comes next | |||
emergency | Trainers only: list the emergency commands |
Steering an aircraft privately
Open a private chat with the aircraft and type the instruction as you would on the frequency. You can leave out the callsign, because the window already names the aircraft. The aircraft flies it and reads it back in the same window, so the trainee sees only what it does on the scope.
A line that starts with the callsign of a different aircraft on the server is refused, so a line
typed into the wrong window cannot steer the wrong aircraft. Server commands such as pause belong
in the chat with SERVER, not in an aircraft's window. While the simulation is paused, nothing is
flown and the aircraft tells you to type RESUME first.
Making an aircraft speak
Everything after say is the text, so nothing on that line is flown. The aircraft says the text
on the frequency of the controller who holds it, which is usually the
trainee's, not yours. You are told in the aircraft's window where it was said. If nobody holds the
aircraft, or the controller holding it has not set a frequency yet, nothing is said and you are told
why in the same window. If the aircraft has left the server meanwhile, the answer comes from SERVER
instead. If you type say on the frequency, it is refused and
you are pointed to the aircraft's window, since everybody on the frequency would read it first.
Starting an emergency
Type emergency and the kind in the aircraft's window, for example emergency comms. The
emergency then runs by itself. Before each step the trainee can see, the aircraft tells you in the
same window what comes next and when. You can bring a step forward, pause the emergency, resume it,
end it, or ask where it stands. Any trainer can steer any running emergency, and the aircraft
reports to the trainer who last started or steered it.
An emergency starts at once, after a number of simulated minutes with in, or when the aircraft
passes a fix with at. A paused simulation stops its clock too. emergency pause is not the
server's pause: it stops only the emergency's clock, and the aircraft keeps flying.
Every emergency command typed on the frequency is refused, privately, so the trainee never sees one. Each aircraft can have one emergency at a time.
What the aircraft does in each kind, and why, is in the Emergencies section.
To see every running emergency on the server, ask SERVER (.chat SERVER):
| Command | Meaning |
|---|---|
emergency list | Trainers only: every running emergency, one line per aircraft, grouped by destination |