AE4321 Air Traffic Management
Assignment info
Jacco Hoekstra & Joost Ellerbroek
1|
Second semester ATM:
the future of ATM
LectureDate
1
13-2-2023
2
20-2-2023
3
27-2-2023
4
6-3-2023
5
13-3-2023
6
20-3-2023
7
27-3-2023
Session
Briefing assignments
papers A
papers B
papers C
Plug-ins
SimScen/Prize
Exam practice & Q&A
Lecturer(s)
Jacco Hoekstra/Joost Ellerbroek
Joost Ellerbroek
Marta Ribeiro
Jacco Hoekstra
Joost Ellerbroek
Jacco Hoekstra
Jacco Hoekstra/Joost Ellerbroek
• Assignment (50% grade if >5.0)
• Written exam (50% grade if >5.0)
• Exam: Wednesday afternoon April 12th 2023 13:30-16:30
2|
Templates can be found on Brightspace
• Essay template & Powerpoint template
• Goal is to explain crux of the research presented in the paper and
review it
• Be critical: Not all papers are good. Is the method sound & clearly
explained? Is it reproducible? Do results support conclusions?
• Essay: decide on who takes which part
• Presentations: 20 minutes each (2 x 7.5 min + Q&A), each team
member presents his/her part + 5 minutes questions
• Example good essay and good presentation
3|
Group Sim Assignments
Name
E-mail
Group
van Beek, Jorn
J.vanBeek-2@student.tudelft.nl
S1
Ou, Dequan
D.Ou@student.tudelft.nl
S1
Shu, Luke
A.Shu-1@student.tudelft.nl
S1
Gebben, Fabian
F.Gebben@student.tudelft.nl
S1
Caron, Julius
J.Caron-1@student.tudelft.nl
S2
Hollander, Ties
T.J.A.Hollander@student.tudelft.nl
S2
Poelstra, Sander
S.Poelstra@student.tudelft.nl
S2
van Kaam, Jorn
J.K.E.vanKaam@student.tudelft.nl
S2
Barbian, Luuk
L.H.K.Barbian@student.tudelft.nl
S3
Kruidenier, Wessel
W.L.Kruidenier@student.tudelft.nl
S3
Cürgül, Yaren
Y.Curgul@student.tudelft.nl
S3
Timmermans, Daniël
D.I.Timmermans@student.tudelft.nl
S3
Miranda de Andrade Veiga,
C.MirandadeAndradeVeiga@student.tudelft.nlS4
Constanca
Pabsch, Christoph
C.M.N.Pabsch@student.tudelft.nl
S4
Dietz, Willemijn
S.W.Dietz@student.tudelft.nl
S4
Zijlmans, Noa
N.Zijlmans@student.tudelft.nl
S4
Assignment
Schiphol early merge
Schiphol early merge
Schiphol early merge
Schiphol late merge
Schiphol late merge
Schiphol late merge
Schiphol late merge
Schiphol late merge
Regional airports
Regional airports
Regional airports
Regional airports
Dutch Caribbean airspace
Dutch Caribbean airspace
Dutch Caribbean airspace
Dutch Caribbean airspace
4|
Airspace Design
•Make description and presentation
•Each sub-team presents:
• considerations, starting points
• their design
• choices
• how they simulated it
•Make a simulation using BlueSky
5|
Specific assignments per group
• Team S1 Fixed arrival (Early merge):
Use the 3 initial approach fixes and fixed arrival routes
• Team S2 Late merging:
Use the 3 initial approach fixes, but flexible routing and late merging
• Team S3 Regional Airports:
Investigate how mnay flight could be taken over to regional airports EHRD en EHLE,
optionally: design other regional airport procedures
• Team S4 Carribean:
Stusy current situation but use a blank sheet approach to design procedure for the ABC islands
Metrics, mostly presentation, simulation and short report to explain design, but also:
Green: minimize for CO2 (and fuel)
- Noise: avoid populated areas as much as possible
- Time: arrive close to schedule (if given, otherwise maximize capacity. Minimize delays)
- Route length: efficiency
and
Safety: separation/distribution of traffic
6|
Airspace Design information
• Assume Free Route Airspace above FL245 (or even lower?)
• Aeronautical chart:
https://www.lvnl.nl/media/2490/lvnl-anc-icao-2018c.pdf
• Use AIP for existing information: https://www.lvnl.nl/eaip/2020-12-17AIRAC/html/index-en-GB.html Also Caribean (see BrightSpace)
• AIS publications
• Integrated Aeronautical Information Package
• Part 2 En-route (ENR)
• ENR 6 EN ROUTE CHARTS
• Part 3 Aerodromes (AD)
• EHAM Amsterdam/Schiphol
• Aerodrome charts
• Use Google maps to avoid major cities for lower part of departures
• Assume continuous descent operations and fixed arrival routes
7|
BlueSky Wiki & Command reference
• Link to Wiki: https://github.com/TUDelft-CNS-ATM/bluesky/wiki
• Command reference: https://github.com/TUDelft-CNSATM/bluesky/wiki/Command-Reference
• Commands to check out:
• SIM control: HOLD, OP, FF, RTF, SAVEIC, IC, IC IC
• Basics: CRE, HDG, SPD, ALT, VS (only in combination with ALT), POS
• Display: PAN, button
• FMS: ADDWPT, DELWPT, LISTRTE, DELRTE, AT, LNAV, VNAV (speed
command will override VNAV speeds), RTA, AFTER, SWTOC, SWTOD
Scripts/prcodures: PCALL (use with an argument to add arrivals/departures, or
header with settings)
• Conditional commands: ATALT, ATSPD, ATDIST
• Drawing: POLY, POLYLINE, LINE, CIRCLE, COLOUR
• Tools: DIST,CALC
• Radarclick position or aircraft id. As arguments, click in radar window
to: select an aircraft, enter a lat/lon,
8|
BlueSky Wiki tutorials
• Can be found at:
https://github.com/TUDelft-CNS-ATM/bluesky/wiki/Tutorials
• Editing flight plans: https://github.com/TUDelft-CNSATM/bluesky/wiki/Editing-flight-plans
• Running Batch scenario’s: https://github.com/TUDelft-CNSATM/bluesky/wiki/Running-batch-scenario (Different from PCALL!)
9|
BlueSky needs Python 3.8 or higher
• Recommended is newest Python 3 version 64-bits
• See wiki for installation instructions
10 |
Steps to take: Download BlueSky
• Go to https://github.com/TUDelft-CNS-ATM/bluesky
11 |
Copy bluesky-master folder
12 |
BlueSky start
13 |
Scenario files are text files with time
stamped commands
14 |
Load 0-demo-scenario.scn
• Define a waypoint in front of the coast with DEFWPT name,lat,lon
Click lat,lon
• Measure distance with dist to coast with DIST lat1,lon1,lat2,lon2
(clicking)
• Select an aircraft (double click on symbol to see route and info)
• Use addwpt to add your waypoint
• Also add SPY and SPL
• Make sure LNAV and VANV are on
15 |
Control an aircraft: traffic-NE.scn
• Load traffic-NE.scn from Contest folder or from downloaded from
BrightSpace
• Select an aircraft which is taking off
• Give ALT, SPD and HDG instruction
• Then add waypoints with an altitude in the direction of the
heading (LNAV should be switched on automatically.) Switch on
VNAV
• VNAV logic:
- climb as soon as possible to next higher altitude constraint in
route
• - descend as late as possible to meet next lower altitude
constraint
16 |
Making a new BlueSky plug-in
• Example plug-ins (based on earlier years):
• Route planning plug-in for BlueSky
• Automatic Aircraft Rerouting Plugin for Closed Airspace
• Planning ETOPS route
• Planning emergency landing route
• Arrival Manager or Departure Manager
• Import/export plug-ins, webcrawlers
• Scenario utilities
17 |
Plug-in template & examples in plugin subfolder
• Template: example.py
18 |
Plug-in template & examples in plugin subfolder
• Template: example.py
19 |
20 |
21 |
Plug-in Assignment
Name
Becking, Pieter
IJzermans, Paul
Pietersz, Alec
Smeets, Jorian
van Laar, M.J.
E-mail
P.H.Becking@student.tudelft.nl
P.M.IJzermans@student.tudelft.nl
A.A.A.Pietersz@student.tudelft.nl
J.Smeets-1@student.tudelft.nl
M.J.vanLaar@student.tudelft.nl
Plug-in
P1
P1
P3
P4
P6
Title
Bird formation flying
Emergency route 1
Emergency route 1
TBD
• Joost Ellerbroek is coordinatr of Plug-in session, will give briefing
as part of second part of BlueSky lecture
• Send in your plug-in proposal before Session A
22 |
Dutch Airspace Design
requirements: Mil AirSpace
• Due to the JSF with long range weapons , the military wants a
larger exercise area up to an high altitude (large line of sight)
during weekdays 8:00 – 17:00. This could be temporarily on/off
or partially dynamic) .
• As there are less civil flights over the north of the Dutch airspace,
especially north-west this seems the best location.
23 |
Schiphol Runway 22-04
operated as separate GA airport
• Most aircraft should go to other (longer) runways
• Business jets and GA aircraft land on RW22 or RW04 (SchipholOost)
24 |
Runway use Schiphol: Check
scenario file
• Avoid populated areas Amsterdam and Hoofddorp
X
X
25 |
Step 1: Make your design in BlueSky
• Make draft on paper
• Use BlueSky to draw sectors, save clicked lat,lons in a recorded
scenario file (POLYGON command)
• Use BlueSky to define routes, define waypoints with clicks, use
them to define a route (polyline) and optionally make a procedure
file which adds these waypoints in the right order to the aircraft
for which your call the scenario file with the procedure
• Output are scenario files:
• files with definitions of sectors (POLYGON, use names which make
sense)
• files with defined waypoints (DEFWPT) for STARs and SIDs
• files with routes (LINES) to be drawn
• files with same routes as procedure (%0 ADDWPT
wpname/lat,lon,alt,speed
26 |
Step 2: Fine tuning and preparing for
simulation
• Merge scenario files into one file for all types (sectors, waypoints,
routes, procedures)
• Run it separately to try your sector and get proficient in guiding
traffic in your sector:
•
•
•
•
KL204
KL204 PROCWEST01
KL204 APPRWY24
KL204 LNAV ON
mouse)
• KL204 ALT 5000
Check destination
Add waypoints to the route to FMS
Add more waypoints to FMS
Make AP follow route for heading
(instead of HDG command with
Instead of VNASV you can use tactical
commands
• KL204 SPD 200
• KL204 ALT 2000; KL204 SPD 160; Kl204 ALT 0
27 |
Step 3: Make your final simulation in
a scenario file
• The end result of the simulation assignment should be a file which
has the total scenario
28 |
Merge scenario file with SUMSCEN
• In utils/sumscen folder you can find a utility to merge scenario
files
• Identical lines will only occur once in the resulting files
• All lines (incl. timestamp) which are unique will be added, ordered
by the timestamp
• This allows you to work separately on your sector as long as it is
clear under whose control an aircraft is!
29 |
Combining it into one scenario
offline
• Scenario files (extension .scn) are simply text files so you can
combine multiple with some logic in a Python program
• SUMSCEN tool
• Combine the lines for the traffic under your control (calls sign and
time based):
• Making a Python program/script to combine relevant lines is
recommended
• Run the combined script to de-conflict
30 |
Real Time configuration
for making final simulation
Start BlueSky with
master scenario
file on most
powerful
laptop/macbook
Join the simulation with
other GUIs
Use HOLD when
necessary
|
31 scenario
Make one hour
Variation in difficulty
• Technically most simple: use HDG command and only draw
routes/sectors, but a lot of work when flying
• Use procedure files, assign routes, use heading command only
when necessary
• Very advanced (requires programming):
• process scenario file digitally (use geo.py) to have procedure
assignment in scenario file, only manage exceptions
• make a plug-in to automate assignment of procesdures real-time,
only manage exceptions with hdg or only spd/alt
• Share questions and solution on BrightSpace
32 |
Scenarios
• Scenario file will be provided on BrightSpace
• Allow 20 minutes for build-up time: first a/c arrives at EHAM
• Around 20 minutes wave of F-35 fly to North Sea
• Around 40 minutes wave of F-35s come back from North Seas
• Starts with outbound peak, around 40 minutes runway changes at
EHAM, so each scenario has two parts
• Measurement planned for after 20 minutes
• Submit final scenario files including controlled traffic, one set for
wind each case
33 |
Design teams
• Set up communication
• Appoint coordinator/leader/secretary
• Make appointments for simulation
34 |
Adding your ATC commands to
scenario
• SAVEIC newscen
• IC oldscen
: Save current situation as initial condition
: Open existing scenario file
• BlueSky will now read oldscn.scn and record all commands from
the file and from the console(s) in the saveic file in thic case
newscen.scn
• You can use CD or CHDRI to move to subfolder
• From one scenario file you can call other scenario file
• CALL subscen
: e.g., for drawing or defining sectors,
waypoints, routes, procedures etc.
• CALL subscen KL204 : then KL204 will be filled in where in the
subscen.scn file it says %0, for example
CALL EHAM/SID18LANDIK
35 |
Two ways to make sectors
• Use POLYGON command to draw sectors:
• POLYGON name lat0,lon0,lat1,lon1,lat2,lon2, etc.
• POLYGON SEAWEST, 51.0310,03.12,N52’34’12E001’23’57,SPY
• POLYGON command closes polygon for you
• Vertices can be lat,lon (e.g. mouse click) or DMS notation or
waypoint
• You can edit sectors in two ways:
1. Edit a scenario file:
00:00:00.00>POLYGON SEAWEST,
51.0310,03.12,N52’34’12E001’23’57,SPY
2. Record it from your console when clicking with the mouse with
SAVEIC
36 |
BlueSky commands to check out (1/3)
Check out examples in scenario folder (a .scn is a text file)
General structure to control traffic:
acid(call sign) COMMAND args
Click on map for: a lat/lon, to select an aircraft. Lat/lons can be used as wpt
Traffic controls:
• CRE
• HDG,SPD,ALT,VS
• DEL acid
: Create an aircraft (when creating on runway,
leave open heading (or *)
: Tactical controls
: Delete an aircraft
FMS (route):
• DEST, ORIG, ADDWPT, AT: Edit route/flight plan
• DIRECT wpt
: Set active waypoint
• LNAV, VNAV
: Activate lateral and vertcila FMS A/P mode
https://github.com/ProfHoekstra/bluesky/wiki/Command-Reference
37 |
BlueSky commands to check out (2/3)
• Waypoints:
POS wpt/apt/acid
: gives info on item such as waypoint
DEFWPT newwpt,lat,lon : define a new waypoint for nav database 9use
e.g. mouse to find lat/lon)
• Define procedure: (see examples in EHAM scenario folder)
CALL SID18R KL204
: calling a scenario file with an argument
(KL204) which will be filled in for %0 ,%1 %2
• Drawing commands (to draw routes and sectors)
LINE, POLY, CIRCLE
: to draw the airspace design and the routes to
help you in controlling the traffic
• Tools:
DIST
lat1,lon1,lat2,lon2
CALC expression
:calculate distance (and direction)
: calculator/debug variables can use
units such as nm, kts, ft etc
https://github.com/ProfHoekstra/bluesky/wiki/Command-Reference
38 |
BlueSky commands to check out (3/3)
Scenario files:
• IC scenfile
: load and start scenario file
• SAVEIC newscenfile : record current situation as IC and start
recording commands
• CALL scenfile
: call scenario file
(e.g. for general settings or drawing or
waypoint definitions)
Simulation control:
• IC IC
•
•
•
•
HOLD
OP
FF
RTF n
: restart using last loaded scenario file
(is being saved between runs)
: Pause simulation
: (re)start simuation
: fast forward
: real time factor (RTF 2 = double speed)
https://github.com/ProfHoekstra/bluesky/wiki/Command-Reference
39 |
First step: Airspace in BlueSky
• Use a text editor to make scenario file, use DIST command to
click on map to get lat/lons which draws your sector and its
routes, combine with sumscen
• Scenario files need the extension .scn, which can be left out in
commands in console when you load a scenario file with IC
• Syntax of line in a scenario file:
HH:MM:SS.hh>command line as edited in console
Example:
# This is a comment line because of hash sign
00:01:34.56>KL204 HDG 270
• Format lat/lon: decimal or DMS:
52.1,4.0
or
N52’24’30.01”,E004’23’45.02”
40 |