diff --git a/_images/manual/frames/flight-school-242.png b/_images/manual/frames/flight-school-242.png new file mode 100644 index 00000000..e305ef4c Binary files /dev/null and b/_images/manual/frames/flight-school-242.png differ diff --git a/_images/manual/frames/flight-school-242@2x.png b/_images/manual/frames/flight-school-242@2x.png new file mode 100644 index 00000000..778ed5f0 Binary files /dev/null and b/_images/manual/frames/flight-school-242@2x.png differ diff --git a/_images/manual/frames/flight-school-242@3x.png b/_images/manual/frames/flight-school-242@3x.png new file mode 100644 index 00000000..cebd4920 Binary files /dev/null and b/_images/manual/frames/flight-school-242@3x.png differ diff --git a/_images/manual/frames/flight-training-233.png b/_images/manual/frames/flight-training-233.png deleted file mode 100644 index 97d5ea2d..00000000 Binary files a/_images/manual/frames/flight-training-233.png and /dev/null differ diff --git a/_images/manual/frames/flight-training-233@2x.png b/_images/manual/frames/flight-training-233@2x.png deleted file mode 100644 index 96a7fd98..00000000 Binary files a/_images/manual/frames/flight-training-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/flight-training-233@3x.png b/_images/manual/frames/flight-training-233@3x.png deleted file mode 100644 index 810cee9a..00000000 Binary files a/_images/manual/frames/flight-training-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/flight-training-242.png b/_images/manual/frames/flight-training-242.png new file mode 100644 index 00000000..b55be7be Binary files /dev/null and b/_images/manual/frames/flight-training-242.png differ diff --git a/_images/manual/frames/flight-training-242@2x.png b/_images/manual/frames/flight-training-242@2x.png new file mode 100644 index 00000000..8d8bb9ab Binary files /dev/null and b/_images/manual/frames/flight-training-242@2x.png differ diff --git a/_images/manual/frames/flight-training-242@3x.png b/_images/manual/frames/flight-training-242@3x.png new file mode 100644 index 00000000..25abf6a7 Binary files /dev/null and b/_images/manual/frames/flight-training-242@3x.png differ diff --git a/_images/manual/frames/home-screen-233.png b/_images/manual/frames/home-screen-233.png deleted file mode 100644 index 8a60fbcb..00000000 Binary files a/_images/manual/frames/home-screen-233.png and /dev/null differ diff --git a/_images/manual/frames/home-screen-233@2x.png b/_images/manual/frames/home-screen-233@2x.png deleted file mode 100644 index 278917dc..00000000 Binary files a/_images/manual/frames/home-screen-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/home-screen-233@3x.png b/_images/manual/frames/home-screen-233@3x.png deleted file mode 100644 index f3320c44..00000000 Binary files a/_images/manual/frames/home-screen-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/home-screen-242-v2.png b/_images/manual/frames/home-screen-242-v2.png new file mode 100644 index 00000000..84342468 Binary files /dev/null and b/_images/manual/frames/home-screen-242-v2.png differ diff --git a/_images/manual/frames/home-screen-242-v2@2x.png b/_images/manual/frames/home-screen-242-v2@2x.png new file mode 100644 index 00000000..bd1bd25f Binary files /dev/null and b/_images/manual/frames/home-screen-242-v2@2x.png differ diff --git a/_images/manual/frames/home-screen-242-v2@3x.png b/_images/manual/frames/home-screen-242-v2@3x.png new file mode 100644 index 00000000..03cea9a9 Binary files /dev/null and b/_images/manual/frames/home-screen-242-v2@3x.png differ diff --git a/_images/manual/frames/mode-233.png b/_images/manual/frames/mode-233.png deleted file mode 100644 index 8183f80a..00000000 Binary files a/_images/manual/frames/mode-233.png and /dev/null differ diff --git a/_images/manual/frames/mode-233@2x.png b/_images/manual/frames/mode-233@2x.png deleted file mode 100644 index 541e8ca7..00000000 Binary files a/_images/manual/frames/mode-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/mode-233@3x.png b/_images/manual/frames/mode-233@3x.png deleted file mode 100644 index 2853f406..00000000 Binary files a/_images/manual/frames/mode-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/mode-242.png b/_images/manual/frames/mode-242.png new file mode 100644 index 00000000..8a51ec8a Binary files /dev/null and b/_images/manual/frames/mode-242.png differ diff --git a/_images/manual/frames/mode-242@2x.png b/_images/manual/frames/mode-242@2x.png new file mode 100644 index 00000000..a70ee4e0 Binary files /dev/null and b/_images/manual/frames/mode-242@2x.png differ diff --git a/_images/manual/frames/mode-242@3x.png b/_images/manual/frames/mode-242@3x.png new file mode 100644 index 00000000..895bb7ce Binary files /dev/null and b/_images/manual/frames/mode-242@3x.png differ diff --git a/_images/manual/frames/settings-account-233.png b/_images/manual/frames/settings-account-233.png deleted file mode 100644 index 8551c841..00000000 Binary files a/_images/manual/frames/settings-account-233.png and /dev/null differ diff --git a/_images/manual/frames/settings-account-233@2x.png b/_images/manual/frames/settings-account-233@2x.png deleted file mode 100644 index 7adb6207..00000000 Binary files a/_images/manual/frames/settings-account-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/settings-account-233@3x.png b/_images/manual/frames/settings-account-233@3x.png deleted file mode 100644 index aaf53c9a..00000000 Binary files a/_images/manual/frames/settings-account-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/settings-account-242.png b/_images/manual/frames/settings-account-242.png new file mode 100644 index 00000000..a60ad567 Binary files /dev/null and b/_images/manual/frames/settings-account-242.png differ diff --git a/_images/manual/frames/settings-account-242@2x.png b/_images/manual/frames/settings-account-242@2x.png new file mode 100644 index 00000000..1e3cf517 Binary files /dev/null and b/_images/manual/frames/settings-account-242@2x.png differ diff --git a/_images/manual/frames/settings-account-242@3x.png b/_images/manual/frames/settings-account-242@3x.png new file mode 100644 index 00000000..92394d48 Binary files /dev/null and b/_images/manual/frames/settings-account-242@3x.png differ diff --git a/_images/manual/frames/settings-audio-233.png b/_images/manual/frames/settings-audio-233.png deleted file mode 100644 index bc30b456..00000000 Binary files a/_images/manual/frames/settings-audio-233.png and /dev/null differ diff --git a/_images/manual/frames/settings-audio-233@2x.png b/_images/manual/frames/settings-audio-233@2x.png deleted file mode 100644 index ce52ffe4..00000000 Binary files a/_images/manual/frames/settings-audio-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/settings-audio-233@3x.png b/_images/manual/frames/settings-audio-233@3x.png deleted file mode 100644 index 388492a3..00000000 Binary files a/_images/manual/frames/settings-audio-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/settings-audio-242.png b/_images/manual/frames/settings-audio-242.png new file mode 100644 index 00000000..1b2bb0a1 Binary files /dev/null and b/_images/manual/frames/settings-audio-242.png differ diff --git a/_images/manual/frames/settings-audio-242@2x.png b/_images/manual/frames/settings-audio-242@2x.png new file mode 100644 index 00000000..5e24b75b Binary files /dev/null and b/_images/manual/frames/settings-audio-242@2x.png differ diff --git a/_images/manual/frames/settings-audio-242@3x.png b/_images/manual/frames/settings-audio-242@3x.png new file mode 100644 index 00000000..4fad2d2b Binary files /dev/null and b/_images/manual/frames/settings-audio-242@3x.png differ diff --git a/_images/manual/frames/settings-controls-233.png b/_images/manual/frames/settings-controls-233.png deleted file mode 100644 index a6b8cad7..00000000 Binary files a/_images/manual/frames/settings-controls-233.png and /dev/null differ diff --git a/_images/manual/frames/settings-controls-233@2x.png b/_images/manual/frames/settings-controls-233@2x.png deleted file mode 100644 index b012cd3f..00000000 Binary files a/_images/manual/frames/settings-controls-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/settings-controls-233@3x.png b/_images/manual/frames/settings-controls-233@3x.png deleted file mode 100644 index f0ecdb89..00000000 Binary files a/_images/manual/frames/settings-controls-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/settings-controls-242.png b/_images/manual/frames/settings-controls-242.png new file mode 100644 index 00000000..218a90ef Binary files /dev/null and b/_images/manual/frames/settings-controls-242.png differ diff --git a/_images/manual/frames/settings-controls-242@2x.png b/_images/manual/frames/settings-controls-242@2x.png new file mode 100644 index 00000000..7fea2549 Binary files /dev/null and b/_images/manual/frames/settings-controls-242@2x.png differ diff --git a/_images/manual/frames/settings-controls-242@3x.png b/_images/manual/frames/settings-controls-242@3x.png new file mode 100644 index 00000000..c957a4c3 Binary files /dev/null and b/_images/manual/frames/settings-controls-242@3x.png differ diff --git a/_images/manual/frames/settings-general-233.png b/_images/manual/frames/settings-general-233.png deleted file mode 100644 index 5d3d5523..00000000 Binary files a/_images/manual/frames/settings-general-233.png and /dev/null differ diff --git a/_images/manual/frames/settings-general-233@2x.png b/_images/manual/frames/settings-general-233@2x.png deleted file mode 100644 index cf06d255..00000000 Binary files a/_images/manual/frames/settings-general-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/settings-general-233@3x.png b/_images/manual/frames/settings-general-233@3x.png deleted file mode 100644 index 6065c07f..00000000 Binary files a/_images/manual/frames/settings-general-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/settings-general-242.png b/_images/manual/frames/settings-general-242.png new file mode 100644 index 00000000..588b2973 Binary files /dev/null and b/_images/manual/frames/settings-general-242.png differ diff --git a/_images/manual/frames/settings-general-242@2x.png b/_images/manual/frames/settings-general-242@2x.png new file mode 100644 index 00000000..c05259d3 Binary files /dev/null and b/_images/manual/frames/settings-general-242@2x.png differ diff --git a/_images/manual/frames/settings-general-242@3x.png b/_images/manual/frames/settings-general-242@3x.png new file mode 100644 index 00000000..10503ac4 Binary files /dev/null and b/_images/manual/frames/settings-general-242@3x.png differ diff --git a/_images/manual/frames/settings-graphics-233.png b/_images/manual/frames/settings-graphics-233.png deleted file mode 100644 index d2058552..00000000 Binary files a/_images/manual/frames/settings-graphics-233.png and /dev/null differ diff --git a/_images/manual/frames/settings-graphics-233@2x.png b/_images/manual/frames/settings-graphics-233@2x.png deleted file mode 100644 index 6b02bef5..00000000 Binary files a/_images/manual/frames/settings-graphics-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/settings-graphics-233@3x.png b/_images/manual/frames/settings-graphics-233@3x.png deleted file mode 100644 index 1fe05e23..00000000 Binary files a/_images/manual/frames/settings-graphics-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/settings-graphics-242.png b/_images/manual/frames/settings-graphics-242.png new file mode 100644 index 00000000..9a5eecd7 Binary files /dev/null and b/_images/manual/frames/settings-graphics-242.png differ diff --git a/_images/manual/frames/settings-graphics-242@2x.png b/_images/manual/frames/settings-graphics-242@2x.png new file mode 100644 index 00000000..a618f692 Binary files /dev/null and b/_images/manual/frames/settings-graphics-242@2x.png differ diff --git a/_images/manual/frames/settings-graphics-242@3x.png b/_images/manual/frames/settings-graphics-242@3x.png new file mode 100644 index 00000000..92c78f04 Binary files /dev/null and b/_images/manual/frames/settings-graphics-242@3x.png differ diff --git a/_images/manual/frames/settings-online-233.png b/_images/manual/frames/settings-online-233.png deleted file mode 100644 index 46659033..00000000 Binary files a/_images/manual/frames/settings-online-233.png and /dev/null differ diff --git a/_images/manual/frames/settings-online-233@2x.png b/_images/manual/frames/settings-online-233@2x.png deleted file mode 100644 index d97998b4..00000000 Binary files a/_images/manual/frames/settings-online-233@2x.png and /dev/null differ diff --git a/_images/manual/frames/settings-online-233@3x.png b/_images/manual/frames/settings-online-233@3x.png deleted file mode 100644 index 05330ebf..00000000 Binary files a/_images/manual/frames/settings-online-233@3x.png and /dev/null differ diff --git a/_images/manual/frames/settings-online-242.png b/_images/manual/frames/settings-online-242.png new file mode 100644 index 00000000..b6502517 Binary files /dev/null and b/_images/manual/frames/settings-online-242.png differ diff --git a/_images/manual/frames/settings-online-242@2x.png b/_images/manual/frames/settings-online-242@2x.png new file mode 100644 index 00000000..c81da13f Binary files /dev/null and b/_images/manual/frames/settings-online-242@2x.png differ diff --git a/_images/manual/frames/settings-online-242@3x.png b/_images/manual/frames/settings-online-242@3x.png new file mode 100644 index 00000000..00a3be3b Binary files /dev/null and b/_images/manual/frames/settings-online-242@3x.png differ diff --git a/_images/manual/graphics/atc-specialist.svg b/_images/manual/graphics/promotion-to-specialist-v2.svg similarity index 83% rename from _images/manual/graphics/atc-specialist.svg rename to _images/manual/graphics/promotion-to-specialist-v2.svg index c62a96d8..bff1858b 100644 --- a/_images/manual/graphics/atc-specialist.svg +++ b/_images/manual/graphics/promotion-to-specialist-v2.svg @@ -1,5 +1,5 @@ - + @@ -20,7 +20,7 @@ - + @@ -41,7 +41,7 @@ - + diff --git a/_images/manual/graphics/radar-recruitment-v2.svg b/_images/manual/graphics/radar-recruitment-v3.svg similarity index 50% rename from _images/manual/graphics/radar-recruitment-v2.svg rename to _images/manual/graphics/radar-recruitment-v3.svg index 2fb0ad53..03b0199a 100644 --- a/_images/manual/graphics/radar-recruitment-v2.svg +++ b/_images/manual/graphics/radar-recruitment-v3.svg @@ -5,40 +5,42 @@ - - - - - - + + + + - - + + - - - - + + + + + + + + - - - - - - + + + + + + @@ -49,37 +51,42 @@ - - - - + + - - - + + + + + + - - - + - + - + + + + + + - - - + + + + - - - - - - - + + + + + + + diff --git a/atc-guide/index.md b/atc-guide/index.md index c803b017..bf62c8a0 100644 --- a/atc-guide/index.md +++ b/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.1.0 +## Guide Version: 24.2.0 diff --git a/atc-manual/1a.-administration/1a.3-controller-rules.md b/atc-manual/1a.-administration/1a.3-controller-rules.md index 7ed9b24b..0c76ebb1 100644 --- a/atc-manual/1a.-administration/1a.3-controller-rules.md +++ b/atc-manual/1a.-administration/1a.3-controller-rules.md @@ -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)* diff --git a/atc-manual/1a.-administration/1a.4-airport-selection.md b/atc-manual/1a.-administration/1a.4-airport-selection.md index 9b483bab..d99eebd4 100644 --- a/atc-manual/1a.-administration/1a.4-airport-selection.md +++ b/atc-manual/1a.-administration/1a.4-airport-selection.md @@ -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 diff --git a/atc-manual/1a.-administration/1a.6-rank-structure.md b/atc-manual/1a.-administration/1a.6-rank-structure.md index 69151159..833f6f45 100644 --- a/atc-manual/1a.-administration/1a.6-rank-structure.md +++ b/atc-manual/1a.-administration/1a.6-rank-structure.md @@ -22,16 +22,16 @@ 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)* @@ -39,25 +39,37 @@ The table below outlines the rank structure in place. Promotion is based on acti -## 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: @@ -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: @@ -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: diff --git a/atc-manual/1a.-administration/1a.7-check-ride-process.md b/atc-manual/1a.-administration/1a.7-check-ride-process.md index 7190a9d2..14ae64da 100644 --- a/atc-manual/1a.-administration/1a.7-check-ride-process.md +++ b/atc-manual/1a.-administration/1a.7-check-ride-process.md @@ -16,68 +16,60 @@ 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) @@ -85,21 +77,22 @@ A summary of the process for becoming a Specialist is contained within the follo -### 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) \ No newline at end of file +![Image 7.4.9.1 - Radar Recruitment Flowchart](_images/manual/graphics/radar-recruitment-v3.svg) \ No newline at end of file diff --git a/atc-manual/2.-ground/2.2-taxi-and-use-of-give-way.md b/atc-manual/2.-ground/2.2-taxi-and-use-of-give-way.md index 28ac6c33..8dd5bdee 100644 --- a/atc-manual/2.-ground/2.2-taxi-and-use-of-give-way.md +++ b/atc-manual/2.-ground/2.2-taxi-and-use-of-give-way.md @@ -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: @@ -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. diff --git a/atc-manual/3.-tower/3.1-separation.md b/atc-manual/3.-tower/3.1-separation.md index 64d6d7c8..d2668a41 100644 --- a/atc-manual/3.-tower/3.1-separation.md +++ b/atc-manual/3.-tower/3.1-separation.md @@ -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: diff --git a/atc-manual/3.-tower/3.2-departures.md b/atc-manual/3.-tower/3.2-departures.md index 43aeefd6..5c26b2a7 100644 --- a/atc-manual/3.-tower/3.2-departures.md +++ b/atc-manual/3.-tower/3.2-departures.md @@ -55,25 +55,33 @@ Intersection departures are a great method in which to optimize the departure se ## Take-Off -### 3.2.6 -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)*. + +### 3.2.6 + +Jet aircraft are assumed ready for departure upon reaching the hold short line at the assigned departure runway. Controllers may issue a line up & wait or takeoff clearance **prior** to the aircraft requesting departure. ### 3.2.7 -The range displayed in nm on an aircraft tag is with reference to the tower, not the runway threshold that the aircraft is landing on. Controllers are encouraged to work out what the aircraft range is from the threshold so that they are aware when separation is close. A good way is by looking at the altitude of the aircraft, when aircraft fly a standard 3 degree glideslope, you can expect a range of 2nm from the touchdown to coincide with an altitude of approximately 600ft, assuming an airport elevation of 0ft *(see [6.10.4](/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.4) 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.7](/guide/atc-manual/3.-tower/3.2-departures#3.2.7) below)*. ### 3.2.8 +The range displayed in nm on an aircraft tag is with reference to the tower, not the runway threshold that the aircraft is landing on. Controllers are encouraged to work out what the aircraft range is from the threshold so that they are aware when separation is close. A good way is by looking at the altitude of the aircraft, when aircraft fly a standard 3 degree glideslope, you can expect a range of 2nm from the touchdown to coincide with an altitude of approximately 600ft, assuming an airport elevation of 0ft *(see [6.11.4](/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.4) below).* + + + +### 3.2.9 + When "Straight Out Dept." is being broadcast in the current ATIS *(see [4.2.1](/guide/atc-manual/4.-atis/4.2-remarks-and-notams#4.2.1) below)*, the use of "fly runway heading until at or above XXXXft" **should**{.red} be used with every take-off command sent as a final reminder to the departing aircraft; the options available include 1000ft, 3000ft and 5000ft AAL (rounded down to the nearest 500ft). Aircraft climb rates can vary significantly, thus; although aircraft have been instructed to maintain runway heading until a specific altitude, with "Straight Out Dept." selected in the ATIS, aircraft cannot deviate from runway heading until the departing aircraft is clear of any conflict. -### 3.2.9 +### 3.2.10 SIDs often involve turns away from the airport shortly after departure; due to this, if "Straight Out Dept." is being utilized, Controllers **should**{.red} note that this may prevent pilots from flying the selected SID *(see [4.2.1](/guide/atc-manual/4.-atis/4.2-remarks-and-notams#4.2.1) and [6.4.3](/guide/atc-manual/6.-radar/6.4-departure-check-in#6.4.3) below)*. @@ -81,7 +89,7 @@ SIDs often involve turns away from the airport shortly after departure; due to t ## Frequency Change -### 3.2.10 +### 3.2.11 Departing aircraft **should**{.red} be issued a frequency change 1/2 mile off the departure end unless there are potential conflicts (these **must**{.red} be resolved prior to approving a frequency change). Controllers **should**{.red} avoid changes during critical phases of flight (i.e. immediately after rotation). diff --git a/atc-manual/6.-radar/6.9-global-positioning-system-(gps)-approach.md b/atc-manual/6.-radar/6.10-global-positioning-system-(gps)-approach.md similarity index 88% rename from atc-manual/6.-radar/6.9-global-positioning-system-(gps)-approach.md rename to atc-manual/6.-radar/6.10-global-positioning-system-(gps)-approach.md index f49f8811..e994d7db 100644 --- a/atc-manual/6.-radar/6.9-global-positioning-system-(gps)-approach.md +++ b/atc-manual/6.-radar/6.10-global-positioning-system-(gps)-approach.md @@ -1,11 +1,11 @@ --- -id: 6.9-global-positioning-system-(gps)-approach -title: 6.9 Global Positioning System (GPS) Approach +id: 6.10-global-positioning-system-(gps)-approach +title: 6.10 Global Positioning System (GPS) Approach meta: How to control GPS Approaches within Infinite Flight. -order: 9 +order: 10 --- -# 6.9 Global Positioning System (GPS) Approach +# 6.10 Global Positioning System (GPS) Approach @@ -13,13 +13,13 @@ order: 9 -### 6.9.1 +### 6.10.1 The Global Positioning System (GPS) Approach is a non-precision approach within IF but is not commonly used as functionality is currently limited. If however, pilots request this type of approach, Controllers **should**{.red} try to accommodate this when traffic permits. The GPS Approach is defined by a series of waypoints and altitude restrictions that the pilot will follow to the runway threshold, free of conventional guidance such as a localizer/glideslope etc. -### 6.9.2 +### 6.10.2 When a pilot requests the GPS Approach and this is approved by the Controller (or if the GPS Approach is issued by the Controller), Controllers can expect aircraft to continue on their FPL (or the new FPL if they had a different approach programmed previously). At an appropriate point (such as base), clear the aircraft for the GPS Approach. Vectors, altitude assignments, and/or intercepts **should not**{.red} be required and the pilot is expected to follow their flight plan to the runway threshold. @@ -31,13 +31,13 @@ Tip -### 6.9.3 +### 6.10.3 Once the aircraft is established (this may not be inline with the runway for various GPS Approaches that are offset) Controllers can then hand them off to Tower/Unicom as appropriate. -### 6.9.4 +### 6.10.4 Controllers can favor utilizing vectors in the following cases: @@ -51,7 +51,7 @@ Controllers can favor utilizing vectors in the following cases: -In these instances, Controllers **should**{.red} provide the aircraft with vectors to the Initial Approach Fix (IAF) as a **MINIMUM**; and in **ALL** cases, **must**{.red} ensure that the aircraft is able to establish inbound on the GPS Approach. Once this is assured **AND** the observed track of the aircraft suggests a successful rejoin, the aircraft can be cleared for the GPS Approach (*see [6.9.2](/guide/atc-manual/6.-radar/6.9-global-positioning-system-(gps)-approach#6.9.2) above*). +In these instances, Controllers **should**{.red} provide the aircraft with vectors to the Initial Approach Fix (IAF) as a **MINIMUM**; and in **ALL** cases, **must**{.red} ensure that the aircraft is able to establish inbound on the GPS Approach. Once this is assured **AND** the observed track of the aircraft suggests a successful rejoin, the aircraft can be cleared for the GPS Approach (*see [6.10.2](/guide/atc-manual/6.-radar/6.10-global-positioning-system-(gps)-approach#6.10.2) above*). diff --git a/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach.md b/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach.md similarity index 81% rename from atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach.md rename to atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach.md index ad0eef66..0fd5dafa 100644 --- a/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach.md +++ b/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach.md @@ -1,23 +1,23 @@ --- -id: 6.10-instrument-landing-system-(ils)-approach -title: 6.10 Instrument Landing System (ILS) Approach +id: 6.11-instrument-landing-system-(ils)-approach +title: 6.11 Instrument Landing System (ILS) Approach meta: How to vector aircraft for the ILS Approach in Infinite Flight. -order: 10 +order: 11 --- -# 6.10 Instrument Landing System (ILS) Approach +# 6.11 Instrument Landing System (ILS) Approach ## What is an ILS Approach? -### 6.10.1 +### 6.11.1 The ILS consists of two beams, the Localizer (LOC), providing lateral guidance (left/right) and the Glideslope (G/S) providing vertical guidance (up/down). -### 6.10.2 +### 6.11.2 The cone at the end of a runway provides a **VISUAL AID** for both pilots and Controllers of where the LOC and G/S are, however it is important to remember that the LOC and G/S are not confined to the cone. The LOC and G/S are independent radio ‘signals’ that are sent out, and thus continue to go out. Aircraft can receive these signals and therefore intercept them - both within the cone or outside of the cone. @@ -25,27 +25,27 @@ The cone at the end of a runway provides a **VISUAL AID** for both pilots and Co ## Intercepting the LOC and G/S -### 6.10.3 +### 6.11.3 -To intercept the LOC of an ILS, Controllers **should**{.red} issue an intercept heading *(for exceptions see [6.10.5](/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.5) below)*; this heading **should**{.red} be as close to 30 degrees as possible, offset from the runway designator *(see 6.10.3.1 below)*. The intercept heading needs to give the aircraft a good closing angle to get onto the LOC expeditiously and thus 10 degrees or less **should**{.red} be avoided. Although the standard method for determination of the intercept headings to be used **should**{.red} be based off the runway designator (e.g. for RWY 27, 30 degree intercepts would be headings 240 and 300 as shown in the image below), Controllers may need to take into account the actual runway heading if it is considered significantly different (e.g. KMIA RWY 08R has an actual heading of 092, therefore the ideal intercept headings would be 060 or 120 degrees). +To intercept the LOC of an ILS, Controllers **should**{.red} issue an intercept heading *(for exceptions see [6.11.5](/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.5) below)*; this heading **should**{.red} be as close to 30 degrees as possible, offset from the runway designator *(see 6.11.3.1 below)*. The intercept heading needs to give the aircraft a good closing angle to get onto the LOC expeditiously and thus 10 degrees or less **should**{.red} be avoided. Although the standard method for determination of the intercept headings to be used **should**{.red} be based off the runway designator (e.g. for RWY 27, 30 degree intercepts would be headings 240 and 300 as shown in the image below), Controllers may need to take into account the actual runway heading if it is considered significantly different (e.g. KMIA RWY 08R has an actual heading of 092, therefore the ideal intercept headings would be 060 or 120 degrees). -![Image 6.10.3.1 - Intercepting the localizer](_images/manual/graphics/atc-intercept-loc.jpg) +![Image 6.11.3.1 - Intercepting the localizer](_images/manual/graphics/atc-intercept-loc.jpg) -### 6.10.4 +### 6.11.4 -To intercept the G/S of an ILS, Controllers **must**{.red} issue an altitude that is below the G/S path *(see 6.10.4.1 below).* The typical G/S follows a 3 degree flight path angle that guides the aircraft to the runway threshold. At 1nm the G/S altitude would be 300ft AAL (above aerodrome level); at 2nm, 600ft AAL and so on. +To intercept the G/S of an ILS, Controllers **must**{.red} issue an altitude that is below the G/S path *(see 6.11.4.1 below).* The typical G/S follows a 3 degree flight path angle that guides the aircraft to the runway threshold. At 1nm the G/S altitude would be 300ft AAL (above aerodrome level); at 2nm, 600ft AAL and so on. -![Image 6.10.4.1 - Intercepting the glideslope](_images/manual/graphics/atc-intercept-gs.jpg) +![Image 6.11.4.1 - Intercepting the glideslope](_images/manual/graphics/atc-intercept-gs.jpg) -### 6.10.5 +### 6.11.5 Controllers may issue an ILS approach clearance at an appropriate position without an assigned intercept heading if the aircraft's filed STAR and/or Instrument Approach meet one of the following criteria: @@ -56,7 +56,7 @@ Controllers may issue an ILS approach clearance at an appropriate position witho -In all cases, an appropriate altitude **must**{.red} still be assigned to serve as the lowest authorized altitude until the aircraft is established on the localizer. If a Controller has an advanced understanding of an airport's specific ILS approach plate, the Controller may still issue a clearance without an intercept heading outside of the two conditions listed above. To do this, the Controller **must**{.red} have familiarized themselves with the instrument approach procedure and be able to visually determine when aircraft are established. If in doubt, Controllers **should**{.red} opt for issuing vectors instead *(see [6.10.3](/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.3) above)*. +In all cases, an appropriate altitude **must**{.red} still be assigned to serve as the lowest authorized altitude until the aircraft is established on the localizer. If a Controller has an advanced understanding of an airport's specific ILS approach plate, the Controller may still issue a clearance without an intercept heading outside of the two conditions listed above. To do this, the Controller **must**{.red} have familiarized themselves with the instrument approach procedure and be able to visually determine when aircraft are established. If in doubt, Controllers **should**{.red} opt for issuing vectors instead *(see [6.11.3](/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.3) above)*. @@ -66,9 +66,9 @@ In all cases, an appropriate altitude **must**{.red} still be assigned to serve ## Determining the Intercept Altitude -### 6.10.6 +### 6.11.6 -As already mentioned *(see [6.10.2](/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.2) above)*, the cone is a useful **VISUAL AID** that Controllers can utilize for the ILS or GPS approach. The cones have a standard length of about 11nm and thus the G/S altitude at this point is approximately 3500ft AAL. Although this will assist in determining the best altitudes to use for the intercept, it will also be affected by the following: +As already mentioned *(see [6.11.2](/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.2) above)*, the cone is a useful **VISUAL AID** that Controllers can utilize for the ILS or GPS approach. The cones have a standard length of about 11nm and thus the G/S altitude at this point is approximately 3500ft AAL. Although this will assist in determining the best altitudes to use for the intercept, it will also be affected by the following: @@ -80,7 +80,7 @@ As already mentioned *(see [6.10.2](/guide/atc-manual/6.-radar/6.10-instrument-l -To ensure that aircraft intercept the G/S from below Controllers **must**{.red} use an altitude that is lower than the G/S at the point of interception *(see [6.10.4](/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.4) above)* – by convention, this tends to be 500ft lower but there is no hard rule on this. For example, Airport A has an elevation of 1000ft, therefore the G/S altitude at the end of the cone is approximately 4500ft. Assuming the aircraft is intercepting at the end of the cone, an altitude of 4000ft would be a sensible intercept altitude (based on no terrain to effect apart from the airport elevation). If the aircraft was to intercept further out than the cone, or even within the cone itself, then you will need to adjust the intercept altitude to allow the aircraft to not be above the G/S when intercepting. Without flying the approach before controlling and/or using approach plates, it will be difficult to determine the best altitudes that ensure terrain separation and a good intercept! +To ensure that aircraft intercept the G/S from below Controllers **must**{.red} use an altitude that is lower than the G/S at the point of interception *(see [6.11.4](/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.4) above)* – by convention, this tends to be 500ft lower but there is no hard rule on this. For example, Airport A has an elevation of 1000ft, therefore the G/S altitude at the end of the cone is approximately 4500ft. Assuming the aircraft is intercepting at the end of the cone, an altitude of 4000ft would be a sensible intercept altitude (based on no terrain to effect apart from the airport elevation). If the aircraft was to intercept further out than the cone, or even within the cone itself, then you will need to adjust the intercept altitude to allow the aircraft to not be above the G/S when intercepting. Without flying the approach before controlling and/or using approach plates, it will be difficult to determine the best altitudes that ensure terrain separation and a good intercept! @@ -92,13 +92,13 @@ To ensure that aircraft intercept the G/S from below Controllers **must**{.red} -### 6.10.7 +### 6.11.7 -Controllers **must**{.red} ensure that aircraft continue to meet the IFR separation criteria *(see [6.2.2](/guide/atc-manual/6.-radar/6.2-separation#6.2.2) above)* until they are established on the LOC or lateral guidance *(see [6.13.2](/guide/atc-manual/6.-radar/6.13-handover-to-towerunicom#6.13.2) below)*. Once established, the IFR separation criteria no longer need to be applied between aircraft aligned with parallel runways. +Controllers **must**{.red} ensure that aircraft continue to meet the IFR separation criteria *(see [6.2.2](/guide/atc-manual/6.-radar/6.2-separation#6.2.2) above)* until they are established on the LOC or lateral guidance *(see [6.14.2](/guide/atc-manual/6.-radar/6.14-handover-to-towerunicom#6.14.2) below)*. Once established, the IFR separation criteria no longer need to be applied between aircraft aligned with parallel runways. -### 6.10.8 +### 6.11.8 During parallel operations, lateral separation will always be lost first, therefore during the intercept, only vertical separation can be relied upon. If Controllers identify two or more aircraft that will end up being "parallel" during the final approach, there are two steps that **should**{.red} be followed to ensure the separation requirement above is met: @@ -109,7 +109,7 @@ During parallel operations, lateral separation will always be lost first, theref **Example:** -In the following image *(see 6.10.8.1 below)*, both aircraft are level for the intercept (one at 3000ft and the other at 4000ft). In the example on the left, the aircraft will be established on the LOC before the G/S is met. However in the example on the right, the aircraft have not intercepted the LOC in-line with each other and thus the aircraft that was at 4000ft has already met the G/S and begun their descent. Subsequently, the vertical separation is lost before both aircraft are established on the LOC! +In the following image *(see 6.11.8.1 below)*, both aircraft are level for the intercept (one at 3000ft and the other at 4000ft). In the example on the left, the aircraft will be established on the LOC before the G/S is met. However in the example on the right, the aircraft have not intercepted the LOC in-line with each other and thus the aircraft that was at 4000ft has already met the G/S and begun their descent. Subsequently, the vertical separation is lost before both aircraft are established on the LOC! -![Image 6.10.8.1 - Parallel Operations](_images/manual/graphics/atc-parallel-ops.jpg) +![Image 6.11.8.1 - Parallel Operations](_images/manual/graphics/atc-parallel-ops.jpg) diff --git a/atc-manual/6.-radar/6.11-radar-vectors.md b/atc-manual/6.-radar/6.12-radar-vectors.md similarity index 89% rename from atc-manual/6.-radar/6.11-radar-vectors.md rename to atc-manual/6.-radar/6.12-radar-vectors.md index 128983d5..0b788a8a 100644 --- a/atc-manual/6.-radar/6.11-radar-vectors.md +++ b/atc-manual/6.-radar/6.12-radar-vectors.md @@ -1,15 +1,15 @@ --- -id: 6.11-radar-vectors -title: 6.11 Radar Vectors +id: 6.12-radar-vectors +title: 6.12 Radar Vectors meta: How to provide aircraft with Radar Vectors in Infinite Flight. -order: 11 +order: 12 --- -# 6.11 Radar Vectors +# 6.12 Radar Vectors -### 6.11.1 +### 6.12.1 Radar Vectors are primarily used to put aircraft into the VFR pattern for an airport. Controllers **should**{.red} vector aircraft into a recognizable position (e.g. downwind, base etc.), and before handing over to Tower, descend the aircraft down to pattern altitude (see table below). When aircraft call in following Radar Vectors, Tower **must**{.red} issue a pattern entry, a sequence (if required) and then a clearance. If the runway which is in use has an instrument approach (ILS or GPS), Controllers can vector the aircraft towards the localizer however the aircraft **must**{.red} not be cleared for an approach, but instead handed over to tower who will issue a pattern entry, sequence (if required) and then a clearance. @@ -22,12 +22,12 @@ Radar Vectors are primarily used to put aircraft into the VFR pattern for an air -### 6.11.2 +### 6.12.2 Controllers **must**{.red} check the Airport Elevation of the airfield they are Radar Vectoring an aircraft to so that the correct pattern altitude can be determined; and as always, consideration to surrounding terrain **must**{.red} be taken into account. -### 6.11.3 +### 6.12.3 -If the weather at the airport in question is below VMC (see [3.4](/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4-pattern-work-%2F-transitions-%2F-flight-of-xx) above), then aircraft **must**{.red} be vectored towards the instrument approach for the airport (ILS or GPS), and then handed over to Tower/Unicom at an altitude and position that allows for the aircraft to independently set up for an instrument approach to landing. In this case, descent to pattern altitude is not required, but a suitable altitude **should**{.red} be issued to take into account the position in relation to the airport and G/S (see [6.10.4](/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.4) above). \ No newline at end of file +If the weather at the airport in question is below VMC (see [3.4](/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4-pattern-work-%2F-transitions-%2F-flight-of-xx) above), then aircraft **must**{.red} be vectored towards the instrument approach for the airport (ILS or GPS), and then handed over to Tower/Unicom at an altitude and position that allows for the aircraft to independently set up for an instrument approach to landing. In this case, descent to pattern altitude is not required, but a suitable altitude **should**{.red} be issued to take into account the position in relation to the airport and G/S (see [6.11.4](/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.4) above). \ No newline at end of file diff --git a/atc-manual/6.-radar/6.12-visual-approach.md b/atc-manual/6.-radar/6.13-visual-approach.md similarity index 88% rename from atc-manual/6.-radar/6.12-visual-approach.md rename to atc-manual/6.-radar/6.13-visual-approach.md index 7c5a81cd..cf56d174 100644 --- a/atc-manual/6.-radar/6.12-visual-approach.md +++ b/atc-manual/6.-radar/6.13-visual-approach.md @@ -1,44 +1,44 @@ --- -id: 6.12-visual-approach -title: 6.12 Visual Approach +id: 6.13-visual-approach +title: 6.13 Visual Approach meta: How to provide aircraft with a Visual Approach in Infinite Flight. -order: 12 +order: 13 --- -# 6.12 Visual Approach +# 6.13 Visual Approach -### 6.12.1 +### 6.13.1 A visual approach is an approach to a runway at an aerodrome conducted under IFR but where the pilot proceeds by visual reference when cleared to do so. This means that the pilot **must**{.red} be visual before the Controller can clear the aircraft for the visual approach. To accommodate this, Visual Meteorological Conditions (VMC) **must**{.red} exist for visual approaches to be allowed – for IF only purposes, this is a **MINIMUM** of 3 statute miles (approx. 5000 meters) visibility. -### 6.12.2 +### 6.13.2 Although similar to Radar Vectors, the underlying difference is that when aircraft are under Radar Vectors, they will not receive an approach clearance. Therefore when aircraft call in following Radar Vectors, Tower would issue a pattern entry, a sequence (if required) and then a clearance. Whereas with the visual approach, they do not require a pattern entry because they have been cleared for the approach, therefore only a sequence (if required) and a clearance is issued by Tower. -### 6.12.3 +### 6.13.3 There are multiple ways in which a visual approach can be given to the pilot but generally speaking, and terrain permitting; the aircraft **should**{.red} be positioned in a recognizable position such as downwind, base, or even straight in. The Approach Controller must then ask the aircraft to "report airport in sight" (note that Controllers can still continue to issue vectors to the pilot after requesting the pilot to "report airport in sight"). Once the pilot has responded with the airport in sight, the Approach Controller can clear them for the visual approach (with or without a final vector) and then hand them off to Tower/Unicom as appropriate. -### 6.12.4 +### 6.13.4 -There are some specific procedures for various aerodromes but this relies on both the Controller and pilot using the correct chart. This can be adopted using the same method as already outlined *(see [6.8.6](/guide/atc-manual/6.-radar/6.8-approach#6.8.6) above).* +There are some specific procedures for various aerodromes but this relies on both the Controller and pilot using the correct chart. This can be adopted using the same method as already outlined *(see [6.9.6](/guide/atc-manual/6.-radar/6.9-approach#6.9.6) above).* -### 6.12.5 +### 6.13.5 -The Visual Approach at JFK, New York (KJFK) onto RWY13L/R *(see image 6.12.5.1 below)* is a good example of a specific procedure. For this procedure the Controller would need to vector aircraft towards the start which in this case is the Canarsie (CRI) VOR. The chart requires an inbound heading of 043, so a heading of 040 or similar would be appropriate and the minimum altitude for the approach is 2000ft initially. The pilot can then be instructed to report the airport in sight, and once they have, cleared for the visual approach and handed over to Tower. In this particular case, the aircraft would essentially be handed over on a right base for RWY13L/R, however if the pilot fails to report the airport in sight, further vectors may be required to ensure they continue to follow the prescribed tracks until they have confirmed that they are visual with the airport. +The Visual Approach at JFK, New York (KJFK) onto RWY13L/R *(see image 6.13.5.1 below)* is a good example of a specific procedure. For this procedure the Controller would need to vector aircraft towards the start which in this case is the Canarsie (CRI) VOR. The chart requires an inbound heading of 043, so a heading of 040 or similar would be appropriate and the minimum altitude for the approach is 2000ft initially. The pilot can then be instructed to report the airport in sight, and once they have, cleared for the visual approach and handed over to Tower. In this particular case, the aircraft would essentially be handed over on a right base for RWY13L/R, however if the pilot fails to report the airport in sight, further vectors may be required to ensure they continue to follow the prescribed tracks until they have confirmed that they are visual with the airport. -![Image 6.12.5.1 - KJFK FAA Chart](_images/manual/graphics/kjfk-chart.jpg) +![Image 6.13.5.1 - KJFK FAA Chart](_images/manual/graphics/kjfk-chart.jpg) \ No newline at end of file diff --git a/atc-manual/6.-radar/6.13-handover-to-towerunicom.md b/atc-manual/6.-radar/6.14-handover-to-towerunicom.md similarity index 57% rename from atc-manual/6.-radar/6.13-handover-to-towerunicom.md rename to atc-manual/6.-radar/6.14-handover-to-towerunicom.md index a38c7422..c27d824d 100644 --- a/atc-manual/6.-radar/6.13-handover-to-towerunicom.md +++ b/atc-manual/6.-radar/6.14-handover-to-towerunicom.md @@ -1,36 +1,38 @@ --- -id: 6.13-handover-to-towerunicom -title: 6.13 Handover to Tower/Unicom +id: 6.14-handover-to-towerunicom +title: 6.14 Handover to Tower/Unicom meta: How to hand aircraft over to Tower/Unicom on Infinite Flight. -order: 13 +order: 14 --- -# 6.13 Handover to Tower/Unicom +# 6.14 Handover to Tower/Unicom -### 6.13.1 +### 6.14.1 Before the Controller can hand an aircraft over to Tower/Unicom they **must**{.red} ensure that the aircraft has successfully established on the "intended approach path" **AND** has an acceptable closure rate with the aircraft ahead. -### 6.13.2 +### 6.14.2 -The "intended approach path" for the GPS Approach, Radar Vectors and a Visual Approach are covered above *(see [6.9.3](/guide/atc-manual/6.-radar/6.9-global-positioning-system-(gps)-approach#6.9.3), [6.11.1](/guide/atc-manual/6.-radar/6.11-radar-vectors#6.11.1) and [6.12.3](/guide/atc-manual/6.-radar/6.12-visual-approach#6.12.3) above respectively)*. For the ILS approach, Controllers **must**{.red} ensure that the aircraft has successfully intercepted the LOC, this is especially important when parallel operations are in use *(see 6.13.2.1 below)*. Do not confuse aircraft being established on the LOC, with "being in the cone" – aircraft must be aligned with the centerline of the runway to be established, regardless of their position inside or outside of the cone. +The "intended approach path" for the GPS Approach, Radar Vectors and a Visual Approach are covered above *(see [6.10.3](/guide/atc-manual/6.-radar/6.10-global-positioning-system-(gps)-approach#6.10.3), [6.12.1](/guide/atc-manual/6.-radar/6.12-radar-vectors#6.12.1) and [6.13.3](/guide/atc-manual/6.-radar/6.13-visual-approach#6.13.3) above respectively)*. For the ILS approach, Controllers **must**{.red} ensure that the aircraft has successfully intercepted the LOC, this is especially important when parallel operations are in use *(see 6.14.2.1 below)*. Do not confuse aircraft being established on the LOC, with "being in the cone" – aircraft must be aligned with the centerline of the runway to be established, regardless of their position inside or outside of the cone. -![Image 6.13.2.1 - Radar intercept right vs wrong](_images/manual/graphics/atc-intercept-right-vs-wrong.jpg) +![Image 6.14.2.1 - Radar intercept right vs wrong](_images/manual/graphics/atc-intercept-right-vs-wrong.jpg) -### 6.13.3 + + +### 6.14.3 Radar Controllers **must**{.red} ensure that the aircraft closure rate is "acceptable" and issue speed control if the desired separation cannot be maintained (e.g. if Aircraft A is at 180kts GS on final approach, and Aircraft B is intercepting at 250kts GS with only 3nm spacing, separation could be compromised and result in a go-around). Aircraft **should**{.red} be kept on frequency until separation is assured, this may mean leaving the frequency change until very late! -### 6.13.4 +### 6.14.4 To help with separation on final approach, the use of "maintain XXXkts until X mile final" **should**{.red} be used by Radar Controllers when traffic levels are busy. Aircraft will be expected to reduce their IAS to the specified speed, maintain this until the specified distance has been met and then reduce to their final approach speed following this. diff --git a/atc-manual/6.-radar/6.14-aircraft-speed.md b/atc-manual/6.-radar/6.15-aircraft-speed.md similarity index 87% rename from atc-manual/6.-radar/6.14-aircraft-speed.md rename to atc-manual/6.-radar/6.15-aircraft-speed.md index a50756c6..ab645a0d 100644 --- a/atc-manual/6.-radar/6.14-aircraft-speed.md +++ b/atc-manual/6.-radar/6.15-aircraft-speed.md @@ -1,29 +1,29 @@ --- -id: 6.14-aircraft-speed -title: 6.14 Aircraft Speed +id: 6.15-aircraft-speed +title: 6.15 Aircraft Speed meta: Relationship between Mach Number (M), Indicated Airspeed (IAS) and Groundspeed (GS) on Infinte Flight. -order: 14 +order: 15 --- -# 6.14 Aircraft Speed +# 6.15 Aircraft Speed ## Indicated Airspeed (IAS) Vs. Groundspeed (GS) -### 6.14.1 +### 6.15.1 There is a common misconception between the relationship between Indicated Airspeed (IAS) and Groundspeed (GS). For simplicity the reasons behind the difference are not covered, however there are two things that will ultimately affect the relationship: wind and altitude! -### 6.14.2 +### 6.15.2 Wind: if there is a tailwind of 20kts, that means there is 20kts of wind pushing the aircraft along in addition to its normal speed, so 180kts IAS will become 200kts GS. Similarly, if there is 20kts of headwind, that means there is 20kts of wind pushing against the aircraft, so 180kts IAS becomes 160kts GS. -### 6.14.3 +### 6.15.3 Altitude: as the altitude of aircraft increases, so will the difference between IAS and GS. Below are some very "ball-park" figures which can be used for reference. With the aircraft flying at 250kts IAS with no wind: @@ -34,9 +34,9 @@ Altitude: as the altitude of aircraft increases, so will the difference between -### 6.14.4 +### 6.15.4 -An aircraft's current IAS (Mach Number above FL280) is displayed on their information tab when opened along with other data, all speed commands are referenced to IAS or Mach Number although GS is displayed on the radar screen to assist controllers in the effects of altitude and wind *(see [6.14.2](/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.2) and [6.14.3](/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.3) above)*. +An aircraft's current IAS (Mach Number above FL280) is displayed on their information tab when opened along with other data, all speed commands are referenced to IAS or Mach Number although GS is displayed on the radar screen to assist controllers in the effects of altitude and wind *(see [6.15.2](/guide/atc-manual/6.-radar/6.15-aircraft-speed#6.15.2) and [6.15.3](/guide/atc-manual/6.-radar/6.15-aircraft-speed#6.15.3) above)*. @@ -44,7 +44,7 @@ An aircraft's current IAS (Mach Number above FL280) is displayed on their inform -### 6.14.5 +### 6.15.5 IAS is converted to Mach Number at FL280, with all speed referred to as Mach above this Flight Level. Below is a table that highlights typical cruising Mach Numbers for different aircraft types. Controllers **should**{.red} note that altitude and weight have a huge influence on Mach Number and therefore if aircraft are asked to perform outside of the speed ranges below, the aircraft may be unable to comply: @@ -68,20 +68,20 @@ Tip -### 6.14.6 +### 6.15.6 When issuing speed control to aircraft, Controllers **must**{.red} utilize the following techniques: -- Compensate for closure rate when assigning speed adjustment in an "in-trail" situation by either reducing the trailing aircraft speed first, or increasing the lead aircraft speed first *(see [6.14.7](/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.7) below)* +- Compensate for closure rate when assigning speed adjustment in an "in-trail" situation by either reducing the trailing aircraft speed first, or increasing the lead aircraft speed first *(see [6.15.7](/guide/atc-manual/6.-radar/6.15-aircraft-speed#6.15.7) below)* - Implement specific speed control if required to maintain spacing - Allow sufficient time and distance to achieve speed adjustments (especially at higher altitudes, greater speed differentials and when aircraft are in a clean configuration) -- Ensure that aircraft are able to operate in a clean configuration for as long as possible *(see [6.14.8](/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.8) below)* +- Ensure that aircraft are able to operate in a clean configuration for as long as possible *(see [6.15.8](/guide/atc-manual/6.-radar/6.15-aircraft-speed#6.15.8) below)* -### 6.14.7 +### 6.15.7 It is important to note that if you have only given a speed assignment to a single aircraft (when multiple aircraft are involved), it is unlikely this will provide the necessary separation, for example: @@ -96,18 +96,18 @@ In addition, "Adjust Speed to Follow Aircraft Ahead" can be useful but does not -### 6.14.8 +### 6.15.8 When aircraft slow down, they may need to configure; Controllers **should**{.red} avoid slowing aircraft down where they will have to configure until within 20 track miles to touchdown - expeditious approaches are only possible if aircraft keep their speed up until close to the airport. -### 6.14.9 +### 6.15.9 If aircraft have been holding, once they are cleared to leave the hold, speed is at their discretion unless they are subsequently assigned a speed command. -### 6.14.10 +### 6.15.10 -Once aircraft are cleared for the approach, speed is at their discretion unless they are subsequently assigned a speed command. In this instance Controllers **should**{.red} use the "maintain XXXkts until X mile final" option *(see [6.13.4](/guide/atc-manual/6.-radar/6.13-handover-to-towerunicom#6.13.4) above)*. +Once aircraft are cleared for the approach, speed is at their discretion unless they are subsequently assigned a speed command. In this instance Controllers **should**{.red} use the "maintain XXXkts until X mile final" option *(see [6.14.4](/guide/atc-manual/6.-radar/6.14-handover-to-towerunicom#6.14.4) above)*. diff --git a/atc-manual/6.-radar/6.6-center.md b/atc-manual/6.-radar/6.6-center.md index 1f633836..4d3a7469 100644 --- a/atc-manual/6.-radar/6.6-center.md +++ b/atc-manual/6.-radar/6.6-center.md @@ -95,7 +95,7 @@ Aircraft at cruise may utilize the "Resume Flight" feature if all criteria has b ### 6.6.7 -In the cruise phase speed control is essential in traffic flow management, controllers **must**{.red} ensure that they are familiar with typical Mach cruising speeds for aircraft under their control *(see [6.14.5](/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.5) below)*. An increase or decrease of Mach .01 can change an aircraft's arrival time significantly (dependent on how far ahead the instruction is sent). Therefore to control traffic flow, Center Controllers **should**{.red} utilize speed control where possible (although altitude changes and vectors are always available if required). This will reduce Controller workload and prevent aircraft being taken hundreds of miles off their flight plan. +In the cruise phase speed control is essential in traffic flow management, controllers **must**{.red} ensure that they are familiar with typical Mach cruising speeds for aircraft under their control *(see [6.15.5](/guide/atc-manual/6.-radar/6.15-aircraft-speed#6.15.5) below)*. An increase or decrease of Mach .01 can change an aircraft's arrival time significantly (dependent on how far ahead the instruction is sent). Therefore to control traffic flow, Center Controllers **should**{.red} utilize speed control where possible (although altitude changes and vectors are always available if required). This will reduce Controller workload and prevent aircraft being taken hundreds of miles off their flight plan. @@ -129,7 +129,7 @@ IFR/VFR Semi-circular rules are not implemented, however they are something that ### 6.6.9 -Standard Terminal Arrival Routes, known as STARs, are a published flight procedure that are followed by aircraft on an IFR flight plan from an intermediate altitude. STARs allow aircraft to arrive following a pre-defined route (and in some cases with altitude/speed restrictions) that help them navigate adjacent airspaces, terrain and departing traffic. Controllers **should**{.red} let aircraft continue on a STAR to the maximum extent possible for arrival unless vectors are required for an expeditious service, sequencing or traffic avoidance *(see [6.8.4](/guide/atc-manual/6.-radar/6.8-approach#6.8.4) below)*. +Standard Terminal Arrival Routes, known as STARs, are a published flight procedure that are followed by aircraft on an IFR flight plan from an intermediate altitude. STARs allow aircraft to arrive following a pre-defined route (and in some cases with altitude/speed restrictions) that help them navigate adjacent airspaces, terrain and departing traffic. Controllers **should**{.red} let aircraft continue on a STAR to the maximum extent possible for arrival unless vectors are required for an expeditious service, sequencing or traffic avoidance *(see [6.9.4](/guide/atc-manual/6.-radar/6.9-approach#6.9.4) below)*. diff --git a/atc-manual/6.-radar/6.8-diversion.md b/atc-manual/6.-radar/6.8-diversion.md new file mode 100644 index 00000000..a6546e7e --- /dev/null +++ b/atc-manual/6.-radar/6.8-diversion.md @@ -0,0 +1,26 @@ +--- +id: 6.8-diversion +title: 6.8 Diversion +meta: How to manage diversions within Infinite Flight. +order: 8 +--- + +# 6.8 Diversion + + + +### 6.8.1 + +Aircraft may request to divert at any point throughout their flight while on an active radar frequency. ATC will have the ability to approve or deny this request, advising the aircraft to resume own navigation to the requested airport or to expect radar vectors. + + + +### 6.8.2 + +In congested or complex airspace, aircraft **should**{.red} be given radar vectors to avoid unpredictable pilot actions whilst departing the area. Once clear aircraft can be told to resume own navigation or, workload permitting, Controllers may elect to provide radar services to the divert airport if within your area of jurisdiction. + + + +### 6.8.3 + +Diversion denial **should**{.red} be used *sparingly* and only to prevent diversion to an unsuitable airport or an airport at capacity. diff --git a/atc-manual/6.-radar/6.8-approach.md b/atc-manual/6.-radar/6.9-approach.md similarity index 91% rename from atc-manual/6.-radar/6.8-approach.md rename to atc-manual/6.-radar/6.9-approach.md index 4674110d..0f7c2c52 100644 --- a/atc-manual/6.-radar/6.8-approach.md +++ b/atc-manual/6.-radar/6.9-approach.md @@ -1,11 +1,11 @@ --- -id: 6.8-approach -title: 6.8 Approach +id: 6.9-approach +title: 6.9 Approach meta: How to control Approach within Infinite Flight. -order: 8 +order: 9 --- -# 6.8 Approach +# 6.9 Approach @@ -17,43 +17,43 @@ Tip ## What is Approach? -### 6.8.1 +### 6.9.1 Approach airspace is from surface up to FL180 and 50nm around the airport although airport elevation can be taken into account if it is deemed significant *(see [5.2.1](/guide/atc-manual/5.-airspace/5.2-on-guard-procedures#5.2.1) above)*. Below is a checklist of what you **must**{.red} be aware of **BEFORE** opening an approach facility (it is also recommended to fly the approach yourself, this will enable you to determine the ideal altitudes and vectors required for a good approach service): - - Airport Elevation: By determining what the elevation is, this can be used to find the best intercept altitudes *(see [6.10.5](/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.5) below)* + - Airport Elevation: By determining what the elevation is, this can be used to find the best intercept altitudes *(see [6.11.5](/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.5) below)* - Runway Exits: Rapid Exit Taxiways (RETs) will allow aircraft to exit the runway quicker than a 90 degree exit or if the aircraft has to back-taxi to exit, this **must**{.red} be taken into account when spacing aircraft on final approach - If there are Controllers on the tower frequencies under your coverage area, liaise with them to confirm departure/arrival strategies and runway(s) in use. In addition, make prior arrangements with other Radar Controllers for handover points, altitudes, and headings when aircraft are travelling between airports *(see [3.6.1](/guide/atc-manual/3.-tower/3.6-tower-working-with-radar#3.6.1) above)* - - Airport Plates: Controllers **should**{.red} access approach plates for the airfield as it will increase your situational awareness, and in particular; terrain awareness *(see [6.8.6](/guide/atc-manual/6.-radar/6.8-approach#6.8.6) below)* + - Airport Plates: Controllers **should**{.red} access approach plates for the airfield as it will increase your situational awareness, and in particular; terrain awareness *(see [6.9.6](/guide/atc-manual/6.-radar/6.9-approach#6.9.6) below)* ## STARs and Initial Vectoring -### 6.8.2 +### 6.9.2 It is important to note that most STARs normally occur in Approach airspace *(see [5.1.1](/guide/atc-manual/5.-airspace/5.1-airspace#5.1.1) above)*, however if Center controllers are present, coordination **must**{.red} take place between **ALL** controllers involved to ensure a seamless service is provided. -### 6.8.3 +### 6.9.3 On initial contact with Approach, aircraft are expected to make their approach request. If the aircraft has already been cleared to descend via the STAR from a previous Controller, it will be visible on their flight progress strip *(see [6.6.11](/guide/atc-manual/6.-radar/6.6-center#6.6.11) above)*, Approach Controllers **should**{.red} respond with "Continue as Filed, Expect the [approach type/runway] at [location]" if they wish the aircraft to continue as previously cleared. If the aircraft was previously receiving vectors, was not approved for descent via the STAR or the Controller wants to issue vectors/altitude assignments, then "Expect Vectors for the [approach type/runway] at [location]" **should**{.red} be used instead. In the absence of Center, aircraft who have already begun their initial descent via a STAR may continue their descent with the response "Continue as Filed, Expect the [approach type/runway] at [location]" without a specific descent via clearance *(see [6.6.12](/guide/atc-manual/6.-radar/6.6-center#6.6.12) above)*. -### 6.8.4 +### 6.9.4 -Controllers **should**{.red} let aircraft continue on a STAR to the maximum extent possible for arrival unless vectors are required for an expeditious service, sequencing or traffic avoidance *(see [6.8.5](/guide/atc-manual/6.-radar/6.8-approach#6.8.5) below)*. The Controller can select preferred STARs, offering a variety of authorized procedures from different directions *(see [4.2.2](/guide/atc-manual/4.-atis/4.2-remarks-and-notams#4.2.2) above)*; aircraft not on a preferred STAR **should**{.red} be instructed to "Amend Flight Plan to Include Preferred STAR at Destination" *(see [6.6.8](/guide/atc-manual/6.-radar/6.6-center#6.6.8) above)*, unless the aircraft is established in the descent *(see [6.6.12](/guide/atc-manual/6.-radar/6.6-center#6.6.12) above)*. +Controllers **should**{.red} let aircraft continue on a STAR to the maximum extent possible for arrival unless vectors are required for an expeditious service, sequencing or traffic avoidance *(see [6.9.5](/guide/atc-manual/6.-radar/6.9-approach#6.9.5) below)*. The Controller can select preferred STARs, offering a variety of authorized procedures from different directions *(see [4.2.2](/guide/atc-manual/4.-atis/4.2-remarks-and-notams#4.2.2) above)*; aircraft not on a preferred STAR **should**{.red} be instructed to "Amend Flight Plan to Include Preferred STAR at Destination" *(see [6.6.8](/guide/atc-manual/6.-radar/6.6-center#6.6.8) above)*, unless the aircraft is established in the descent *(see [6.6.12](/guide/atc-manual/6.-radar/6.6-center#6.6.12) above)*. -### 6.8.5 +### 6.9.5 At any time if you do issue a vector and/or altitude assignment and then want the aircraft to return to their flight plan, you **should**{.red} let the pilot know by sending "Continue as Filed" and/or "Altitude at your Discretion" respectively. Traffic and terrain permitting, aircraft **must**{.red} be given the most direct routing possible, and therefore **should not**{.red} be made to fly a full STAR procedure when these conditions exist. @@ -61,31 +61,31 @@ At any time if you do issue a vector and/or altitude assignment and then want th ## Approach Charts -### 6.8.6 +### 6.9.6 Approach charts can generally be found online by searching in any search engine for "approach charts" with the related ICAO code; Controllers **should**{.red} familiarize themselves with how to read these charts as it will increase the Controller’s situational awareness. -### 6.8.7 +### 6.9.7 -The MSA (Minimum Sector Altitude) is an area in which an aircraft can be safely vectored and have guaranteed terrain clearance provided the aircraft is not cleared below the altitude displayed within that sector. Most Charts have an MSA displayed *(see 6.8.7.1 below)* within segments of a circle (normally based around the airport itself or a navigation aid). Each segment contains an altitude which will guarantee terrain separation but Controllers can vector aircraft below this altitude if terrain clearance is assured. +The MSA (Minimum Sector Altitude) is an area in which an aircraft can be safely vectored and have guaranteed terrain clearance provided the aircraft is not cleared below the altitude displayed within that sector. Most Charts have an MSA displayed *(see 6.9.7.1 below)* within segments of a circle (normally based around the airport itself or a navigation aid). Each segment contains an altitude which will guarantee terrain separation but Controllers can vector aircraft below this altitude if terrain clearance is assured. -![Image 6.8.7.1 - KSFO FAA Chart](_images/manual/graphics/ksfo-chart.jpg) +![Image 6.9.7.1 - KSFO FAA Chart](_images/manual/graphics/ksfo-chart.jpg) -### 6.8.8 +### 6.9.8 -From the image *(see 6.8.7.1 above)* it can be assumed that aircraft approaching from the North will be clear of terrain down to 5100ft, aircraft from the South down to 4500ft and aircraft from out over the sea down to 3500ft. By flying the approach yourself before you control there, you can continue to build a full picture. Where are the high points of terrain, what is the best intercept altitude and so on. +From the image *(see 6.9.7.1 above)* it can be assumed that aircraft approaching from the North will be clear of terrain down to 5100ft, aircraft from the South down to 4500ft and aircraft from out over the sea down to 3500ft. By flying the approach yourself before you control there, you can continue to build a full picture. Where are the high points of terrain, what is the best intercept altitude and so on. ## Flight Plan Approach Prefixes -### 6.8.9 +### 6.9.9 If a published approach has been selected by a pilot, this will be visible to the Controller within the pilot's flight plan. The following prefixes are used to help differentiate between the different approaches available at an airport: diff --git a/atc-manual/7.-recruitment-and-training/7.1-overview.md b/atc-manual/7.-recruitment-and-training/7.1-overview.md index a3a48034..6d18efc0 100644 --- a/atc-manual/7.-recruitment-and-training/7.1-overview.md +++ b/atc-manual/7.-recruitment-and-training/7.1-overview.md @@ -54,7 +54,7 @@ All aspects of controlling are trained but Trainees **should**{.red} be aware of ### 7.1.5 -The *#training-time* Discord channels are used by Trainers to coordinate training sessions for Recruits by announcing how many pilots are required to join, and in which channel. Controllers that wish to participate in these training sessions by flying can opt in to notifications by "reacting" to the relevant role in the *#role-assignments* Discord channel *(see [1A.1.2](/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.2) above)*. +The *#training-time* Discord channels are used by Trainers to coordinate training sessions for a Trainee by announcing how many pilots are required to join, and in which channel. Controllers that wish to participate in these training sessions by flying can opt in to notifications by "reacting" to the relevant role in the *#role-assignments* Discord channel *(see [1A.1.2](/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.2) above)*. diff --git a/atc-manual/7.-recruitment-and-training/7.3-tower-written-and-practical-tests.md b/atc-manual/7.-recruitment-and-training/7.3-tower-written-and-practical-tests.md index 5e989825..4cba828b 100644 --- a/atc-manual/7.-recruitment-and-training/7.3-tower-written-and-practical-tests.md +++ b/atc-manual/7.-recruitment-and-training/7.3-tower-written-and-practical-tests.md @@ -15,7 +15,7 @@ order: 3 ### 7.3.1 -The minimum requirements for joining IFATC, application instructions and the time limit for re-test if unsuccessful, are outlined on the IFC channel [here](https://community.infiniteflight.com/t/infinite-flight-atc-recruiting/564656). +The minimum requirements for joining IFATC, application instructions and the time limit for re-test if unsuccessful, are outlined on the IFC channel [here](https://community.infiniteflight.com/t/atc-recruiting/843545). @@ -23,13 +23,13 @@ Controllers **must**{.red} ensure they meet the minimum requirements **BEFORE AP -[APPLY NOW](/join-ifatc){.button} +[APPLY NOW](/joinatc){.button} ### 7.3.2 -Recruits are allowed to go through the full recruitment process as outlined within the IFC channel without any training if they wish to do so. However, The Training Team is available **should**{.red} they wish to utilize this resource. To ensure Recruits are committed to joining, training **must not**{.red} be provided until the trainee has passed the Tower Written Test as a **MINIMUM**. +Recruits are allowed to go through the full recruitment process as outlined within the IFC channel without any training if they wish to do so. However, The Training Team is available **should**{.red} they wish to utilize this resource. To ensure Recruits are committed to joining, training **must not**{.red} be provided until the Recruit has passed the Tower Written Test as a **MINIMUM**. @@ -37,11 +37,11 @@ Recruits are allowed to go through the full recruitment process as outlined with -### 7.3.3 +### 7.3.3 + +Following successful completion of the Tower Written Test, Recruits will be given the option to have training. If accepted, a Trainer will be in contact within 7 days to commence training with the Recruit. Trainees will be afforded 15 training sessions. Upon reaching 15 sessions, the training team will review overall progress to determine preparedness for testing, need for termination, or will allocate more sessions to reach the skill level required for certification. -Following successful completion of the Tower Written Test, Recruits will be given the option to have training. If accepted, a Trainer will be in contact within 7 days to commence training with the Recruit. - ### 7.3.4 diff --git a/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests.md b/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests.md index 45e8952e..c413a909 100644 --- a/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests.md +++ b/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests.md @@ -34,36 +34,42 @@ Controllers **must**{.red} ensure they meet the minimum requirements **BEFORE AP -[APPLY NOW](/join-ifatc){.button} +[APPLY NOW](/joinatc){.button} -### 7.4.2 +### 7.4.2 -All training is considered optional with the exception of Radar Training – Controllers that wish to upgrade to Radar **must**{.red} have training, and meet the standards required *(see [7.4.4](/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.4) below)* **BEFORE** the Radar Practical Test. +After submitting an application, a Recruiter will conduct a review on the performance of the Controller. The requirements laid out within this section *(see [7.4.1](/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.1) above)* will assist the Recruiter in gauging the Controller’s competency and suitability for the role. If the review is deemed successful, the Controller will be given the Radar Written Test. To ensure Recruits are ready, training **must not**{.red} be provided until the Recruit has passed the Radar Written Test as a **MINIMUM**. If the Controller is considered not to be ready, a set waiting period (minimum of 30 days) will be assigned where the Controller **must**{.red} endeavor to address the feedback given. Subsequent reviews will continue until there is no doubt that they are ready for the position. ### 7.4.3 -A Recruiter will conduct a review on the performance of the Controller that has requested Radar Training. The requirements laid out within this section *(see [7.4.1](/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.1) above)* will assist the Recruiter in gauging the Controller’s competency and suitability for the role. If the review is deemed successful, the Controller will be placed in the "Training Waitlist" ready for Trainer allocation. If the Controller is considered not to be ready, a set waiting period (minimum of 30 days) will be assigned where the Controller **must**{.red} endeavor to address the feedback given. Subsequent reviews will continue until there is no doubt that they are ready for the position. +After successful completion of the Radar Written Test, the Recruit will be placed in the "Training Waitlist" ready for Trainer allocation. Training for the rank of Officer is mandatory and **must**{.red} be successfully completed **BEFORE** the Radar Practical Test. ### 7.4.4 -Following a successful review, a Trainer will assign themselves to the Recruits application and Radar Training will then commence (training for the position of Radar is mandatory). At an appropriate point during training, as decided by the Trainer; the Recruiter will issue the Radar Written Test and Radar Practical Test (and debrief as appropriate on the results - *see [7.1.1](/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.1) above*). The Radar Practical Test will only be organized once the Radar Written Test has been passed and the Trainer is satisfied that the Trainee is ready. Controlling on the Training Server is only permitted with the explicit permission of a Trainer - this will only be authorized if Trainees have met the requirements for upgrade to the rank of Officer *(see [1A.6.4](/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.4) above)*, and have **STARTED** their Radar Training with a Trainer. +A Trainer will assign themselves to the Recruits application and Radar Training will then commence. The Radar Training program will consist of structured training sessions designed to teach basic radar fundamentals and techniques in a variety of airport environments. Trainees will be afforded 20 training sessions. Upon reaching 20 sessions, the training team will review overall progress to determine preparedness for testing, need for termination, or will allocate more sessions to reach the skill level required for certification. -### 7.4.5 +### 7.4.5 -Whilst under Training, Trainees may wish to seek fellow Controllers to fly radar patterns on the IFATC Server for extra practice if the Trainer is not available. Provided the Trainee has the Trainer’s permission, the use of the Discord *#training-time* channel is authorized to try and find Controllers that are free. +At an appropriate point during training, as decided by the Trainer; the Recruiter will issue the Radar Practical Test (and debrief as appropriate on the results - *see [7.1.1](/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.1) above*). The Radar Practical Test will only be organized once the Trainer is satisfied that the Trainee is ready. Controlling on the Training Server is only permitted with the explicit permission of a Trainer - this will only be authorized if Trainees have met the requirements for upgrade to the rank of Officer *(see [1A.6.4](/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.4) above)*, and have **STARTED** their Radar Training with a Trainer. ### 7.4.6 +Whilst under Training, Trainees may wish to seek fellow Controllers to fly radar patterns on the IFATC Server for extra practice if the Trainer is not available. Provided the Trainee has the Trainer’s permission, the use of the Discord *#training-time* channel is authorized to try and find Controllers that are free. + + + +### 7.4.7 + All aircraft present at the Radar Practical Test **must**{.red} fly in accordance with the radar service being provided; in addition, any aircraft type can be selected but it **must**{.red} be deemed suitable to meet the training objective. The following table lists the items that are included in the Radar Practical test: @@ -82,14 +88,14 @@ All aircraft present at the Radar Practical Test **must**{.red} fly in accordanc -### 7.4.7 +### 7.4.8 -Recruits that are successful in the Radar Practical Test will be promoted and placed in the Officer Check Ride phase *(see [1A.7.8](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.8) above)*. +Recruits that are successful in the Radar Practical Test will be promoted and placed in the Officer Check Ride phase *(see [1A.7.6](/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.6) above)*. -### 7.4.8 +### 7.4.9 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) diff --git a/atc-manual/7a.-trainers/7a.2-training-structure.md b/atc-manual/7a.-trainers/7a.2-training-structure.md index 5f70999e..74fca003 100644 --- a/atc-manual/7a.-trainers/7a.2-training-structure.md +++ b/atc-manual/7a.-trainers/7a.2-training-structure.md @@ -83,7 +83,7 @@ Step 7 ->For Radar Trainee's, Trainers **must**{.red} inform the assigned Recruiter when the Trainee is ready for the Radar Written and Practical Tests +>For Radar Trainee's, Trainers **must**{.red} inform the assigned Recruiter when the Trainee is ready for the Radar Practical Test +++ @@ -103,7 +103,20 @@ Trainers **must**{.red} utilize the "Add Session" function (and ensure "Training ### 7A.2.5 -Trainers reserve the right to terminate training at any point *(see [7.1.4](/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.4) above)*, but **should**{.red} speak to the Trainee's Recruiter **BEFORE** termination as this may effect the Trainee's eligibility for joining IFATC (or future promotions if already within IFATC). A two strike policy is normally observed allowing the Trainee the benefit of the doubt when mistakes are made however appeals may be reviewed by the Training Team Administrator and/or the IFATC Manager on a case-by-case basis. +The maximum amount of training sessions allowed before a review of trainee performance are listed below: + +| Trainee Type | Maximum Training Sessions | +| ------------ | ------------------------- | +| Tower | 15 | +| Radar | 20 | + +Upon reaching the session limit, the training team will review overall progress to determine preparedness for testing, need for termination, or will allocate more sessions to reach skill level required for certification. + + + +### 7A.2.6 + +Trainers reserve the right to terminate training at any point *(see* *[7.1.4](https://infiniteflight.com/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.4)* *above)*, but **should** speak to the Trainee’s Recruiter **BEFORE** termination as this may effect the Trainee’s eligibility for joining IFATC (or future promotions if already within IFATC). A two strike policy is normally observed allowing the Trainee the benefit of the doubt when mistakes are made however appeals may be reviewed by the Training Team Administrator and/or the IFATC Manager on a case-by-case basis. @@ -119,13 +132,13 @@ Reasons for termination can include (but are not limited to): ## Recommended Training Airports -### 7A.2.6 +### 7A.2.7 For Tower Training, Trainers **should**{.red} conduct training at airports with parallel and/or intersecting runways depending on the circumstances of their Trainees. -### 7A.2.7 +### 7A.2.8 The following list outlines recommended airports for Radar Training (Trainers are encouraged to rotate through each site on a consistent basis). Trainers **must not**{.red} train (or allow training to take place) at test sites in order to avoid any unfair advantages *(see [7B.2.1](/guide/atc-manual/7b.-testers/7b.2-tower-testing#7b.2.1) and [7B.3.2](/guide/atc-manual/7b.-testers/7b.3-radar-testing#7b.3.2) below)*: @@ -270,7 +283,7 @@ Recommended STARs: AVSA1C (North), and TIKE1C (North-west) ## Training Complete Checklist -### 7A.2.8 +### 7A.2.9 Before approving any Trainee to conduct a Practical Test, Trainers **must**{.red} consult the following checklists to ensure that all necessary materials are covered before the Trainee proceeds forward: diff --git a/atc-manual/7b.-testers/7b.1-testing-process.md b/atc-manual/7b.-testers/7b.1-testing-process.md index 5ac6aee9..fc45f632 100644 --- a/atc-manual/7b.-testers/7b.1-testing-process.md +++ b/atc-manual/7b.-testers/7b.1-testing-process.md @@ -10,6 +10,10 @@ auth: testers +> All Testers **must**{.red} ensure that "in-progress airports" are hidden to ensure that taxiway networks are the same for both Testers and Recruits, thus avoiding confusion (Settings > Hide in-progress airports) + + + ### 7B.1.1 All tests (regardless of position) are conducted by Recruiters and issued based on the given materials and/or scenarios provided in this section. Testing scenarios will vary from one recruit to the next. This is to ensure that Recruits are better prepared for a wide array of situations found in the Expert Server environment. Care should be taken by the Recruiter(s) to avoid issuing the same testing scenario repeatedly. Only those involved in the test **should**{.red} attend (unless previously authorized for a specific purpose) - an audience is not authorized. diff --git a/atc-manual/7b.-testers/7b.2-tower-testing.md b/atc-manual/7b.-testers/7b.2-tower-testing.md index 57747849..5ae07c11 100644 --- a/atc-manual/7b.-testers/7b.2-tower-testing.md +++ b/atc-manual/7b.-testers/7b.2-tower-testing.md @@ -10,7 +10,7 @@ auth: testers -> Trainers **must not**{.red} train (or allow training to take place) at test sites in order to avoid any unfair advantages *(see [7A.2.6](/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.6) above)* +> Trainers **must not**{.red} train (or allow training to take place) at test sites in order to avoid any unfair advantages *(see [7A.2.8](/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.8) above)* @@ -24,7 +24,7 @@ The following scenarios and locations are pre-approved Tower test sites and are **Locations:** See Discord channel "pinned post" for locations -**Maximum Aircraft Limit:** 7 +**Maximum Aircraft Limit:** 6 **Description:** Majority of Testers spawn at test airport and wait for the test to begin before taxiing to create ground conflict and complexity. 1 Tester will depart a nearby airport to make a transition request. 1 Tester may depart from a nearby airport to call inbound for pattern work @@ -38,7 +38,7 @@ The following scenarios and locations are pre-approved Tower test sites and are **Locations:** See Discord channel "pinned post" for locations -**Maximum Aircraft Limit:** 7 +**Maximum Aircraft Limit:** 6 **Description:** Majority of Testers will spawn at nearby airports and will call inbound to tower for pattern work. 1-2 Testers should spawn at the test airport and remain in the traffic pattern prior to the inbound aircraft’s arrival. Testers may do full stop and taxi back to create a workload on both tower & ground simultaneously diff --git a/atc-manual/7b.-testers/7b.3-radar-testing.md b/atc-manual/7b.-testers/7b.3-radar-testing.md index cdec46bc..b10ac346 100644 --- a/atc-manual/7b.-testers/7b.3-radar-testing.md +++ b/atc-manual/7b.-testers/7b.3-radar-testing.md @@ -10,7 +10,7 @@ auth: testers -> Trainers **must not**{.red} train (or allow training to take place) at test sites in order to avoid any unfair advantages *(see [7A.2.7](/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.7) above)* +> Trainers **must not**{.red} train (or allow training to take place) at test sites in order to avoid any unfair advantages *(see [7A.2.8](/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.8) above)* diff --git a/atc-manual/7c.-recruiters/7c.1-overview.md b/atc-manual/7c.-recruiters/7c.1-overview.md index e1707ad5..dce98a83 100644 --- a/atc-manual/7c.-recruiters/7c.1-overview.md +++ b/atc-manual/7c.-recruiters/7c.1-overview.md @@ -31,6 +31,10 @@ Recruiters are selected by the IFATC Manager based on a number of criteria, incl +Any Controller considered **must**{.red} hold the rank of Officer as a minimum in order to qualify (this is to guarantee that all components of the testing program can be administered). + + + ### 7C.1.3 The following table outlines the minimum notice period that **must**{.red} be given to a Recruit before their Tower or Radar Practical Test (including the test location): @@ -157,6 +161,8 @@ The following are examples of situations where it may be considered appropriate Violations **must**{.red} be issued for blatant offenses to the point where pilots on the Expert Server are being negatively affected by the actions of other pilots. + + Taxiing through other aircraft, landing on top of aircraft/failure to go around, going too fast in a controlled environment, and/or other clearly distinguishable acts of interference are some of the most common reasons to issue a Violation in the absence of a Controller. diff --git a/atc-manual/7c.-recruiters/7c.2-recruitment-process.md b/atc-manual/7c.-recruiters/7c.2-recruitment-process.md index eae50de0..b5810117 100644 --- a/atc-manual/7c.-recruiters/7c.2-recruitment-process.md +++ b/atc-manual/7c.-recruiters/7c.2-recruitment-process.md @@ -42,7 +42,7 @@ Step 4 : Select the Recruit you would like to accept by tapping the orange "Assign Yourself" button (Recruiters **should**{.red} consider the timezone of the Recruit before accepting to ensure it is workable) -> The Recruiter will be added to the PM with the Recruit on the IFC +> The Recruiter will then need to send the Recruit a PM (this can be done either via Discord or the IFC) @@ -98,8 +98,8 @@ Step 11 > For the radar certification process, Recruiters are only required to: > -> - review the Recruit before approving their training -> - and to administer the Radar Written and Practical Tests (subject to Trainer approval) +> - review the Recruit and to administer the Radar Written test before approving their training +> - and to administer the Radar Practical test (subject to Trainer approval) > > Recruiters **should not**{.red} be required for other functions however reserve the right to terminate the radar process of a Trainee if necessary @@ -127,8 +127,6 @@ Step 4 : Select the Recruit you would like to accept by tapping the orange "Assign Yourself" button (Recruiters **should**{.red} consider the timezone of the Recruit before accepting to ensure it is workable) -> The Recruiter will be added to the PM with the Recruit on the IFC - Step 5 @@ -151,21 +149,15 @@ Step 7 Step 8 -: This action will open up their "ATC Recruitment" profile. If they have been approved, training can be requested, otherwise they **must**{.red} be informed of the agreed waiting time before their application will be reviewed again, and any areas for improvement - - - -Step 9 - -: Once the Trainer has confirmed that the Trainee is ready to take the Radar Written Test, the Recruiter can return to the "ATC Recruitment" profile of the Trainee to assign it +: This action will open up their "ATC Recruitment" profile where the Radar Written Test can be assigned if they have been approved, otherwise they **must**{.red} be informed of the agreed waiting time before their application will be reviewed again, and any areas for improvement > The Recruiter will need to send a PM to the Trainee with instructions, a unique link (this is copied to your clipboard when tapping "Assign Written Test" and can just be pasted into the PM), and the test code *terrainpullup* to complete the Written Test -Step 10 +Step 9 -: Once they have completed the Radar Written Test, they are instructed to message the Recruiter in the PM that has already been created with any questions they have. Provided they have passed, they can continue training and the Trainer will advise when they are ready to complete the Radar Practical Test +: Once they have completed the Radar Written Test, they are instructed to message the Recruiter in the PM that has already been created with any questions they have. Provided they have passed, they can commence training and the Trainer will advise when they are ready to complete the Radar Practical Test diff --git a/atc-manual/7c.-recruiters/7c.4-written-test.md b/atc-manual/7c.-recruiters/7c.4-written-test.md index 6d5b666a..194b201e 100644 --- a/atc-manual/7c.-recruiters/7c.4-written-test.md +++ b/atc-manual/7c.-recruiters/7c.4-written-test.md @@ -23,13 +23,13 @@ Once a Recruit has taken the Tower Written Test, the final score will determine | 00 - 49% | 30 days | | 50 - 79% | 14 days | -> Three failed attempts at the Tower Written Test results in a 90 day wait period to restart the process. This may be modified at Recruiter and/or IFATC Manager discretion if necessary +> Three failed attempts at the Tower Written Test results in a 90 day wait period to restart the process. This may be modified at Recruiter and/or IFATC Manager discretion if necessary. Recruiters **must**{.red} use the "pause application" function on the dashboard with a 90 day cooldown (and ensure that a user note is added with the reasoning) Tip -: Once a Recruit passes the Tower Written Test, they will become eligible for training if they want it. Recruiters **must**{.red} ensure that Recruits are aware of this *(see [7.3.2](/guide/atc-manual/7.-recruitment-and-training/7.3-tower-written-and-practical-tests#7.3.2) above)*. Trainers **should**{.red} inform Recruiters if a Trainee's performance is of concern, and if this has resulted in termination of training. Recruiters will then have discretion as to whether this effects the Trainee's eligibility criteria to join the IFATC Team *(see [7A.2.5](/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.5) above)* +: Once a Recruit passes the Tower Written Test, they will become eligible for training if they want it. Recruiters **must**{.red} ensure that Recruits are aware of this *(see [7.3.2](/guide/atc-manual/7.-recruitment-and-training/7.3-tower-written-and-practical-tests#7.3.2) above)*. Trainers **should**{.red} inform Recruiters if a Trainee's performance is of concern, and if this has resulted in termination of training. Recruiters will then have discretion as to whether this effects the Trainee's eligibility criteria to join the IFATC Team *(see [7A.2.6](/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.6) above)* @@ -37,7 +37,7 @@ Tip ### 7C.4.2 -Once a Recruit has taken the Radar Written Test, the final score will determine whether or not the process can continue. A **pass mark of 70% or more must**{.red} be achieved to move onto the Radar Practical Test (provided the Trainer has endorsed* this). The following wait periods are required if a Recruit does not pass: +Once a Recruit has taken the Radar Written Test, the final score will determine whether or not the process can continue. A **pass mark of 70% or more must**{.red} be achieved to move onto Radar Training and the Radar Practical Test (provided the Trainer has endorsed* this). The following wait periods are required if a Recruit does not pass: @@ -50,5 +50,5 @@ Once a Recruit has taken the Radar Written Test, the final score will determine -**Once the Radar Written Test has been passed, the Recruit **must**{.red} have the permission of the Trainer to move onto the Radar Practical Test, further training may be required before the Controller can progress* +**Once the Radar Written Test has been passed, the Recruit **must**{.red} complete Radar Training and have the permission of the Trainer to move onto the Radar Practical Test* diff --git a/atc-manual/7c.-recruiters/7c.5-practical.md b/atc-manual/7c.-recruiters/7c.5-practical.md index 95bf0535..7ba07885 100644 --- a/atc-manual/7c.-recruiters/7c.5-practical.md +++ b/atc-manual/7c.-recruiters/7c.5-practical.md @@ -54,7 +54,7 @@ Provided that both the Tower Written and Practical Tests have been passed, the R ### 7C.5.5 -Once the Radar Written Test has been successfully passed, the Recruit can move onto the Radar Practical Test following permission from their Trainer *(see [7B.1](/guide/atc-manual/7b.-testers/7b.1-testing-process#7b.1-testing-process) and [7B.3](/guide/atc-manual/7b.-testers/7b.3-radar-testing#7b.3-radar-testing) above)*. Recruiters **must**{.red} ensure that the Recruit is provided with adequate notice, including a time and location of the test once this has been agreed *(see [7C.1.3](/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.3) above)*. If the Recruit has been trained by the Recruiter, another Recruiter **should**{.red} administer the test *(see [7C.1.4](/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.4) above)*. +Once the Radar Written Test and Radar Training have been successfully passed, the Recruit can move onto the Radar Practical Test *(see [7B.1](/guide/atc-manual/7b.-testers/7b.1-testing-process#7b.1-testing-process) and [7B.3](/guide/atc-manual/7b.-testers/7b.3-radar-testing#7b.3-radar-testing) above)*. Recruiters **must**{.red} ensure that the Recruit is provided with adequate notice, including a time and location of the test once this has been agreed *(see [7C.1.3](/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.3) above)*. If the Recruit has been trained by the Recruiter, another Recruiter **should**{.red} administer the test *(see [7C.1.4](/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.4) above)*. @@ -84,11 +84,11 @@ On completion of the Radar Practical test, the Recruiter **must**{.red} inform t | Marginal | 14 days | | Undetermined | Recruiter Discretion | -> Three failed attempts at the Radar Practical Test results in a 90 day wait period (although restarting the process is not required and can continue after the wait period expires) +> Three failed attempts at the Radar Practical Test results in a 90 day wait period (although restarting the process is not required and can continue after the wait period expires). Recruiters **must**{.red} use the "pause application" function on the dashboard with a 90 day cooldown (and ensure that a user note is added with the reasoning) ### 7C.5.8 -Provided that both the Radar Written and Practical Tests have been passed, the Recruit can be promoted to the rank of Officer (this process is automatic when the "Passed Practical" button is tapped within the Recruits "ATC Recruitment" profile). +Provided that the Radar Written Test, Radar Training and Radar Practical Test have been passed, the Recruit can be promoted to the rank of Officer (this process is automatic when the "Passed Practical" button is tapped within the Recruits "ATC Recruitment" profile). diff --git a/atc-manual/index.md b/atc-manual/index.md index 6ce91daa..db51b30d 100644 --- a/atc-manual/index.md +++ b/atc-manual/index.md @@ -8,7 +8,7 @@ meta: Introduction to the Infinite Flight Air Traffic Controller (IFATC) Manual. -## Guide Version: 24.1.0 +## Guide Version: 24.2.0 @@ -26,13 +26,47 @@ Should -## ATC Manual Version (Internal): 24.1.1 +## ATC Manual Version (Internal): 24.2.1 -## Last Updated: 1200Z - 02 JAN 24 +## Last Updated: 1515Z - 15 MAR 24 -+++ Summary of Changes - Version: 24.1.1 (CURRENT VERSION) ++++ Summary of Changes - Version: 24.2.1 (CURRENT VERSION) + +| Location | Change | +| ------------------------ | ------------------------------------------------------------ | +| 1A.3.1 | Controllers are not to tag Controllers that are currently open on an active frequency | +| 1A.6.1 | B airports added to Apprentice rank | +| 1A.6.2 | More detail on the Apprentice entry rank into IFATC | +| 1A.6.3 - 1A.6.5 | Renumbered to make space for 1A.6.2 | +| 1A.6.4 | To commence radar training, Controllers now apply online and do not need to contact a Recruiter | +| 1A.6.6 | Guidance on returning members of IFATC that apply for the rank of Officer | +| 1A.6.7 - 1A.6.8 | Renumbered to make space for 1A.6.6 | +| 1A.7 | Section rewritten and new max arrival counts added | +| 2.2.3 | More guidance on the use of Drag & Taxi feature | +| 2.2.4 / 2.2.5 | Renumbered to make space for 2.2.3 | +| 3.1.3 | Note added to give controllers guidance on requested aircraft to reject the takeoff | +| 3.2.6 | Controllers may issue line up & wait or takeoff clearance prior to aircraft requesting it | +| 3.2.7 - 3.2.11 | Renumbered to make space for 3.2.6 | +| 6.8 | New diversion section | +| 6.9 - 6.15 | Renumbered to make space for 6.8 | +| 7.3.1 / 7.4.1 | Apply Now buttons made functional | +| 7.3.3 | Maximum number of training sessions outlined | +| 7.4 | Section rewritten | +| 7A.2.3 | Note edited to remove Radar Written Test | +| 7A.2.5 | Maximum training sessions added | +| 7A.2.6 - 7A.2.9 | Renumbered to make space for 7A.2.5 | +| 7B.1 | Note added to ensure testers have in-progress airports hidden for testing | +| 7C.2.1 | Steps adjusted to reflect changes to the Dashboard | +| 7C.4.1 / 7C.5.7 | Recruiters to use the pause application function after 3 failed attempts at the Practical Test | +| 7C.4.2 / 7C.5.5 / 7C.5.8 | Minor wording correction | + ++++ + + + ++++ Summary of Changes - Version: 24.1.1 | Location | Change | | ----------------------- | ------------------------------------------------------------ | @@ -67,13 +101,3 @@ Should +++ - - -+++ Summary of Changes - Version: 23.2.2 - -| Location | Change | -| -------- | ------------------------ | -| 7A.2.1 | Reference to 7.1.3 added | - -+++ - diff --git a/developer-reference/index.md b/developer-reference/index.md index 4b811af3..096afd79 100644 --- a/developer-reference/index.md +++ b/developer-reference/index.md @@ -8,7 +8,7 @@ meta: Reference for the Infinite Flight Live and Connect APIs -## Guide Version: 24.1.0 +## Guide Version: 24.2.0 diff --git a/flying-guide/index.md b/flying-guide/index.md index 8108e669..09bf3df9 100644 --- a/flying-guide/index.md +++ b/flying-guide/index.md @@ -8,7 +8,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 diff --git a/flying-guide/take-off-to-cruise/instrument-flight-rules-(ifr)-en-route-navigation.md b/flying-guide/take-off-to-cruise/instrument-flight-rules-(ifr)-en-route-navigation.md index 5bfe6a9f..9d2c9988 100644 --- a/flying-guide/take-off-to-cruise/instrument-flight-rules-(ifr)-en-route-navigation.md +++ b/flying-guide/take-off-to-cruise/instrument-flight-rules-(ifr)-en-route-navigation.md @@ -111,5 +111,5 @@ Tip Step 5 -: You can also request [Radar Vectors](/guide/atc-manual/6.-radar/6.11-radar-vectors#6.11-radar-vectors) or other ATC services, IFR separation rules (both for aircraft and terrain) will then apply +: You can also request [Radar Vectors](/guide/atc-manual/6.-radar/6.12-radar-vectors#6.12-radar-vectors) or other ATC services, IFR separation rules (both for aircraft and terrain) will then apply diff --git a/get-help/general.md b/get-help/general.md index 04f44781..91519989 100644 --- a/get-help/general.md +++ b/get-help/general.md @@ -37,7 +37,7 @@ Tip +++ iOS - - iOS 13 operating system or later with a 64-bit processor + - iOS 15 operating system or later with a 64-bit processor - [Click here to see full list of devices supported](https://community.infiniteflight.com/t/device-compatibility-thread-19-4-built-by-us-for-you/323610) @@ -49,7 +49,7 @@ Tip Tip -: If your device doesn’t have iOS 13 operating system or later, you will still be able to enjoy Infinite Flight on versions prior to 21.6. To find out if your device meets these requirements, check [here](https://infiniteflight.com/timeline/21-6-ios-support) +: Any device that supports iOS 13 should be able to update to iOS 15, however, if your device doesn’t have iOS 13 operating system or later, you will still be able to enjoy Infinite Flight on versions prior to 21.6. To find out if your device meets these requirements, checkcheck [here](https://infiniteflight.com/timeline/21-6-ios-support) +++ diff --git a/get-help/index.md b/get-help/index.md index 0fdfba57..b00519fc 100644 --- a/get-help/index.md +++ b/get-help/index.md @@ -9,7 +9,7 @@ order: 1 -## Guide Version: 24.1.0 +## Guide Version: 24.2.0 diff --git a/get-help/subscriptions.md b/get-help/subscriptions.md index 7c620f3c..2de8d252 100644 --- a/get-help/subscriptions.md +++ b/get-help/subscriptions.md @@ -139,7 +139,7 @@ Auto-Renew can be cancelled directly from the Google Play or App Store. Please f -![Account Settings](_images/manual/frames/settings-account-233.png) +![Account Settings](_images/manual/frames/settings-account-242.png) diff --git a/getting-started-guide/home-user-interface/home-screen.md b/getting-started-guide/home-user-interface/home-screen.md index 94d3b74a..cbda6390 100644 --- a/getting-started-guide/home-user-interface/home-screen.md +++ b/getting-started-guide/home-user-interface/home-screen.md @@ -15,18 +15,19 @@ order: 0 Welcome to the home screen of your newly downloaded Infinite Flight app. Below you’ll find everything you need to know about this page and how to navigate your way through it. -![Home](_images/manual/frames/home-screen-233.png) +![Free Flight](_images/manual/frames/home-screen-242-v2.png) -1. Tap this symbol to access our news page as well as the leaderboards, your [logbook](/guide/getting-started-guide/home-user-interface/logbook#logbook) and [settings](/guide/getting-started-guide/home-user-interface/settings#settings) -2. At the top left you’ll find the [Get Pro](/guide/getting-started-guide/home-user-interface/subscriptions) subscription button. If you already have a subscription, then your [User Profile](/guide/getting-started-guide/home-user-interface/user-profile) will show instead +1. The top left symbol can be tapped to access our news page as well as the leaderboards, your [logbook](/guide/getting-started-guide/home-user-interface/logbook#logbook) and [settings](/guide/getting-started-guide/home-user-interface/settings#settings). Next to this you’ll find the [Get Pro](/guide/getting-started-guide/home-user-interface/subscriptions) subscription button. If you already have a subscription, then your [User Profile](/guide/getting-started-guide/home-user-interface/user-profile) will show instead 3. Location (airport/stand) selection - this search function allows you to [find the airport](/guide/getting-started-guide/home-user-interface/home-screen#airport-and-gate-selection) you want with ease. If you know the ICAO four letter code (e.g. KSFO for San Francisco Intl.) then you can type some or all of this, and a list of options will appear. Alternatively, just type in some or all of the city/airport name (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) 4. Tap here to [select your aircraft](/guide/getting-started-guide/home-user-interface/home-screen#aircraft-selection) (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) -5. Center map symbol -6. You can also use the map to find your starting location. Just use your finger to navigate around the globe, a pinching motion to zoom in and out, and then tap on the airport you want. You can also select the specific gate that you want by zooming in and then tapping on the respective light blue dot representing your chosen gate (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) -7. Select the [Mode](/guide/getting-started-guide/home-user-interface/mode#mode) and if you have chosen Multi Player, the [Server](/guide/getting-started-guide/home-user-interface/mode#servers) too -8. Ready to go flying? Tap on the [Fly button](/guide/getting-started-guide/pilot-user-interface/fly-screen) to begin +5. If Air Traffic Control is open at the airport you have selected, the facilities will be highlighted in green (only available in Multi Player on specific [Servers](/guide/getting-started-guide/home-user-interface/mode#servers)) +6. Select the time of day by tapping one of the symbols (sunrise, midday, sunset, night or current time). Or the arrow to fully customise the date and time +7. Weather is shown here, this can be adjusted using the arrow symbol (only available in Single Player [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) +8. In the bottom left of the map is the Center map symbol. You can also use the map to find your starting location. Just use your finger to navigate around the globe, a pinching motion to zoom in and out, and then tap on the airport you want. You can also select the specific gate that you want by zooming in and then tapping on the respective light blue dot representing your chosen gate (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode). A green boarder is shown if you do not have a [Pro](/guide/getting-started-guide/home-user-interface/subscriptions) subscription. Flight and airport selection is limited to within these various regions across the globe +11. Select the [Mode](/guide/getting-started-guide/home-user-interface/mode#mode) and if you have chosen Multi Player, the [Server](/guide/getting-started-guide/home-user-interface/mode#servers) too +12. Ready to go flying? Tap on the [Fly button](/guide/getting-started-guide/pilot-user-interface/fly-screen) to begin @@ -76,26 +77,17 @@ When in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free 1. The search function allows you to find the airport you want with ease. If you know the ICAO four letter code (e.g. KSFO for San Francisco Intl.) then you can type some or all of this, and a list of options will appear. Alternatively, just type in some or all of the city/airport name - - ​ - 2. Blue dots signify airports that have a tower facility (although it may not necessarily have active ATC) and magenta dots signify uncontrolled airports - - - 3. Airports that have buildings added are marked with a "3D" symbol +4. In Single Player, you can park wherever you want. But in Multi Player all parking positions are size restricted. If there are no parking positions available at an airport for the selected aircraft type, it will tell you the airport is too small when trying to select it - -4. In Single Player, you can park wherever you want. But in Multi Player all parking positions are size restricted. If there are no parking positions available at an airport for the selected aircraft type, it will tell you the airport is too small when trying to select it - +Tip - Tip +: [Select the aircraft](/guide/getting-started-guide/home-user-interface/home-screen#aircraft-selection) you want to fly before selecting a parking position, then you’ll be able to see where you can and can’t park - : [Select the aircraft](/guide/getting-started-guide/home-user-interface/home-screen#aircraft-selection) you want to fly before selecting a parking position, then you’ll be able to see where you can and can’t park - If you’re about to fly online, we also use a variety of colors to give you an idea of what the weather is like: diff --git a/getting-started-guide/home-user-interface/mode.md b/getting-started-guide/home-user-interface/mode.md index b7026acf..33ec4ccb 100644 --- a/getting-started-guide/home-user-interface/mode.md +++ b/getting-started-guide/home-user-interface/mode.md @@ -11,12 +11,12 @@ There are four modes that can be selected, these are: - [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) - choose your aircraft and airport, customize your flight plan, and enjoy an immersive flying experience at your own pace - [Missions](/guide/getting-started-guide/home-user-interface/mode#missions) - jump right into the action with recommended airline and charter routes based on traffic and ATC -- [Flight Training](/guide/getting-started-guide/home-user-interface/mode#free-training) - master your piloting skills with interactive tutorials +- [Flight Training](/guide/getting-started-guide/home-user-interface/mode#free-training) - master your piloting skills with interactive tutorials (Single Player only) - [ATC](/guide/getting-started-guide/home-user-interface/air-traffic-control) - leave the cockpit for the tower and control aircraft in the Infinite Flight skies (Multi Player only) -![Modes](_images/manual/frames/mode-233.png) +![Modes](_images/manual/frames/mode-242.png) @@ -30,18 +30,19 @@ There are four modes that can be selected, these are: -![Free Flight](_images/manual/frames/home-screen-233.png) +![Free Flight](_images/manual/frames/home-screen-242-v2.png) -1. Tap this symbol to access our news page as well as the leaderboards, your [logbook](/guide/getting-started-guide/home-user-interface/logbook#logbook) and [settings](/guide/getting-started-guide/home-user-interface/settings#settings) -2. At the top left you’ll find the [Get Pro](/guide/getting-started-guide/home-user-interface/subscriptions) subscription button. If you already have a subscription, then your [User Profile](/guide/getting-started-guide/home-user-interface/user-profile) will show instead -3. Location (airport/stand) selection - this search function allows you to [find the airport](/guide/getting-started-guide/home-user-interface/home-screen#airport-and-gate-selection) you want with ease. If you know the ICAO four letter code (e.g. KSFO for San Francisco Intl.) then you can type some or all of this, and a list of options will appear. Alternatively, just type in some or all of the city/airport name (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) -4. Tap here to [select your aircraft](/guide/getting-started-guide/home-user-interface/home-screen#aircraft-selection) (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) -5. Center map symbol -6. You can also use the map to find your starting location. Just use your finger to navigate around the globe, a pinching motion to zoom in and out, and then tap on the airport you want. You can also select the specific gate that you want by zooming in and then tapping on the respective light blue dot representing your chosen gate (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) -7. Select the [Mode](/guide/getting-started-guide/home-user-interface/mode#mode) and if you have chosen Multi Player, the [Server](/guide/getting-started-guide/home-user-interface/mode#servers) too -8. Ready to go flying? Tap on the [Fly button](/guide/getting-started-guide/pilot-user-interface/fly-screen) to begin +1. The top left symbol can be tapped to access our news page as well as the leaderboards, your [logbook](/guide/getting-started-guide/home-user-interface/logbook#logbook) and [settings](/guide/getting-started-guide/home-user-interface/settings#settings). Next to this you’ll find the [Get Pro](/guide/getting-started-guide/home-user-interface/subscriptions) subscription button. If you already have a subscription, then your [User Profile](/guide/getting-started-guide/home-user-interface/user-profile) will show instead +2. Location (airport/stand) selection - this search function allows you to [find the airport](/guide/getting-started-guide/home-user-interface/home-screen#airport-and-gate-selection) you want with ease. If you know the ICAO four letter code (e.g. KSFO for San Francisco Intl.) then you can type some or all of this, and a list of options will appear. Alternatively, just type in some or all of the city/airport name (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) +3. Tap here to [select your aircraft](/guide/getting-started-guide/home-user-interface/home-screen#aircraft-selection) (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) +4. If Air Traffic Control is open at the airport you have selected, the facilities will be highlighted in green (only available in Multi Player on specific [Servers](/guide/getting-started-guide/home-user-interface/mode#servers)) +5. Select the time of day by tapping one of the symbols (sunrise, midday, sunset, night or current time). Or the arrow to fully customise the date and time +6. Weather is shown here, this can be adjusted using the arrow symbol (only available in Single Player [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode) +7. In the bottom left of the map is the Center map symbol. You can also use the map to find your starting location. Just use your finger to navigate around the globe, a pinching motion to zoom in and out, and then tap on the airport you want. You can also select the specific gate that you want by zooming in and then tapping on the respective light blue dot representing your chosen gate (only available in [Free Flight](/guide/getting-started-guide/home-user-interface/mode#free-flight) mode). A green boarder is shown if you do not have a [Pro](/guide/getting-started-guide/home-user-interface/subscriptions) subscription. Flight and airport selection is limited to within these various regions across the globe +8. Select the [Mode](/guide/getting-started-guide/home-user-interface/mode#mode) and if you have chosen Multi Player, the [Server](/guide/getting-started-guide/home-user-interface/mode#servers) too +9. Ready to go flying? Tap on the [Fly button](/guide/getting-started-guide/pilot-user-interface/fly-screen) to begin @@ -49,17 +50,21 @@ There are four modes that can be selected, these are: -![Flight Training](_images/manual/frames/flight-training-233.png) +![Flight Training](_images/manual/frames/flight-training-242.png) + + + +1. Select the category within Flight Training by tapping on it + +![Flight School](_images/manual/frames/flight-school-242.png) -1. Select the tutorial you want to fly by tapping on it - -2. Ready to go flying? Tap on the [Fly button](/guide/getting-started-guide/pilot-user-interface/fly-screen) to begin +1. Select the tutorial you want to fly by tapping on it. Ready to go flying? When the tutorial has loaded, tap on the [Fly button](/guide/getting-started-guide/pilot-user-interface/fly-screen) to begin - + ## Missions diff --git a/getting-started-guide/home-user-interface/settings.md b/getting-started-guide/home-user-interface/settings.md index 3d598b3d..0ee866a7 100644 --- a/getting-started-guide/home-user-interface/settings.md +++ b/getting-started-guide/home-user-interface/settings.md @@ -11,7 +11,7 @@ contributor: deercrusher The Settings menu allows you to customize your Infinite Flight experience before and during play. Below is a guide to help you navigate your way around and to find the best settings for you! -![General Settings](_images/manual/frames/settings-general-233.png) +![General Settings](_images/manual/frames/settings-general-242.png) 1. On the left hand side of the screen are 6 categories that split the settings up, tap each one to find settings within @@ -69,11 +69,32 @@ Tip +## Graphics + +Infinite Flight supports both iOS and Android devices; because of this, the settings may need to be changed to ensure optimum performance. Unfortunately, not all devices are able to perform with all settings on high. Different combinations of high, medium and low may be required. For a detailed look at what graphics settings each device can handle, take a look at [this](https://community.infiniteflight.com/t/device-compatibility-thread-20-3-built-by-us-for-you/323610) topic on the Infinite Flight Community Forum. + + + +![Graphics Settings](_images/manual/frames/settings-graphics-242.png) + + + +| Setting | What it does | +| -------------------- | ------------------------------------------------------------ | +| Rendering Quality | Controls the quality of the rendering | +| 3D Object Density | Controls the density of objects at airports | +| Rendering Resolution | Controls the rendering resolution of the aircraft and scenery | +| Texture Quality | Controls the quality of the textures | +| Anti-Aliasing | Makes lines/graphics smoother and softens out the jagged/rough graphics that you may experience (it is not supported on all devices and can run very slow because of this - if device performance starts to degrade, turn this setting to **OFF**) | +| Frame Rate Limit | Sets the highest allowed frame rate | + + + ## Online -![Online Settings](_images/manual/frames/settings-online-233.png) +![Online Settings](_images/manual/frames/settings-online-242.png) @@ -113,10 +134,11 @@ Tip | [Discord Account](/guide/getting-started-guide/home-user-interface/user-profile#linking-a-discord-account) | Link a Discord account to gain exclusive access to our Pro-only Discord server | | Account Statistics | See your [grade level and violation history](/guide/getting-started-guide/home-user-interface/user-profile#the-grade-table). These stats determine multiplayer server level eligibility | | Switch Account | Use a different Infinite Flight account to access a subscription bought on another device | +| Delete Account | Removes your personal information, stats and linked accounts. Your subscription will still be available via a new, anonymous account. | -![Account Settings](_images/manual/frames/settings-account-233.png) +![Account Settings](_images/manual/frames/settings-account-242.png) @@ -126,7 +148,7 @@ There are two sliders that adjust the SFX and ATC Volume. Slide your finger alon -![Audio Settings](_images/manual/frames/settings-audio-233.png) +![Audio Settings](_images/manual/frames/settings-audio-242.png) @@ -143,27 +165,6 @@ Tip -## Graphics - -Infinite Flight supports both iOS and Android devices; because of this, the settings may need to be changed to ensure optimum performance. Unfortunately, not all devices are able to perform with all settings on high. Different combinations of high, medium and low may be required. For a detailed look at what graphics settings each device can handle, take a look at [this](https://community.infiniteflight.com/t/device-compatibility-thread-20-3-built-by-us-for-you/323610) topic on the Infinite Flight Community Forum. - - - -![Graphics Settings](_images/manual/frames/settings-graphics-233.png) - - - -| Setting | What it does | -| -------------------- | ------------------------------------------------------------ | -| Rendering Quality | Controls the quality of the rendering | -| 3D Object Density | Controls the density of objects at airports | -| Rendering Resolution | Controls the rendering resolution of the aircraft and scenery | -| Texture Quality | Controls the quality of the textures | -| Anti-Aliasing | Makes lines/graphics smoother and softens out the jagged/rough graphics that you may experience (it is not supported on all devices and can run very slow because of this - if device performance starts to degrade, turn this setting to **OFF**) | -| Frame Rate Limit | Sets the highest allowed frame rate | - - - ## Controls In the control settings you can adjust your control sensitivity for each axis as well as customize your settings for joysticks, keyboards or other controlling devices. The 2 axes that your device’s accelerometers utilize are: @@ -183,7 +184,7 @@ In the control settings you can adjust your control sensitivity for each axis as -![Control Settings](_images/manual/frames/settings-controls-233.png) +![Control Settings](_images/manual/frames/settings-controls-242.png) diff --git a/getting-started-guide/home-user-interface/user-profile.md b/getting-started-guide/home-user-interface/user-profile.md index acab7176..ee4131d9 100644 --- a/getting-started-guide/home-user-interface/user-profile.md +++ b/getting-started-guide/home-user-interface/user-profile.md @@ -19,7 +19,7 @@ order: 4 -![Account Settings](_images/manual/frames/settings-account-233.png) +![Account Settings](_images/manual/frames/settings-account-242.png) @@ -192,8 +192,8 @@ Below is a table that outlines the different Grade requirements: | Min Total XP | - | 2000 | 50,000 | 80,000 | 175,000 | | Min Total Flight Time | - | 5 | 50 | 120 | 500 | | Min Total Landings | - | 25 | 100 | 400 | 800 | -| Min Flight Time (90 days) | - | 3 | 10 | 30 | 70 | -| Min Landings (90 days) | - | 5 | 15 | 100 | 180 | +| Min Flight Time (90 days) | - | - | - | 30 | 70 | +| Min Landings (90 days) | - | - | - | 100 | 180 | | Max Level 1 Violations (24 hours) | - | 7 | 5 | 0 | 0 | | Max Level 1 Violations (7 days) | - | 25 | 5 | 0 | 0 | | Max Level 1 Violations/Landings Ratio (1 year) | - | 0.8 | 0.5 | 0.22 | 0.05 | @@ -201,7 +201,7 @@ Below is a table that outlines the different Grade requirements: | Max Level 3 Violations (7 days) | - | 5 | 0 | 0 | 0 | | Max Level 3 Violations (1 year) | - | 10 | 5 | 4 | 2 | | Max Combined Level 2 and 3 Violations (1 year) | - | 10 | 5 | 4 | 2 | -{.grade-table} +|{.grade-table}|||||| diff --git a/getting-started-guide/index.md b/getting-started-guide/index.md index f16a7a3d..4d517f2c 100644 --- a/getting-started-guide/index.md +++ b/getting-started-guide/index.md @@ -8,7 +8,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 diff --git a/getting-started-guide/installing-the-app/iOS.md b/getting-started-guide/installing-the-app/iOS.md index 918ef358..55ac3f24 100644 --- a/getting-started-guide/installing-the-app/iOS.md +++ b/getting-started-guide/installing-the-app/iOS.md @@ -14,7 +14,7 @@ Infinite Flight is available for download on the App Store. Below are the minimum requirements for a successful install on your device. In addition to this, we strongly recommend that your device has **at least** 3GB+ of internal device memory (RAM): - - iOS 13 operating system or later with a 64-bit processor + - iOS 15 operating system or later with a 64-bit processor - [Click here to see full list of devices supported](https://community.infiniteflight.com/t/device-compatibility-thread-19-4-built-by-us-for-you/323610) @@ -26,7 +26,7 @@ Below are the minimum requirements for a successful install on your device. In a Tip -: If your device doesn’t have iOS 13 operating system or later, you will still be able to enjoy Infinite Flight on versions prior to 21.6. To find out if your device meets these requirements, check [here](https://infiniteflight.com/timeline/21-6-ios-support) +: Any device that supports iOS 13 should be able to update to iOS 15, however, if your device doesn’t have iOS 13 operating system or later, you will still be able to enjoy Infinite Flight on versions prior to 21.6. To find out if your device meets these requirements, check [here](https://infiniteflight.com/timeline/21-6-ios-support) diff --git a/getting-started-guide/pilot-user-interface/flight-planning.md b/getting-started-guide/pilot-user-interface/flight-planning.md index 1520992c..095f63f7 100644 --- a/getting-started-guide/pilot-user-interface/flight-planning.md +++ b/getting-started-guide/pilot-user-interface/flight-planning.md @@ -63,6 +63,36 @@ Tip +## Adding Coordinates to your Flight Plan + +The following format needs to be used when adding coordinates to a flight plan: + + + +ddmmx/ddmmy + + + +> **Key:** +> +> d - degrees +> +> m - minutes +> +> x - N or S +> +> y - E or W + + + +When adding a coordinate, you will need to include at least one other waypoint or coordinate as it is not possible to add just one coordinate by itself. For example, if you wanted to add 55N050W (5500N/05000W using the above compatible format), you would need to select another coordinate or waypoint to add to the flight plan at the same time (e.g. 5500N/05000W 5500N/04000W 5500N/03000W etc.). + + + +> It is currently not possible to add seconds so these will need to be rounded to the nearest minute when adding to your flight plan + + + ## Share Flight Plan diff --git a/scenery-editor-manual/index.md b/scenery-editor-manual/index.md index 2d0e7b20..1f554621 100644 --- a/scenery-editor-manual/index.md +++ b/scenery-editor-manual/index.md @@ -8,7 +8,7 @@ meta: Learn how to use the Infinite Flight Scenery Editor with our online docume -## Guide Version: 24.1.0 +## Guide Version: 24.2.0