Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

24.2 #664

Merged
merged 12 commits into from
Mar 17, 2024
Merged

24.2 #664

Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added _images/manual/frames/flight-school-242.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/manual/frames/flight-school-242@2x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/manual/frames/flight-school-242@3x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed _images/manual/frames/flight-training-233.png
Binary file not shown.
Binary file removed _images/manual/frames/flight-training-233@2x.png
Binary file not shown.
Binary file removed _images/manual/frames/flight-training-233@3x.png
Binary file not shown.
Binary file added _images/manual/frames/flight-training-242.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/manual/frames/flight-training-242@2x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/manual/frames/flight-training-242@3x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed _images/manual/frames/home-screen-233.png
Binary file not shown.
Binary file removed _images/manual/frames/home-screen-233@2x.png
Binary file not shown.
Binary file removed _images/manual/frames/home-screen-233@3x.png
Binary file not shown.
Binary file added _images/manual/frames/home-screen-242-v2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/manual/frames/home-screen-242-v2@2x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/manual/frames/home-screen-242-v2@3x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed _images/manual/frames/mode-233.png
Binary file not shown.
Binary file removed _images/manual/frames/mode-233@2x.png
Binary file not shown.
Binary file removed _images/manual/frames/mode-233@3x.png
Binary file not shown.
Binary file added _images/manual/frames/mode-242.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/manual/frames/mode-242@2x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added _images/manual/frames/mode-242@3x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed _images/manual/frames/settings-account-233.png
Binary file not shown.
Binary file removed _images/manual/frames/settings-account-233@2x.png
Binary file not shown.
Binary file removed _images/manual/frames/settings-account-233@3x.png
Binary file not shown.
Binary file added _images/manual/frames/settings-account-242.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed _images/manual/frames/settings-audio-233.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-audio-233@2x.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-audio-233@3x.png
Diff not rendered.
Binary file added _images/manual/frames/settings-audio-242.png
Binary file added _images/manual/frames/settings-audio-242@2x.png
Binary file added _images/manual/frames/settings-audio-242@3x.png
Binary file removed _images/manual/frames/settings-controls-233.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-controls-233@2x.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-controls-233@3x.png
Diff not rendered.
Binary file added _images/manual/frames/settings-controls-242.png
Binary file removed _images/manual/frames/settings-general-233.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-general-233@2x.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-general-233@3x.png
Diff not rendered.
Binary file added _images/manual/frames/settings-general-242.png
Binary file removed _images/manual/frames/settings-graphics-233.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-graphics-233@2x.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-graphics-233@3x.png
Diff not rendered.
Binary file added _images/manual/frames/settings-graphics-242.png
Binary file removed _images/manual/frames/settings-online-233.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-online-233@2x.png
Diff not rendered.
Binary file removed _images/manual/frames/settings-online-233@3x.png
Diff not rendered.
Binary file added _images/manual/frames/settings-online-242.png
Binary file added _images/manual/frames/settings-online-242@2x.png
Binary file added _images/manual/frames/settings-online-242@3x.png

Large diffs are not rendered by default.

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion atc-guide/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ meta: Learn how to get the most out of Infinite Flight with our online documenta



## Guide Version: 24.1.0
## Guide Version: 24.2.0



Expand Down
1 change: 1 addition & 0 deletions atc-manual/1a.-administration/1a.3-controller-rules.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ auth: ifatc
- 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
- Controllers **must not**{.red} tag other Controllers that are currently open on an active frequency unless it is operationally critical (this does not include Controllers open on a different frequency that are sending operational messages to each other)
- Controllers **must not**{.red} control on the Training Server *(see [7.4.4](/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.4) below for exceptions)*
- Controllers **must not**{.red} act as a Controller and as a pilot simultaneously on separate devices
- Controllers **must not**{.red} control Infinite Flight on other platforms (such as BlueStacks) due to Controller replays not being stored *(see [1B.3.1](/guide/atc-manual/1b.-violations/1b.3-incident-resolution-procedure#1b.3.1) above)*
Expand Down
2 changes: 1 addition & 1 deletion atc-manual/1a.-administration/1a.4-airport-selection.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,4 @@ auth: ifatc



> For official events (e.g. FF, GA Day or steams), Controllers can open the event airports up to 1 hour (maximum) before the event start time to ensure full coverage
> For official events (e.g. FF, GA Day or livesteams), Controllers can open the event airports up to 1 hour (maximum) before the event start time to ensure full coverage
46 changes: 30 additions & 16 deletions atc-manual/1a.-administration/1a.6-rank-structure.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,42 +22,54 @@ The table below outlines the rank structure in place. Promotion is based on acti



| Rank | Frequencies Available | Test Required | Check Ride |
| ---------- | ------------------------ | ------------------------------ | ---------- |
| Apprentice | C / D / ATIS | Theory and Practical (Initial) | No |
| Specialist | B / C / D / ATIS | No | Yes* |
| Officer | Radar / B / C / D / ATIS | Theory and Practical (Radar) | Yes** |
| Supervisor | No restrictions | No | No |
| Rank | Frequencies Available | Test Required | Check Ride |
| ---------- | ------------------------ | ---------------------------- | ---------- |
| Apprentice | B / C / D / ATIS | Theory and Practical (Tower) | No |
| Specialist | B / C / D / ATIS | No | Yes* |
| Officer | Radar / B / C / D / ATIS | Theory and Practical (Radar) | Yes** |
| Supervisor | No restrictions | No | No |

**On promotion to Specialist, Controllers are placed on probation until the "Specialist Check Ride" phase is completed (see [1A.7.2](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.2) below)*
**On promotion to Specialist, Controllers are placed on probation until the "Specialist Check Ride" phase is completed (see [1A.7.4](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.4) below)*

***On promotion to Officer, Controllers are placed on probation until the "Officer Check Ride" phase is completed (see [1A.7.8](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.8) below)*
***On promotion to Officer, Controllers are placed on probation until the "Officer Check Ride" phase is completed (see [1A.7.6](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.6) below)*



> All Controllers are subject to promotion/demotion at any time based on activity, performance and feedback!



## Promotion to Specialist
## Apprentice

### 1A.6.2

Promotion to the rank of Specialist is dealt with on a case by case basis, and not solely on time served. With this in mind, Apprentice Controllers **must**{.red} avoid asking when they will be promoted; and instead, **should**{.red} focus on providing a good quality ATC service. Controllers will be notified when they have been promoted and placed in the Specialist Check Ride phase *(see [1A.7.2](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.2) below)*.
This is the entry rank for IFATC and so the maximum arrival count at the time of opening any airport is 25 aircraft. Apprentices **must not**{.red} control any facility which is a livestream airport, official event airport, or HUB of 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)*



## Promotion to Officer
> It is acceptable for the arrival count to increase above this limit once open, however Apprentices **should**{.red} try to select appropriate airports that take into account the length of time they are controlling for, and any increases in traffic *(see [1A.4.1](/guide/atc-manual/1a.-administration/1a.4-airport-selection#1a.4.1) and [1A.5.3](/guide/atc-manual/1a.-administration/1a.5-activity-requirements#1a.5.3) above)*



## Promotion to Specialist

### 1A.6.3

Promotion to the rank of Officer is on application only *(see [7.4.1](/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.1) below)* and the Radar Training program **must**{.red} be successfully passed in order to achieve this rank and subsequently control radar facilities.
Promotion to the rank of Specialist is dealt with on a case by case basis, and not solely on time served. With this in mind, Apprentice Controllers **must**{.red} avoid asking when they will be promoted; and instead, **should**{.red} focus on providing a good quality ATC service. Controllers will be notified when they have been promoted and placed in the Specialist Check Ride phase *(see [1A.7.4](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.4) below)*.



## Promotion to Officer

### 1A.6.4

Before commencement of training for the rank of Officer, the following requirements **must**{.red} be met (do not contact a Recruiter for Radar Training before you meet the minimum requirements):
Promotion to the rank of Officer is by application only *(see [7.4.1](/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.1) below)* and the Radar Training program **must**{.red} be successfully passed in order to achieve this rank and subsequently control radar facilities.



### 1A.6.5

Before commencement of training for the rank of Officer, the following requirements **must**{.red} be met:



Expand All @@ -72,13 +84,15 @@ Before commencement of training for the rank of Officer, the following requireme



> Returning members of IFATC are not subject to the above same criteria and may apply (and commence training) for the rank of Officer immediately following the successful completion of the "Specialist Check Ride" phase *(see [1A.7.2](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.2) below)*
### 1A.6.6

Returning members of IFATC that previously held the rank of Officer are not subject to the above same criteria and may apply (and commence training) for the rank of Officer immediately following the successful completion of the "Specialist Check Ride" phase *(see [1A.7.1](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.1) below)*.



## Promotion to Supervisor

### 1A.6.5
### 1A.6.7

The rank of Supervisor is only awarded when a need exists and to Controllers that have demonstrated a high standard of controlling and professional conduct within IFATC. Their role is to assist in the day-to-day operations of IFATC, provide leadership and/or mentoring of individual Controllers, monitor controlling quality via the "Check Ride" process, and to moderate the Infinite Flight Expert Server. The following prerequisites are required for promotion to the rank of Supervisor:

Expand All @@ -94,7 +108,7 @@ The rank of Supervisor is only awarded when a need exists and to Controllers tha

## Other IFATC Roles

### 1A.6.6
### 1A.6.8

In addition to the rank structure outlined above, individuals may hold other roles within IFATC. These are shown below:

Expand Down
61 changes: 27 additions & 34 deletions atc-manual/1a.-administration/1a.7-check-ride-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,90 +16,83 @@ The Check Ride process is used to monitor newly promoted Specialists and Officer



| Check Ride | Period | Eligibility |
| ---------- | ------- | ------------------------------------------------------------ |
| Specialist | 7 days | See [1A.6.2](/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.2) above |
| Officer | 30 days | See [1A.6.3](/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.3) above |

| Check Ride | Period | Max Arrival Count* | Eligibility |
| ------------- | ------- | ------------------ | ------------------------------------------------------------ |
| Specialist | 7 days | 50 | See [1A.6.2](/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.2) above |
| Officer | 30 days | 50 | See [1A.6.3](/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.3) above |
| Prior Officer | 15 days | 50 | See [1A.6.6](/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.6) above |

**at the time of opening*

> One of the main aspects of the Check Ride process is ensuring that quality of service is maintained with the Controller's new role. Therefore during the evaluation, the Controller's ability to select sensible airports and set a personal limitation **must**{.red} be satisfactory to complete the Check Ride phase



## Specialist Check Ride



### 1A.7.2

When Controllers are eligible for promotion to the rank of Specialist (based on activity, performance and feedback), they will receive a DM informing them of their promotion on a probationary basis.
When Controllers are eligible for promotion to the rank of Specialist (based on activity, performance and feedback) or have passed The Radar Practical Test for the rank of Officer, they will receive a DM informing them of their promotion on a probationary basis. Moderators and/or Supervisors will receive automatic notifications when the Controller opens, and those that are available will attend the Controller’s current session and monitor their performance. At the end of the Check Ride phase, all evaluations will be collated, with a final review taking place. The Controller will be informed if they have been successful or unsuccessful, and given feedback when applicable.



### 1A.7.3

The probation period **should not**{.red} exceed 7 days, unless it is due to Moderator/Supervisor availability *(see [1A.7.5](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.5) below*). During this time, Controllers:

- **Must**{.red} control Bravo classification airports where possible (Charlie classification airports are acceptable if they provide for adequate evaluation)
- **Must**{.red} control on a regular basis (at least 3 separate occasions)
- **Must not**{.red} control stream or FF featured airports (airports from the ATC Schedule or other official events are permitted unless indicated otherwise)
The Check Ride phase should not be longer than the periods outlined *(see [1A.7.1](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.1) above)*, however if Moderators and/or Supervisors are unable to attend one of the Controllers sessions during their probation period, their probation will be extended provided that they have followed **ALL** the instructions set out within this section and in particular, controlling on a regular basis in which to maximize the chance of a review. If this is not the case, they will be demoted back to their previous rank, and a subsequent promotion will take place in due course.



Tip

: Splitting the frequencies (such as just controlling Ground) with other Controllers is heavily encouraged, especially at featured airports
## Specialist Check Ride



### 1A.7.4

Moderators and/or Supervisors will receive automatic notifications when the Controller opens, and those that are available will attend the Controller’s current session and monitor their performance. At the end of the Check Ride phase, all evaluations will be collated, with a final review taking place. The Controller will be informed if they have been successful or unsuccessful, and given feedback when applicable.
Controllers that are currently in the Specialist Check Ride phase:

- **must**{.red} control Bravo classification airports where possible (Charlie classification airports are acceptable if they provide for adequate evaluation)
- **must**{.red} control on a regular basis (at least 3 separate occasions)

- **must not**{.red} control any facility which has 50 or more total inbounds at the time of opening

### 1A.7.5
- **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)*

If Moderators and/or Supervisors are unable to attend one of the Controllers sessions during their probation period, their probation will be extended provided that they have followed **ALL** the instructions set out within this section *(see [1A.7.3](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.3) above)* and in particular, controlling on a regular basis in which to maximize the chance of a review. If this is not the case, they will be demoted back to Apprentice, and a subsequent promotion will take place in due course.


Tip

### 1A.7.6
: Splitting the frequencies (such as just controlling Ground) with other Controllers is heavily encouraged, especially at featured airports

If the Controller has been successful, the probation period will end with immediate effect and the instructions contained within this section will no longer need to be followed. If they are unsuccessful, a waiting period will be given before they re-enter the Check Ride phase; in which time, the Controller will be able to improve in the areas briefed.



### 1A.7.7
### 1A.7.5

A summary of the process for becoming a Specialist is contained within the following flow chart:



![Image 1A.7.7.1 - Promotion to Specialist Flowchart ](_images/manual/graphics/atc-specialist.svg)
![Image 1A.7.5.1 - Promotion to Specialist Flowchart ](_images/manual/graphics/promotion-to-specialist-v2.svg)



## Officer Check Ride



### 1A.7.8
### 1A.7.6

Controllers that are currently in the Officer Check Ride phase:

Controllers that are successful in the Radar Practical Test will be promoted and placed in the Officer Check Ride phase for a period of 30 days. Moderators and/or Supervisors will receive automatic notifications when the Controller opens*, and those that are available will attend the Controller’s current session and monitor their performance. At the end of the Officer Check Ride phase, all evaluations will be collated, with a final review taking place. The Controller will be informed if they have been successful or unsuccessful, and given feedback when applicable. **During this time, Controllers are expected to be responsible in their new role; starting off slowly and ensuring quality of service, over quantity.**{.red}
- **must not**{.red} control any facility 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)*


> 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, this includes Center if the position will serve as the primary approach facility (i.e. approach is not currently open)
> - which is a stream or FF featured airport *(airports from the ATC Schedule or 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)*

> Controllers are expected to be responsible in their new role; starting off slowly and ensuring quality of service, over quantity.


### 1A.7.9

### 1A.7.7

A summary of the process for becoming an Officer is contained within the following flow chart:

![Image 7.4.8.1 - Radar Recruitment Flowchart](_images/manual/graphics/radar-recruitment-v2.svg)
![Image 7.4.9.1 - Radar Recruitment Flowchart](_images/manual/graphics/radar-recruitment-v3.svg)
8 changes: 7 additions & 1 deletion atc-manual/2.-ground/2.2-taxi-and-use-of-give-way.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,12 @@ Tip

### 2.2.3

Controllers **should**{.red} not assign specific gates for arriving aircraft requesting taxi to park. Parking spot determination **should**{.red} be made by the pilot and accommodated by ATC, when possible. Aircraft requesting a clearance to taxi to parking without a specific spot may be given specific routing via progressive instructions or drag & taxi routing to deconflict with other traffic, however they **should**{.red} be allowed to proceed to their desired spot once all conflicts are resolved.



### 2.2.4

Controllers also have Progressive Taxi Instructions to assist with ground movement including one way systems, potential conflicts and intersection departures. Controllers **should**{.red} take note that **VERY CLOSE MONITORING** is required when using this tool and therefore **should**{.red} only use it when absolutely necessary. Before it’s used, Controllers **should**{.red} send "Expect Progressive Taxi Instructions" to the aircraft in question (although this may not always be possible), once this is done the following commands are available:


Expand All @@ -63,7 +69,7 @@ Once the Progressive Taxi Instructions are no longer required, the Controller **



### 2.2.4
### 2.2.5

If an aircraft requests frequency change after being issued "taxi to RWYXX, contact tower when ready" (commonly encountered when the aircraft is holding short of the runway), a "frequency change already sent" message **should**{.red} be used. Sometimes the pilots do not realise that the previous command gave them permission to change frequency.

Expand Down
4 changes: 4 additions & 0 deletions atc-manual/3.-tower/3.1-separation.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,10 @@ If at any time, separation is likely to be lost, the Controller **must**{.red} b



> It is generally considered too late to request an aircraft to reject the takeoff roll when they are above 100kts



### 3.1.4

Most commercial aircraft approach speeds are between 120-150kts. If a Controller needs more separation the use of "maintain slowest practical speed" can be utilized, however this **should not**{.red} be used within 4 miles to touchdown as it is likely the aircraft is already at its final approach speed. In addition, the Controller **should**{.red} also look at the groundspeed (GS)/indicated airspeed (IAS) of the aircraft in question before sending this command as the aircraft could already be at their final approach speed. Regardless of aircraft position, if an aircraft IAS is excessive then this command can be useful however it is important to take note of two points:
Expand Down
Loading
Loading