Post on 22-Jul-2018
Airspace Concept Handbook Overview
1
HANDBOOK CONTENTS
1. The Airspace Concept
2. Airspace Concept Development
3. Airspace Concept Validation
4. Implementation
2
PBN
3
NAV SPECS
4
AIRSPACE CONCEPT
5
6
Activity 1
✈Capacity ✈Environment ✈Accessibility ✈Safety ✈Efficiency
7
1 - Agree on Operational Requirements
Activity 2
✈ Lead by ATM/airspace specialist
✈ATC (Approach and Area controllers)
✈ATM & CNS specialist
✈ Procedure designers
✈ Technical pilots
✈…… 8
2 – Create Airspace Design Team
Activity 3
✈Objective derived from Ops requirements
✈ Scope !! ( sets the limit of the project)
✈Time
✈Resources
✈ Timescales
Sometimes the most difficult task
9
3 – Project objectives, scope and timescales
Activity 3
10
3 – Project objectives Capacity Efficiency
Improve SID/STAR design
to accommodate
projected traffic growth
Provide shorter and
more predictable
routes to/from Kapitali
Environment
Reduce noise over sensitive
areas
Airspace Concept
Safety? Access?
Activity 3
11
3 – Project objectives, scope and timescales
$ $
Implementation Date(s) Phases of Work?
$ $
Which Human Resources? What about the budget?
What is the
What cannot be done?
Objective ? How much can be done?
Activity 3
12
3 – Project timescales
Update ATC Unit InstructionsATC TrainingPlus
PANS-OPS PreparationPublicationPlus
NB: AIRAC cycle interval
RTS
Prepar
ation
(Concept)VALIDATION
IMP
LEM
ENTA
TIO
N
REVIEW
(Concept)ASSESSMENT
Safety Assessment
DESIGN CONCEPT
Proje
ct St
eerin
g Gr
oup
Wor
k
QualitativeAnalysis
= = =
Proje
ct Te
am se
tup
Proje
ct Ob
jectiv
esSc
ope &
Tim
esca
les
+
FTS
Prep
arati
on
1 3 4 7 8 11 14 18 21 28Week No:
To find out time required to complete a project – calculate backward from Implementation date
Star
t
PLANNING TOOL EXAMPLE
13
Activity 4
✈Assessment of present operations
✈ Identification of positive and negative
✈ Benchmark
✈Avoids repeats of design flaws
14
4 – Analysis of the reference scenario
Activity 5
✈Set success criteria
✈Select Safety Management system
✈Select Safety Assessment Methodology
✈What evidence is needed to prove safety of design
15
5 – Select Performance Criteria, Safety Policy and Criteria
Activity 6
✈Fleet capability
✈Traffic sample (distribution & assignment)
✈Rwy in use
✈Met assumptions
✈CNS assumptions 16
6 – Agree on ATM/CNS assumptions
Activity 6
17
6 – Agree on ATM/CNS assumptions
Activity 7
✈ 1st Design Routes
✈ 2nd Initial Procedure Design Analysis
✈ 3rd Define the airspace volumes and sectorise these, if needed
Iterations necessary!
18
7 – Design the Airspace
Activity 7
✈Arrivals
✈Departures
✈ Transit
✈VFR
✈Military
19
7 – Design the Airspace
AVOID trying to fit the routes into the existing airspace volumes
Activity 8
✈ Capability/functionality needed?
✈ Fleet capability/functionality available?
✈ Coverage provided by available Navaid infrastructure?
✈ Design according to ICAO Doc 8168 and Doc 9905 ✈ Initiation ✈ Collect & Validate Data ✈ Create Conceptual Design ✈ Review by Stakeholders
20
8 – Initial Procedural Design
Activity 9
9- Design Airspace Volumes and Sectors
✈Sectorisation
✈Airspace volume
✈Iterations possible
21
Activity 10
10 – Select ICAO Navigation specification
✈Review NAV specs
✈Identify appropriate spec
✈Go to planning and Implementation
✈If no appropriate spec ✈Apply Trade off
22
Activity 11
11 – Airspace Concept Validation ✈Prove ATM operability & validity
✈Assess objectives
✈Indentify possible weak points
✈Provide evidence and proof to support Safety Assessment
23
CONCEPT VALIDATION
24
Activity 12
12- Finalisation of procedure design ✈Design according to ICAO Doc 8168 and Doc 9905
✈Apply Criteria ✈Document and Store ✈Support Safety Assessment
✈Output: ✈Draft procedure layouts ✈Calculation outputs ✈Textual description of procedure
25
Activity 13
13- Procedure validation ✈Verification of terrain, obstacle and aeronautical
data used to support design ✈Validate intended use of procedure (match to
conceptual design) ✈Validate correct application of criteria ✈Validate flyability and human factors (charting) ✈ Flight Inspection (if required)
26
Activity 14
14- Implementation planning ✈Pre-implementation review
✈Design team available
✈Monitor process
27
Activity 15
15 - Implementation
✈Monitor process
✈Support OPS
✈Redundancy or contingency procedures
✈Support controllers and pilots
28
Activity 16
✈Post Implementation Review
✈Keep LOG
✈Assess if objectives are met
✈Measure!
✈System safety assessment – collect evidence
29
Lessons Learned
✈RNAV implementation in some regions over past 15 years has highlighted some issues.
✈The following slides list a few of those issues.
30
RNAV 5 implementation en-route airspace
✈ Selecting the right Nav Spec can be a challenge… sometimes there are more older aircraft than expected
✈ Roll out airspace changes over time: avoid multiple airspace changes at the same time as the PBN switch on date
✈ ‘Switch on’ PBN in the Terminal Airspace should be matched by ‘switch on’ in continental en route…
31
RNAV 1 and 2 implementation
✈Aircraft populations may not make ‘cleaner’ turns because of PBN … watch turn angles in design
✈ Co-ordination with stakeholders is a pre-requisite for success
✈ The number of SIDs/STARs at some major airports increased significantly which caused problems for operators with limited data base storage space.
✈ Education needed on RNAV and RNP
32
THANK YOU
33