Merge pull request #672 from rah1993/22.7

24.3 Release to Staging

atc-guide/index.md

@@ -9,7 +9,7 @@ meta: Learn how to get the most out of Infinite Flight with our online documenta
 
 
 
-## Guide Version: 24.2.0
+## Guide Version: 24.3.0
 
 
 

atc-manual/1.-introduction/1.1-overview.md

@@ -27,7 +27,7 @@ Should
 
 ### 1.1.2   
 
-The [Infinite Flight User Guide](/guide), [IFC Forum](https://community.infiniteflight.com/) and [FAA 7110.65](https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.current/documentnumber/7110.65) are additional tools that Controllers **should**{.red} utilize. In addition, a Controller directory, stats and the home of recruitment & training can all be found at [https://www.if-atc.com](https://www.if-atc.com).
+The [Infinite Flight User Guide](/guide), [IFC Forum](https://community.infiniteflight.com/) and [FAA 7110.65](https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.current/documentnumber/7110.65) are additional tools that Controllers **should**{.red} utilize.
 
 
 

atc-manual/1a.-administration/1a.1-discord-communication.md

@@ -38,15 +38,14 @@ Discord is a messenger app for teams to make work simpler, more pleasant and mor
 | #events                | The Events briefing room channel may be used to coordinate official and unofficial events such as FF, GA Day and streams |
 | #flights               | This channel is used for Controllers to coordinate group flights together. All coordination **should**{.red} remain in this channel |
 | #help-request          | If Controllers require support that cannot be found elsewhere, they can "raise" a ticket in this channel by reacting to the relevant role *(for further guidance see [1A.2.4](/guide/atc-manual/1a.-administration/1a.2-discord-rules#1a.2.4) below)* |
-| #ifatceg               | This channel contains news, tips and more brought to you by the IFATC Education Group |
+| #important-info        | Useful links as well as the Terms & Conditions that **must**{.red} be accepted by "reacting" before access is granted to the rest of the server |
 | #infinite-flight-rules | Highlights where to find the rules of the IFATC Discord server |
 | #offtopic              | This is a channel to discuss things unrelated to IFATC or Infinite Flight. All conversations **should**{.red} remain appropriate. *#offtopic* is a privilege and all members are subject to removal at any time if misused. This is for active members only |
 | #readonly              | Day to day posts (such as housekeeping and event specific procedures) to be made in this channel by the ATC Manager, Staff and Moderators only |
 | #role-assignments      | Within this channel is a "notification opt in" menu - Controllers can react with the corresponding emoji to opt in and when the mentioned phrase is used, the Controller will receive a notification. Controllers that use the mentioned phrase **must**{.red} only use it when necessary to avoid spamming other Controllers *(see [1A.3.1](/guide/atc-manual/1a.-administration/1a.3-controller-rules#1a.3.1) below)* |
 | #screenshots           | This is a place to share Infinite Flight screenshots (in moderation). No other simulator, games, or off-topic content **must**{.red} be shared and all screenshots **should**{.red} be of a high quality |
 | #social-media          | Automated official Infinite Flight social media updates. Controllers **must not**{.red} reply to any material posted in this channel so that all Controllers can be reached effectively |
 | #training-time         | Trainers will post in this channel when they require pilots to join in for training sessions *(see [7.1.5](/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.5) below)* |
-| #training-time[1-3]    | All training session coordination to take place in the designated channel as directed by the Trainer (no more than one training session per channel **must**{.red} be used at any one time) |
 
 
 
@@ -68,30 +67,7 @@ Discord is a messenger app for teams to make work simpler, more pleasant and mor
 
 ### 1A.1.3
 
-Below are some of the commands that can be used in the *#botcommands* channel:
-
-
-
-| Commands              | Purpose                                                      |
-| --------------------- | ------------------------------------------------------------ |
-| /atis[icao]           | Shows current ATIS message for that particular airport       |
-| /atc                  | Shows all open frequencies                                   |
-| .brief[icao]          | Generates an airport briefing including weather, general info, and charts |
-| !commands             | Provides a list of all available commands that can be used   |
-| .charts[icao]         | Gives you the latest charts of the chosen airport            |
-| !feedbackstatus       | Check the status of any feedback provided for the ATC Manual |
-| /find [name]          | Find a controller by real name or IFC username               |
-| /find [search phrase] | This can be used to find a member of IFATC within Discord    |
-| /gmt                  | Provides the current (local) time in GMT                     |
-| .info[icao]           | Gives you general information about the chosen airport       |
-| !lightaircraft        | Lists the "light" aircraft within Infinite Flight            |
-| !manual               | Generates a link to the latest version of the ATC Manual     |
-| !manualfeedback       | Generates a link to the Feedback Form for the ATC Manual     |
-| .metar[icao]          | Gives you the live METAR of the chosen airport               |
-| /mystats              | Search for your IFATC statistics                             |
-| /reference            | Provides quick IFATC references, rules and a link to the latest version of the ATC Manual |
-| /schedule             | Shows a list of scheduled training/testing sessions in the next 48 hours |
-| .taf[icao]            | Gives you the TAF of the chosen airport                      |
+By typing "/" into the Discord message bar, a list of commands will be generated that can be used for various functions. 
 
 
 

atc-manual/1a.-administration/1a.2-discord-rules.md

@@ -20,7 +20,7 @@ Tip
 
 ### 1A.2.1
 
-- All Controllers **must**{.red} [link](/guide/getting-started-guide/home-user-interface/user-profile#linking-community-forum-account) their Community Forum Account **BEFORE** controlling
+- All Controllers **must**{.red} link their [Community Forum](/guide/getting-started-guide/home-user-interface/user-profile#linking-community-forum-account) and [Discord](/guide/getting-started-guide/home-user-interface/user-profile#linking-a-discord-account) accounts **BEFORE** controlling
 - Controllers **must**{.red} ensure that their Discord Nickname is either the same as their IFC Username or real name
 - Controllers **must not**{.red} share any IFATC material or conversations (including audio) contained within the IFATC Discord externally (unless prior approval has been granted)
 - Controllers **must**{.red} be respectful to other users and practice common courtesies

atc-manual/1a.-administration/1a.3-controller-rules.md

@@ -14,7 +14,9 @@ auth: ifatc
 
 - All Controllers **must**{.red} announce in *#controllers* when opening/closing any frequency (including which facilities, such as Ground and Tower) on the Expert Server. When closing, a **MINIMUM** of 5 minutes warning and the last ATIS letter used **must**{.red} be provided. Use of abbreviations in place of the full facility names is acceptable *(see [1A.1.2](/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.2) above)*
 - Controllers are expected to show common courtesy to other Controllers by sharing where possible, opening frequencies that promote traffic between airports, and opening before announcing in *#controllers*
-- Opening frequencies is on a first come, first serve basis within *#controllers*. Therefore Controllers **must not**{.red} reserve frequencies privately or not open in anticipation of a particular frequency becoming available. This does not apply to certain events where frequency allocation may be authorized
+
+- Opening frequencies is on a first come, first serve basis within *#controllers*. Therefore Controllers **must not**{.red} reserve frequencies privately or not open in anticipation of a particular frequency becoming available. Controllers may commit to specific frequencies/positions for community events and **should**{.red} be afforded the opportunity to staff those at the event start time by fellow controllers
+
 - Controllers **should**{.red} avoid staffing or providing service to airports which do not have ramp spawns points for aircraft
 - Controllers that utilize the *@Tower Relief* and *@Radar Relief* reaction roles **must**{.red} only use these once, and **must**{.red} include the airport and time they are closing
 - Controllers that utilize the *@split* reaction role **must**{.red} only use it once, and **must**{.red} include the airport. It is recommended to use this prior to opening

atc-manual/1a.-administration/1a.5-activity-requirements.md

@@ -40,11 +40,14 @@ Minimum and maximum controlling times are enforced to ensure that pilots receive
 
 
 
-| Airport              | Minimum Time | Maximum Time |
-| -------------------- | ------------ | ------------ |
-| Class Charlie/Delta  | 30 minutes   | 12 hours     |
-| Class Bravo          | 1 hour       | 12 hours     |
-| All Radar Facilities | 1 hour       | 12 hours     |
+| Rank        | Minimum Time | Maximum Time |
+| ----------- | ------------ | ------------ |
+| Apprentice  | 30 minutes   | 12 hours     |
+| Specialist* | 1 hour       | 12 hours     |
+| Officer*    | 1 hour       | 12 hours     |
+| Supervisor  | 1 hour       | 12 hours     |
+
+**This includes Controllers currently in the Specialist/Officer Check Ride phase (see [1A.7.1](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.1) below)*
 
 
 

atc-manual/1a.-administration/1a.6-rank-structure.md

@@ -75,7 +75,7 @@ Before commencement of training for the rank of Officer, the following requireme
 
 - Minimum of 60 days at the rank of Specialist
 - Minimum of 2000 all-time operations
-- Attend a minimum of 10 training sessions per 30 days in the *#training-time[1-3]* Discord channels (this is counted with the honor system and members are expected to track their own attendance)
+- Attend a minimum of 10 training sessions per 30 days in the *#training* Discord channel (this is counted with the honor system and members are expected to track their own attendance)
 - Maintain an active controlling record* over the previous 30 days to ensure proficiency (this will be determined by the Recruiter at the time of application)
 
 

atc-manual/1a.-administration/1a.7-check-ride-process.md

@@ -81,7 +81,7 @@ A summary of the process for becoming a Specialist is contained within the follo
 
 Controllers that are currently in the Officer Check Ride phase:
 
-- **must not**{.red} control any facility which has 50 or more total inbounds at the time of opening
+- **must not**{.red} control any facility (including Center) which has 50 or more total inbounds at the time of opening
 
 - **must not**{.red} control any facility which is a livestream airport, official event airport, or HUB of a published event featured on the ATC Schedule *(other official events are permitted unless indicated otherwise - see [1A.4.1](/guide/atc-manual/1a.-administration/1a.4-airport-selection#1a.4.1) above)*
 

atc-manual/1a.-administration/1a.8-disciplinary-and-suspension-procedure.md

@@ -29,17 +29,4 @@ Following any suspension, Controllers will return at the rank they previously he
 
 ### 1A.8.2
 
-If a Controller is issued a Level 2 or Level 3 Violation whilst operating as a pilot, the following can be expected (this will also count towards a Controllers total amount of offenses as outlined above):
-
-
-
-| Violation | Action Taken                          |
-| --------- | ------------------------------------- |
-| Level 2   | 3 day Controller & Discord suspension |
-| Level 3   | 7 day Controller & Discord suspension |
-
-
-
-### 1A.8.3
-
-Serious cases, reviewed by Staff or IFC Moderators, are subject to immediate removal or suspension.
+If a controller is issued a Level 2 or Level 3 Violation whilst operating as a pilot, an IFATC Moderator will initiate a review of the session to determine if the Violation is to be upheld or removed. Excessive Violations or total lack of regard for rules may result in IFATC suspension or permanent removal.

atc-manual/2.-ground/2.1-runway-selection-and-pushback.md

@@ -37,7 +37,7 @@ The color of the runways (i.e. green, amber and red) are for guidance only. You
 
 ### 2.1.3    
 
-When issuing pushback to an aircraft, you **must**{.red} check that the area is clear, if it isn’t, the use of "hold position" **must**{.red} be used (a reminder can be set to avoid forgetting about the aircraft or if it is very busy).
+Controllers **must**{.red} check that the area is clear before issuing pushback clearance. If it is not clear, the use of "hold position" or a give way command **must**{.red} be used prior to issuing the pushback clearance (a reminder can be set to avoid forgetting about the aircraft or if it is very busy).
 
 > By looking at the strips; the oldest "hold position" command would have been sent to the bottom of the tab providing useful reference as to who requested pushback first
 

atc-manual/3.-tower/3.2-departures.md

@@ -65,7 +65,7 @@ Jet aircraft are assumed ready for departure upon reaching the hold short line a
 
 ### 3.2.7    
 
-The use of "Immediate Take-Off" **should**{.red} only be reserved for Departure / Arrival separation where it is highly likely that separation could be lost if the departure does not depart expeditiously. This is normally when aircraft are on final with a range of 2nm or less, however it is also dependent on the final approach speed of the aircraft in question, and the type of aircraft to depart, i.e. 777 vs. 737 *(see [3.2.7](/guide/atc-manual/3.-tower/3.2-departures#3.2.7) below)*.
+The use of "Immediate Take-Off" **should**{.red} only be reserved for Departure / Arrival separation where it is highly likely that separation could be lost if the departure does not depart expeditiously. This is normally when aircraft are on final with a range of 2nm or less, however it is also dependent on the final approach speed of the aircraft in question, and the type of aircraft to depart, i.e. 777 vs. 737 *(see [3.2.8](/guide/atc-manual/3.-tower/3.2-departures#3.2.8) below)*.
 
 
 

atc-manual/4.-atis/4.2-remarks-and-notams.md

@@ -25,8 +25,6 @@ The table below highlights when certain REMARKS or NOTAMS **should**{.red} be us
 | --------------------- | ------------------------------------------------------------ |
 | No Intersection Dept. | Intersection departures **must**{.red} always be allowed unless it blocks the only taxiway for aircraft to access full length **AND** will affect the departure/arrival flow rate *(see [3.2.5](/guide/atc-manual/3.-tower/3.2-departures#3.2.5) above)* |
 | No Pattern Work       | Weather below VMC? Terrain prevents a standard pattern from being flown? **CURRENT** traffic levels will cause a drop in service standards? When 1 of these conditions is met, No Pattern Work **must**{.red} be used *(see [3.4.1](/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4.1) above)* |
-| Flow Control          | Aircraft can expect a delay for departure if the Controller is trying to limit departing traffic (this could be due to aircraft all heading for the same destination) |
-| Long Taxi             | If the runways in use mean that some aircraft can expect a long taxi |
 | Gate Hold             | The use of hold position *(see [2.1.3](/guide/atc-manual/2.-ground/2.1-runway-selection-and-pushback#2.1.3) above)* **should**{.red} be favored but if a long line of  departures needs to be cleared and you have limited space on the taxiways,  gate hold can be used (it **should**{.red} be limited to a maximum of 10 minutes) |
 | No Light Aircraft     | This command **must not**{.red} be used at GA focused airports but can be used at the Controller's discretion at any other airport based on airport accommodations (such as GA parking and airport layout), current traffic, and airport staffing. Controllers **should**{.red} make every attempt to accept light* aircraft at airports which accept them IRL |
 | Rolling Dept.         | To expedite departures – when aircraft are cleared for take-off they will be expected to line up and start their take-off roll immediately. The LUAW command can still be used when there is an operational advantage such as an arrival / departure sequence, or departure / departure sequence where the first aircraft is slow to begin their take-off roll |

atc-manual/7a.-trainers/7a.1-overview.md

@@ -62,7 +62,8 @@ When new Trainers are selected, they will be added to the following channels wit
 
 | Channel        | Purpose                                                      |
 | -------------- | ------------------------------------------------------------ |
-| #tests         | Recruiters will post in this channel with assignments and communication for a test. |
+| #leadership-hq | This channel will be used as a read only announcement channel for all leadership roles. Conversation prompts will be hosted in threads, when needed |
+| #tests         | Recruiters will post in this channel with assignments and communication for a test |
 | #tester [VC]   | This can be used for test participants as a general lounge or operationally to coordinate during an active test. All feedback **should**{.red} still given in writing via the test topic |
 | #test-time     | Automatic notifications of upcoming tests will appear in this channel. Testers **must**{.red} "react" to the post to confirm attendance. Further communication for a test will be in the specific thread for that test in the *#tests* Discord channel |
 | #trainers      | Main channel for coordination purposes within the Training Team |

atc-manual/7a.-trainers/7a.2-training-structure.md

@@ -159,19 +159,6 @@ The following list outlines recommended airports for Radar Training (Trainers ar
 
 
 
-**Location: LPPT (elevation 374ft)**
-
-| RWY  | Approach Type |
-| ---- | ------------- |
-| 03   | ILS           |
-| 17   | GPS           |
-| 21   | ILS           |
-| 35   | GPS           |
-
-> Minimal terrain in the vicinity of the airport. Provides good training for single runway and standard ILS operations as well as an introduction into intersecting runway operations
-
-
-
 **Location: NZAA (elevation 23ft)**
 
 | RWY  | Approach Type |
@@ -260,7 +247,6 @@ Recommended STARs: AVSA1C (North), and TIKE1C (North-west)
 
 +++ Other Airports
 
-- CYVR
 - CYXE
 - KAUS
 - KEGE

atc-manual/7b.-testers/7b.1-testing-process.md

@@ -26,11 +26,12 @@ When new Testers are selected, they will be added to the following channels with
 
 
 
-| Channel      | Purpose                                                      |
-| ------------ | ------------------------------------------------------------ |
-| #tests       | Recruiters will post in this channel with assignments and communication for a test. |
-| #tester [VC] | This can be used for test participants as a general lounge or operationally to coordinate during an active test. All feedback **should**{.red} still given in writing via the test topic |
-| #test-time   | Automatic notifications of upcoming tests will appear in this channel. Testers **must**{.red} "react" to the post to confirm attendance. Further communication for a test will be in the specific thread for that test in the *#tests* Discord channel |
+| Channel        | Purpose                                                      |
+| -------------- | ------------------------------------------------------------ |
+| #leadership-hq | This channel will be used as a read only announcement channel for all leadership roles. Conversation prompts will be hosted in threads, when needed |
+| #tests         | Recruiters will post in this channel with assignments and communication for a test |
+| #tester [VC]   | This can be used for test participants as a general lounge or operationally to coordinate during an active test. All feedback **should**{.red} still given in writing via the test topic |
+| #test-time     | Automatic notifications of upcoming tests will appear in this channel. Testers **must**{.red} "react" to the post to confirm attendance. Further communication for a test will be in the specific thread for that test in the *#tests* Discord channel |