FlowAssist by Neil Brown - PowerPoint PPT Presentation

Title: FlowAssist by Neil Brown


1
FlowAssistby Neil Brown John Keech(a sneak
preview)

• for online controllers pilots

2
Topics well be covering

• Flow control / advanced sequencing a quick
  refresher.
• FlowAssist the new VATSIM / VATPAC flow control
  guidance tool.
• Question time.

3
Disclaimer words of warning dont try this in
real life, even with strict supervision!

• All rules, suggestions, methodology separation
  standards etc are specifically for online
  aviation simulation only.
• They have been modified /or simplified for the
  online environment are not to be used in the
  real world under any circumstances.

4
Advanced sequencingusing the radar clients

• The target to have 2 to 3min between successive
  arrivals at touchdown.
• Use the BRL (bearing range line) from the 10nm
  (or 12nm) approach fix, out to each aircraft.
• Compare distances to run.
• Compare ground speeds (differences due upper
  winds) extrapolate the effect.
• Determine whether you will have a 20nm trail as
  CTR, to hand-off to APP.
• Determine whether you will have a 10nm trail as
  APP, to hand-off to TWR.

5

• Whilst aircraft are still on cruise well before
  TOD, issue speed adjustment instructions.
• Vector aircraft on dog-legs as required,to
  achieve required in trail distances.
• Initiate all sequencing instructionswith For
  sequencing .

27 VHSLJ 184v090 480 YMML LR35
Only an 11nm differential / trail slight
closing due westerly upper winds.
27 QFA431 172v090 500 YMML B738
H 315 135 D 61.0
H 040 220 D 50.0
12nm approach fix
6
FlowAssist

• Minimises traffic delays through automationof
  the following
• Automatic compilation of the sequence order.
• Runway allocation (to best fit the sequence).
• The controller only issues the STAR after
  FlowAssist has allocated the runway (ETA minus
  45min).
• Time delay directives to controllers,for
  aircraft manipulation.
• Constant provision of estimated landing times.

7
Features

• 1 or 2 runways may be programmed / nominated.
• Traffic may be split between the two runways,
  either via a logical inbound radial / airspace
  division, or
• Jets to one runway Props to the alternate
  runway.
• Aircraft are processed into 2 minute slots (same
  runway), or 1 minute slots (crossing or parallel
  runways).
• Slots may be changed by 1 minute increments (in
  the configuration page).
• A new runway configuration may be re-set during
  the sequence to affect only new aircraft
  entering the sequence, or
• affect all existing aircraft already sequenced.

8
The setup / configuration page
Location
Entire sequence runway change
Runway 1
Opens the ladder window
Mid sequence runway change
9
Colour / graphical runway split, showing NE
traffic to 34R SW traffic to 34L
Two runway setup
Radial for airspace division split
10
Advanced features

• Controller over-ride for runway allocation, when
  pilot operationally requires a different runway
  to the FlowAssist allocated runway.
• Priority codes (controller entered), to allow
  forced sequence queue jumping for VIP, Medical
  Emergency status.

11
Logic calculation processes

• ETI calculations include tracking via the 12nm
  approach fix to the allocated runway.
• They also include additional s for gradual
  deceleration from top of descent.
• Aircraft category is determined upon planned TAS,
  so pilots must ensure this is correct ( not IAS).

12
Aircraft status modes

• FlowAssist assigns a stability mode to all
  aircraft as they come into the FlowAssist range
  (lt 60 min from estimated landing time excluding
  delays).
• UNSTABLE gt45min from initial calculated
  touchdown time excluding delays. No runway
  assigned. Slot position may vary. Delay directive
  times not yet displayed.
• STABLE from lt45min to gt30min. Runway assigned
  locked in (unless overidden by controller). Slot
  position may vary. Delay times dynamically
  updating may change.
• SUPER STABLE from lt30min to gt6min. Runway
  assigned locked in (unless changed by
  controller). Slot position locked in (unless
  runway overridden by controller, or aircraft
  priority code causes sequence to change). Delay
  times dynamically updating may change.
• FROZEN lt6min. Runway assigned locked in
  (unless overridden by controller). Slot position
  locked in (unless runway overridden by
  controller). Delay directive times no longer
  displayed.

13
Flow directives display format

• Information is displayed on a sequence ladder.
• The ladder is split into 1 min increments,
  representing the estimated landing time.
• The ladder tics down one step every minute
  the current time is the bottom line of the
  ladder.
• There are two sides, one for each nominated
  runway.
• Flow directives for the left hand side of the
  ladder are shown in this order, from left to
  right

14

• Current delay still required (the aircraft still
  has to absorb this number of minutes delay
  either speed control, dogleg vectoring or
  holding).
• Total delay (until achieved re-set).
• Delay times are colour coded
• 0 in black, lt 5 min in yellow gt 6 min in red
  (suggesting holding).
• Callsign.
• Runway allocated by FlowAssist.
• Estimated landing time (shows as mm not
  hhmm).
• The right hand side of the ladder is a mirror
  image (ie. far right column is the current
  delay column).

15
Location
Last data update time
Current time
Estimated landing time ladder
Current time
16
Estimatedlanding time
Currentdelay
Totaldelay
Callsign
Runway
Currentdelay
Totaldelay
Callsign
Runway
17
Actual sequence into YSCB
18
(No Transcript)
19
(No Transcript)
20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
Moving ahead 19 minutesin the sequence
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34
(No Transcript)
35
(No Transcript)
36
(No Transcript)
37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
(No Transcript)
41
(No Transcript)
42
thats the FlowAssist sneak preview !
43
Caution re presentation content

• Please bear in mind that this presentation
  grossly over-summarises all the real life
  separation standards rules.
• There are many many more rules, hence the real
  ATC course being over 12 months, amazingly not
  just 40 minutes! ?
• Naturally then, application of the previous
  standards would at times be not legally correct,
  are just a general guideline for online
  controllers.

44
Questions ???
eMail john_at_vatpac.org