-
Notifications
You must be signed in to change notification settings - Fork 28
Added Pattern Work Re-Sequence Scenario to ATC Guide #587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kyleboas
wants to merge
3
commits into
infiniteflight:main
Choose a base branch
from
kyleboas:patch-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,7 +27,7 @@ For a step by step guide on how to issue pattern entries, sequencing and clearan | |
|
||
|
||
|
||
+++ SCENARIO - Re-Sequencing | ||
+ SCENARIO - Re-sequencing to control the size of the pattern | ||
|
||
::: scenario-heading | ||
Scenario | ||
|
@@ -55,9 +55,6 @@ Scenario | |
|
||
{.prosandcons} | ||
|
||
|
||
|
||
|
||
| Technique 2 | | ||
| ---------------------------------------------------- | | ||
| 1: Instruct *I-DRUM* to "turn base" | | ||
|
@@ -75,6 +72,61 @@ Scenario | |
+++ | ||
|
||
|
||
+ SCENARIO - Re-sequencing more then one aircraft on the opposite downwind | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same thing here too, needs to have +++ |
||
|
||
::: scenario-heading | ||
Scenario | ||
::: | ||
|
||
::: scenario | ||
*YU-MMY* is number 1 for runway 10R, *G-ZZJB* is sequenced number 2 for runway 10R, *G-RIZZ* is number 1 for runway 10L and *N623KB* is sequenced number 2 for runway 10L. *YU-MMY* then asks for a RWY change to 10L. | ||
::: | ||
|
||
[Insert requested by Regan] | ||
|
||
{.scenario} | ||
|
||
| Technique 1 | | ||
| ------------------------------------------------------------ | | ||
| 1: Instruct *YU-MMY* to "enter right downwind RWY10L, number 2, traffic to follow is on left downwind” | | ||
| 2: If you are concerned about a conflict on base between *G-RIZZ* and *YU-MMY*, then you can also tell *G-RIZZ* to "turn base" ahead of *YU-MMY* to alleviate this | | ||
| 3: When you clear *YU-MMY* for the option, you can then tell them to “make left traffic” if you wish to do so to move them onto that side for subsequent patterns | | ||
| 4: Issue *N623KB* a re-sequence to follow *G-RIZZ* “number 3, traffic to follow is on left downwind” | | ||
|
||
{.technique} | ||
|
||
| Technique 1 | Pro or Con? | | ||
| ----------------- | ------------------------------------------- | | ||
| :fa-check-circle: | *YU-MMY* will not have to extend downwind and the controller will have to issue less commands, lightening the pilot’s and controller’s workload | | ||
| :fa-times-circle: | *N623KB* is in a C172 and you could accommodate a shorter downwind for them by sequencing *YU-UMMY* number 3 to follow *N623KB* | | ||
|
||
{.prosandcons} | ||
|
||
|
||
Tip | ||
|
||
: Aircraft performance should be taken in to account when sequencing aircraft. Controllers should try to accommodate a shorter pattern for slower performance aircraft. | ||
|
||
| Technique 2 | | ||
| ------------------------------------------------------------ | | ||
| 1: Instruct *G-ZZJB* to "turn base” | | ||
| 2: Instruct *YU-MMY* to “enter right downwind RW10L, number 3 traffic to follow is on left downwind” | | ||
| 3: To alleviate the risk of confusion between pilots you can instruct *YU-UMMY* to “extend downwind, I’ll call your base” to ensure there is no conflict with *N623KB* | | ||
| 4: You can instruct *N623KB* to turn base when appropriate so *YU-UMMY* doesn’t have to extend downwind as far | | ||
| 5: Instruct *YU-MMY* to “turn base” when adequate spacing is achieved between them and *N623KB* | | ||
|
||
{.technique} | ||
|
||
| Technique 2 | Pro or Con? | | ||
| ----------------- | ------------------------------------------------------------ | | ||
| :fa-check-circle: | Accommodates a shorter pattern for *N623KB* | | ||
| :fa-times-circle: | Higher workload for the controller with the risk of confusion between pilots | | ||
|
||
{.prosandcons} | ||
|
||
+++ | ||
|
||
|
||
|
||
## Transitions | ||
|
||
|
@@ -150,4 +202,4 @@ Step 2 | |
|
||
Tip | ||
|
||
: It may be easier to use the flight progress strip as multiple aircraft flying in formation can make tapping the aircraft on the map a bit tricky! | ||
: It may be easier to use the flight progress strip as multiple aircraft flying in formation can make tapping the aircraft on the map a bit tricky! |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.