$sql_bdd on the server $sql_server"; exit;} // SELECTION DE L'ENREGISTREMENT CONTENANT L'ID EN COURS $req=mysql_db_query($sql_bdd,"select * from user_data where Pers_Id=\"$connectedvid\" and Rating>0",$db_link) or die(mysql_error()); // SI L'ID N'EXISTE PAS if(mysql_num_rows($req)==0) { // REDIRECTION PAGE ERREUR header("Location:../members/person/login.php?XURL=$this_site"); exit; } // LIGNE FACULTATIVE : RECUPERATION DU PSEUDO $Req_Rating=mysql_result($req,0,"Rating"); if($Req_Rating<11) { header("Location:../noaccess.php"); exit; } ?> IVAO Supervisor Guidelines

Supervisor Guidelines


Supervisor Guidelines

Updated: 09/12/2004

This is an internal document for Supervisors

    Due to the increased numbers of users on the IVAO network, the following guidelines apply to all supervisors in order to ensure a fair and equal treatment of all the users. Bear in mind these are guidelines, and not fixed rules – use your judgement. This rating has been given to you out of trust, and must not be misused. This is a hobby, and the supervisor powers are to be used to prevent misuse and a prevention of other users being unable to use the service.

    We've got some cases of Supervisors doing a wrong use of his position, as a Supervisor killing a person cause he hadn't the ICAO code of the airport correctly written. Well, remember that you, ALWAYS, must be the MOST friendly user of IVAN. You're Supervisors, not policemen. Remember this. Don't kill a user cause you sent him a "Hello" message and he didn't reply; you must, at least, include in the message who're you, what are you doing, and if needed send 3 or 4 messages more before killing. Summary, we need friendly supervisors instead policemen. If you're flying, and concentrated in the flight, it's better you'll not opened IvAc to be connected as Supervisor if you haven't time to check a Heavy Weather landing. It has no sense a user will request your attention for HW and you'll say him you can't cause you're flying. If you're connected as Supervisor, you must, and if you can't, then don't connect. I know a lot of you do a fantastic work as Supervisors. This text is only to refresh knowlegments.

 

USE OF BROADCAST: The broadcast channel is used only for important messages related to the network. Here, you have the list of things you can/cannot announce in BroadCast.

Supervisors must:

 


Use of vulgar language or insulting other users.

  1. User should be contacted by chat and warned that further language of that type will not be tolerated, and will result in a removal from the network.
  2. If user continues to use such language, or directs an insult at another user or staff-member, the following message should be issued by chat: ‘You will be removed from the network for vulgar language – it is not welcome here'.
  3. The user should be reported to an Administrator (if possible) or killed. This must be reported to hq@ivao.org by e-mail immediately.
  4. If user reconnects, allow to continue using IVAO unless further language or insults are tendered. In this case, kill user immediately. Then, inform an Administrator with IVAO ID# immediately to recommend user is contacted, and banned if the situation cannot be rectified.


About Pilots

Unresponsive Pilots in uncontrolled areas ( Sandbag hours ):

  1. The Pilot should be contacted by chat and asked to respond. If he doesn't answer then contact him via Private message.

  2. If the Pilot failed to respond, by chat, after 15 minutes, and after you sent him at least 4 messages, issue the warning: ‘Sir, we have been unable to contact you, and we have therefore disconnected your connection in case the server was not dropping a dead connection. You are welcome to reconnect if you were online and then please contact me’

  3. The user should be reported to an Administrator (if possible) or killed. This must be reported to hq@ivao.org by e-mail immediately. If the user re-connects, they are welcome to continue their flight – and the above guidelines should be re-applied if contact is lost again

Pilots refusing to follow ATC instructions:

  1. User should be contacted on user’s frequency and asked to comply with ATC commands or give a reason for his inability. Explain that this is to allow the controller to enjoy the service, to prevent mid-air collisions, and to reflect reality.

  2. If pilot refuses, warn pilot by chat that if he can only fly within restricted airspace if he is willing to follow ATC directives, otherwise should fly in uncontrolled airspace or will be removed.

  3. If the user continues to refuse to fly by ATC directive, and the ATC’s directive is reasonable or necessary to prevent a disruption (or to follow procedures during heavy traffic), warn the user by chat he will be removed if he fails to comply. If the ATC is changing a flight-plan or forcing a user to comply with local procedures when traffic is light, ask the ATC by chat to compromise and allow the pilot to fly his wishes.

  4. If above conditions are satisfied, and user is risking other traffic or preventing the controller from carrying out his duties, then the user should be reported to an Administrator (if possible) or killed. Before killing, send a message stating: ‘You have been removed as your aircraft was not following ATC directives. If you wish to reconnect, you may providing you fly by ATC directives or in uncontrolled airspace’. This must be reported to hq@ivao.org by e-mail immediately.

Failure to respond to Ait Traffic Controller:

  1. Supervisor should contact the aircraft by the Guard Frequency, and call the aircraft to user’s frequency or to squawk 7600 if unable: ‘contact 132.600 now, or squawk 7600 if unable. I'm an IVAO supervisor’.

  2. If aircraft fails to acknowledge within 45 seconds, supervisor should call the aircraft using the chat facility, warning the user that failure to contact ATC while flying in controlled airspace degrades the service, and enjoyment for other users.

  3. If aircraft continues to fly without making any contact, or declaring any Lost Communications problems, the supervisor must give a notice by chat that ‘You will be disconnected as you are flying in controlled airspace without permission. If you are experiencing communications problems, or were away from the computer, you are welcome to reconnect’.

  4. After waiting a further 30 seconds, the user should be reported to an Administrator (if possible) or killed. This must be reported to hq@ivao.org by e-mail immediately.

Incompetent pilots:

  1. Incompetent pilots are not to killed under any circumstances. The ATC should be advised to explain to the pilot the stages, simply, and make commands clear, except if he doesn't answer calls and can create conflicts with other traffics. 

  2. If the pilot is flying in a controlled area without permission, the guidelines above apply.

  3. If pilot is new, and controller is busy, you must to assist the pilot with basic explanation and recommend that he flies elsewhere (and give a location, if possible) to become familiar with the network if the ATC requested help to you.


About ATCs

ATC in scheduled position:

  1. If the scheduled user arrives and an ATC is already in his position, and the controller is not more than fifteen (15) minutes late, ask the controller politely to surrender the scheduled position, and explain the reason. Suggest an alternative position.

  2. If the controller refuses, ask the scheduled controller if he would object to taking a different position.

  3. If the scheduled controller insists he wants the position he has scheduled, inform the controller by chat he must surrender the position else will be removed.

  4. After waiting a further 20 seconds, the user should be reported to an Administrator (if possible) or killed. This must be reported to hq@ivao.org by e-mail immediately. Obviously, the user should be allowed to reconnect in an alternative position.

Unresponsive Air Traffic Controller:

  1. The ATC should be contacted by chat and asked to respond. If there are waiting aircraft, user has been continually slow to reply, or an event is in progress, user should be given at least forty seconds to respond; otherwise one and a half minutes or longer should be given. If necessary, take control of the user’s frequency to avert any incidents whilst explaining situation to ATC.

  2. If the ATC failed to respond, by chat issue the warning: ‘Sir, we have been unable to contact you, and we have therefore disconnected your connection in case the server was not dropping a dead connection. You are welcome to reconnect if you were online and then please contact me’

  3. The user should be reported to an Administrator (if possible) or killed. This must be reported to hq@ivao.org by e-mail immediately. If the user re-connects, they are welcome to continue to control – and the above guidelines should be re-applied if contact is lost again.

 

Incompetent Air Traffic Controller:

Note: This is the hardest situation to deal with. These guidelines are only to be applied if the controller is completely unable to provide basic ATC, and are not to be used if the controller is not following local procedures (a chat recommending training is sensible here). These guidelines are not to be used in order to replace a less able ATC, with a more able ATC – only if the ATC is preventing an event from proceeding, or other controllers and aircraft from using the system.

  1. User should be contacted by chat and a conversation sought. Ask the user if (s)he is willing to take a less demanding position, and recommend training. Re-assure the user that all controllers start with TWR or DEP, and that – with training – they will easily be able to take higher positions. Also, if traffic levels are high, explain these are the exact difficulties real controllers have.

  2. If the user does not reply in a reasonable time-scale (two minutes), warn the user that they should reply, as they should start learning in a simpler position, and that – if they do not reply – they will have to be removed. If the user refuses to move, and are unable to provide even the most basic ATC, warn the user that they are not ready for the position and should move to learn in an easier position. If necessary, take control of the user’s frequency to avert any incidents whilst explaining situation to ATC.

  3. If the user continues to not reply, or still refuses to move, contact an Administrator. If no Administrator is available, warn one final time: ‘Sir, you must move to a less demanding position until you have more experience’. Issue a kill if no response in one minute. This must be reported to hq@ivao.org by e-mail immediately

Exceptions:

  1. Failure to reply on text: in this case, warn user that a pilot has contacted on text, and only follow above procedures if user continues to ignore given pilot on text. Warn user that they may be banned from using voice or the network if they continue.

  2. Failure to reply on voice or voice control inaudible/not understandable: in this case, warn user that voice should not be provided if controller is not to a standard where they can handle the additional load place by voice or that their voice set-up is inaudible. This is not an offence for killing