Regulations & Procedures

1. All Takeoffs will adhere to the following format :
   /advert [ATC | <Auth Codes> | this is <Ship Name | Callsign>] Requesting take off from UHB - Reason - <Give Reason>.
   Example, Jedi Master Paladin, flying a LAAT/i aircraft from Hangar A, for training, will request TO using the following format and their Auth Codes of “1102E” and their callsign of “Praetorian” They will say: "/advert [ATC | 1102E | this is LAAT/i | “Praetorian” requesting TO from UHA. Reason : Training"

2. A landing request is similar to a take off request in format with the only difference being that a reason for landing is not required to be appended into the landing request: /advert [ATC | <Auth Codes> | <Ship Name | Callsign>] Requesting landing in UHB. 

3. Take-Off (TO) and Landings are only granted to those pilots with valid flight Authorization Codes (Auth Codes), and a valid callsign (CS), both of which will be provided by Pilot Lead+, command for all Clone Battalions and Custom Characters, or by designated Jedi, giving Jedi other Jedi their Flight Certifications. 

4. General TO and Landing requests when ATC is active, can be accepted by Shock Troopers SGT+, 5th Fleet, Jedi Officer  Medical Personnel 1LT+, High Command, or Ground Command. 

5. ATC is considered inactive only if no less than THREE TO and Landings requests to ATC with a minimum of ONE minute between each request has already been submitted using the previous format in /advert. In the case that these conditions are satisfied, a pilot may take off after informing other Republic personnel using the following format : “/advert [Auth Code] This is [Ship Type] [CS], taking off from [Location]”

6. A properly certified pilot will always notify Air Traffic Control (ATC) when taking off by using /advert regardless of your rank. This applies even to High Command, and failure to do so may result in your craft being shot down. Multiple failures will result in pilot certifications being either suspended or completely removed from the offending personnel. 

7. All Auth Codes and CS’s must be submitted as soon as possible, otherwise they will not be logged into the Republic Databases. Otherwise all TO & Landings requests for the craft will be DENIED.

8. Callsigns and Auth Codes must be roleplay friendly. Anything “mingey” will not be tolerated. EX: 420-XD, 911, Bigweiniemeanie, PunnaniSlayer, etc. Failure to adhere to this will result in an immediate revocation of flight certification, and a minimum of a 3 month blacklist from flying, put into an unappealable state.

9. Auth Codes are assigned by Senior Pilot+ or Jedi Personnel in accordance with the procedure outlined in Auth Codes.

EXCEPTIONS TO TAKEOFF RULES:

1. SCRAMBLE - Only the highest Base Ops/Aviation Authority may issue a SCRAMBLE order, which is an order for all pilot certified personnel to get into the airspace, and start attacking all enemy personnel either in the air or on the ground. Pilots do not need to request any TO, and can simply initiate TO and begin engaging the enemy at will.

2. Pre-Authorized - Pre-Authorized or more commonly, Pre-Authorized, means that a specific portion of flight is Pre-Authorized. A proper Pre-Auth order will specify what exactly is Pre-Auth, for example : TO is Pre-Auth, LDNG is Pre-Auth, or TO and LDNG are Pre-Auth. When a proper Pre-Auth is ordered, a Pilot is not required to wait for approval, but must STILL send their TO intent by following the same protocols as one would follow if ATC is inactive.

Selecting your Authorization Code  is Simple: The Start of your Authorization Code will represent your battalion and are shown bellow, The end of your call sign will be numbers (XX) selected by the Trainee and approved by their Trainer.
EX: 

Battalions Callsign Letters: 

High Command = HC10XX

RSB = RSB-XX

Jedi = JO30XX

104th = WP40XX

212th = AB50XX

21st = EC60XX

501st = CL70XX

41st = GR80XX

Shock = SB99XX

Certified Pilots = CRPTXX
CC = CC00XX

Callsigns are nicknames selected by trainees once passing training this is a one to two worded nickname that isn't anything mingy or cringe-like approved by their Trainer. 

There are two types of aircraft in the Frostbite Gaming (FBG) server. There are those that utilise the LFS system, and those that utilise the LVS system. Care must be given to understanding the difference between both systems, and understanding the way both handle flight operations. 

The standard and “upgraded” version of flight operations for FBG is generally considered to be the LVS system, which makes greater use of a pilot’s keyboard rather than their mouse.  

LVS aircraft are capable of maintaining their height in Vertical Take-Off or Landing (VTOL) and are capable of fully adjusting their yaw without affecting their position, provided that a pilot does not adjust their roll or pitch. 

LFS airframes, however, are considerably different from LVS airframes. LFS airframes are not capable of holding a stationary VTOL position, and WILL move along with the pilot’s mouse, adjusting their yaw at the very tip of the aircraft, leading their tail end to be a hazard for any surrounding personnel.

At the rank of Pilot, you are eligible to be selected to join a squadron. Squadrons are named and  handpicked by their Leaders. Fly Valiantly in the sky and prove your worth to fly with the 3rd's Elite Pilots. Reach out to a Senior Pilot+ if you are interested in being recruited to a squadron.

Once at the rank Senior Pilot equivalence, you will be able to to be certified to give out certs and tryouts to pilots and non-pilots of the proper rank.
To get Certified, you must get a Pilot Lead+, they will go over a tryout with you and then you will do a mock tryout. Once done the Pilot Lead+ will decide if you passed or not.