Download presentation
1
FF-ICE/1 and ASBU- Block 1
Stéphane Mondoloni
2
FF-ICE Step 1 12th Air Navigation Conference, Recommendation 3/5:
Operational performance through flight and flow – information for a collaborative environment That the conference: Endorse the aviation system block upgrade module relating to flight and flow – information for a collaborative environment included in Block 1 and recommend that ICAO use it as a basis of its work programme on the subject; That states: Support the development of a flight information exchange model; FF-ICE Step 1 refers to the Block 1 FICE module © 2013 The MITRE Corporation. All rights reserved.
3
Aviation System Block Upgrades
Each Block is composed of modules reflecting capabilities Modules assigned to one of four Performance Improvement Areas (PIAs): Airport Operations Globally Interoperable Systems and Data Optimum Capacity and Flexible Flights Efficient Flight Paths Block 1 available between 2018 to 2023 Each module is mapped to the concept components in the ICAO Global ATM Operational Concept (ICAO Doc. 9854) © 2013 The MITRE Corporation. All rights reserved.
4
Summary of Block 1 Modules†
Airspace Organization & Management Aerodrome Operations Demand Capacity Balancing Traffic Synchronization Airspace User Operations Conflict Management Service Delivery Management Module Module Name AOM AO DCB TS AUO CM SDM Optimized Airport Accessibility Increased runway throughput through dynamic wake turbulence separation Improved airport operations through departure, surface and arrival management Enhanced safety and efficiency of surface operations – SURF, SURF-IA, EVS Optimized airport operations through A-CDM total airport management Remotely operated aerodrome control Increased interoperability, efficiency and capacity through FF-ICE/1 before departure Service improvement through integration of all digital information Performance improvement through the application of SWIM Enhanced operational decisions through integrated MET information Improved operations through optimized ATS routing Enhanced flow performance through network operational planning Improved capacity and efficiency through interval management Ground-based safety nets on approach Improved flexibility and efficiency in descent profiles using VNAV Improved traffic synchronization and initial trajectory-based operations Initial integration of remotely piloted aircraft into non-segregated airspace B1-APTA Airport Operations B1-WAKE B1-RSEQ B1-SURF B1-ACDM Globally Interoperable Systems and Data B1-RATS B1-FICE B1-DATM B1-SWIM B1-AMET B1-FRTO Optimum Capacity & Flexible Flights B1-NOPS B1-ASEP B1-SNET B1-CDO Efficient Flight Path B1-TBO B1-RPAS †According to “Working document for the Aviation System Block Upgrades”, 28 March 2013 © 2013 The MITRE Corporation. All rights reserved.
5
ASBU B1 - FF-ICE Step 1 Module 4DT Implications
Early provision of flight intent Exchange of 4DT information between the AOC and the ASP Services include: Validation Nominal trajectory generation (in absence of user defined 4DT Negotiation (to address constraints) Update of flight information Subscription Knowledge of aircraft capabilities allows 4DTs closer to preferences Trajectory or slot negotiation pre-departure From the module description B1-FICE Implications for 4DT Continue to require predictions, additional information required Information required for validation of 4DT against other provided information A mechanism for negotiation of trajectory Inclusion of constraints required for 4DT Support for update of 4DT when information changes Additional information may be required to support subscription mechanisms Eligibility checking of 4DT against aircraft capabilities Inclusion of slots and target times for pre-departure negotiation © 2013 The MITRE Corporation. All rights reserved.
6
ASBU B1 Relationship to FF-ICE Step 1 4DT Airport Operations
B1-FICE 4DT Integration of PBN GLS procedures Extension to CAT II/III capability Procedure names in route for eligibility checking (route consistent w/ 4DT) B1-APTA Pairwise static wake separation matrix WTMA for runways < 2500 feet apart WTMD for runways < 2500 feet apart B1-WAKE Runway and time estimates for runway demand Target times for metering and departure control ETAs for meter schedule development Metering fix and TOD for OPD assignment Procedure names referenced for eligibility checking Enhanced surface management Departure and surface integration Extended arrival metering Utilization of RNAV/RNP routes B1-RSEQ B1-SURF Surface situational awareness Enhanced traffic situational awareness w/ indications and alerts Enhanced vision systems for taxi B1-ACDM Collaborative airport operations plan Airport performance framework with targets DST for execution & coordination of plan Sharing of resource and operations plans Real-time monitoring B1-RATS Runway and time estimates for runway demand Planning target times PIA: Airport Operations Remote provision of ATS for single aerodrome Remote provision of ATS for multiple aerodromes Remote provision of ATS for contingency situations © 2013 The MITRE Corporation. All rights reserved.
7
PIA: Globally Interoperable Systems & Data
ASBU B1 Relationship to FF-ICE Step 1 4DT Globally Interoperable Systems & Data B1-FICE 4DT B1-FICE Detail provided in prior slide B1-DATM Harmonized framework (FIXM, AIXM, WXXM) Format, structure and definitions consistent B1-SWIM SWIM for ground-ground application Distribution mechanism for FIXM information Information within FIXM may be required to support subscription B1-AMET MET Information provision MET Information Translation ATM Impact Conversion ATM Decision Support 4DT for demand estimation in impact conversion Trajectory options for ATM decision support Trajectory prediction inputs for ATM decision support B1-FRTO Free routing Reduced route spacing Dynamic resectorization Support for free routing in 4DT & eligibility checks Parallel Offset support (across multiple ANSP) Curved Approaches used in prediction for 4DT 4DT for demand estimation in resectorization B1-NOPS PIA: Globally Interoperable Systems & Data ATFM and ATFM-AOM integration Synchronization (TFM slots) Initial UDPP † Flexible use of Airspace Complexity Management 4DT for demand and complexity assessment TFM slots and target times ETAs for SAA entry times – compliance verification †UDPP requires further elaboration © 2013 The MITRE Corporation. All rights reserved.
8
PIA: Optimum Capacity and Flexible Flights
ASBU B1 Relationship to FF-ICE Step 1 4DT Optimum Capacity and Flexible Flights B1-FICE 4DT B1-ASEP Tactical trajectory for GIM-S (need prediction parameters) FIM start/end and defined interval † Interval management from TOD B1-SNET Approach path monitoring (alert of aircraft proximity to terrain) PIA: Optimum Capacity and Flexible Flights Note that the prediction parameters are obtained pre-departure & shared, but the tactical FIM/GIM parameters are provided during flight †Information presently being defined by SC-214. Initially consider as an extension. © 2013 The MITRE Corporation. All rights reserved.
9
ASBU B1 Relationship to FF-ICE Step 1 4DT Efficient Flight Path
B1-FICE 4DT Eligibility checking of procedure Vertical constraints in transition 4DT PBN with VNAV enabling CDOs B1-CDO 4DTRAD RTA/CTA into terminal D-OTIS DCL D-TAXI RTA/CTA constraints Incorporation of 4DTRAD info (if available) to update 4DT Incorporation of TOD Update of 4DT to reflect DCL clearances Update of 4DT times while on surface Update of 4DT to reflect CPDLC clearances B1-TBO B1-RPAS PIA: Efficient Flight Path Streamline process to access non-segregated airspace Defining airworthiness certification for RPA Defining operator certification Defining communication performance requirements Define remote pilot licensing agreements Define detect and avoid technology performance requirements Not for 4DT FIXM UAS data elements © 2013 The MITRE Corporation. All rights reserved.
10
Pre-departure information
AOC provides the route linked to a 4DT DEP procedure ARR procedure Altitude/airspeed constraint Requested altitudes/airspeeds Step climb w speed change Named points RWY OAT segment ROUTE Reference IAS/ predicted wind RWY TOD MF (significant point) 4DT points Lat/long/alt/time 4DT Type of TCP Estimated runway arr time Estimated runway dep time RWY © 2013 The MITRE Corporation. All rights reserved.
11
ANSP Consistency Verification (example)
4DT Matches Route/procedures Flight is eligible for procedures Application of rules & eligibility Constraints are correct and applied correctly Winds match DEP procedure ARR procedure Altitude/airspeed constraint Requested altitudes/airspeeds Step climb w speed change Named points RWY OAT segment (e.g., PBN / GLS procedure) ROUTE Reference IAS/ predicted wind RWY TOD MF (significant point) 4DT points Lat/long/alt/time 4DT Type of TCP Estimated runway arr time Estimated runway dep time RWY B1-FICE © 2013 The MITRE Corporation. All rights reserved.
12
Flow constrained area pre-departure
Multiple 4DTs used to estimate demand B1-AMET Forecast FCA017 RWY 4DT points Lat/long/alt/time FCA017 crossing 4DT point TMI imposed - ΔT Estimated runway arr time RWY Estimated runway dep time Trajectory update Time target (e.g. EDCT) Trajectory options may also be provided to enable TFM automation to assign a re-route versus a delay B1-NOPS © 2013 The MITRE Corporation. All rights reserved.
13
Clearance (pre-departure)
With DCL – route and modifications uplinked to flight deck Without DCL – initial route clearance via PDC/voice B1-TBO Clearance limit † (Annex 11, §3.7) FIR boundary Provides improved target times B1-ACDM †Ideally, this is not used as clearance is coordinated. Coordination pushes the clearance limit downstream. © 2013 The MITRE Corporation. All rights reserved.
14
Departure FIR boundary ΔT
Downstream FIR has improved estimates of demand Actual departure time B1-TBO ANSP updates the ETAs unequipped ΔT i4DTRAD B1-RSEQ e.g., Flights violating curfew or exceeding capacity can be delayed with speed versus hold on arrival. © 2013 The MITRE Corporation. All rights reserved.
15
Clearance provision - altitudes
Today, cleared altitudes are shared across boundary crossing Cleared to FL 240 D-ATSU C-ATSU FIR boundaries Today C-ATSU provides D-ATSU: Coordination point ETA at point CFL (FL240) Minimum altitude at point (180) Requested altitude Original 4DT Profile FL 240 Must cross at or above 180 B1-TBO from (if available, else ground automation) Additional info for 4DT downstream: Providing the predicted altitude at the coordination point Providing the speed at the coordination point Updating downstream 4DT times Providing pressure altitude correction information B1-ASEP (conducted by D-ATSU) B1-NOPS © 2013 The MITRE Corporation. All rights reserved.
16
Clearance provision – Altitude Block
Today, when block altitudes are required they are coordinated C-ATSU D-ATSU Block altitude clearance FL FIR boundary FL370 4DT Profile FL310 Must cross at or above 290 Today C-ATSU provides D-ATSU: Coordination point ETA at point Cleared block altitude (F310F370) Minimum altitude at point (F290A) B1-TBO from (if available, else ground automation) As before : Providing the predicted altitude at the coordination point Providing the speed at the coordination point Updating downstream 4DT times Providing pressure altitude correction information B1-ASEP (conducted by D-ATSU) B1-NOPS © 2013 The MITRE Corporation. All rights reserved.
17
Additional notification items
Today, APAC and NAT ICD support a variety of restrictions: Complete speed and/or level change by a point Restricted time of arrival at a point Combination of above Time of a speed and/or level change (can be reflected in 4DT) Also, lateral offsets in Field 14 (estimate data) For weather, deviations right, left or either up to a distance of route Fixed offsets, specified distance left or right of route Most restrictions represented as constraints in route (but not at time types) Offsets represented with clearance and in 4DT, optionally with 4D Point range in trajectory B1-FRTO ICAO, Asia/Pacific Regional Interface Control Document (ICD) For ATS Interfacility Data Communications (AIDC), Version 3.0, Montreal, Canada, September 2007 ICAO, The North Atlantic Common Coordination Interface Control Document, Version 1.3.1, Montreal, Canada, 2012 © 2013 The MITRE Corporation. All rights reserved.
18
Initial Proposal Today: CPL or EST (if pre-established) FIR boundary
TI message (PANS 4444) TRU Message (APAC): Heading (HDG) Cleared Flight level (CFL) Speed (SPD) Direct to (DCT) Assigned off-track deviation (OTD) D-ATSU C-ATSU FIR boundary Field 14 Field 15 Last significant point Route tailored Future (in addition to tactical info): 4DT profile (incl. sig. pts.) Preserve route past PPOS Speed at crossing Actual clearance 4DT Profile Provides downstream ATSU with improved 4DT estimates, and info for better high-fidelity prediction where necessary. B1-ASEP B1-TBO B1-NOPS B1-FRTO B1-RSEQ © 2013 The MITRE Corporation. All rights reserved.
19
Negotiation and Acceptance
Today: Accept message (ACP) if all good Coordination (CDN) message otherwise with Field 22 (amendment) D-ATSU C-ATSU Field 15 D-ATSU - Needs different route Field 14 D-ATSU - Needs different altitude FIR boundary Future: Negotiation Traj w/ altitude constraint† or Negotiation Traj w/ new route 4DT Profile Response: ACP, CDN or Reject (REJ) …and so on † N.B. exchange expected to be compact © 2013 The MITRE Corporation. All rights reserved.
20
Additional Capabilities
Interval Management Information provided pre-departure by AOC enables prediction of trajectory for problem setup Information provided via 4DTRAD may be used to update prediction for above Continuous Descent Operations Verify eligibility to use procedures Verification of 4DT that constraints applied for procedure Use of AOC data or 4DTRAD data for setup into procedure Extended Arrival Metering Use of AOC data or 4DTRAD for ETA estimation Use of RTA/CTA for meeting time B1-ASEP B1-TBO B1-CDO B1-TBO B1-RSEQ B1-TBO B1-TBO © 2013 The MITRE Corporation. All rights reserved.
21
Summary of 4DT © 2013 The MITRE Corporation. All rights reserved.
22
The 4DT itself is straightforward
A Trajectory consists of a sequence of 4D Trajectory Points Each 4D Trajectory Point has the following data: The 4DT Point describes its latitude, longitude, altitude and time (ETA) The Airspeed describes the IAS or Mach at the point The Groundspeed describes the IAS or Mach at the point The Met data describes the Temperature, wind magnitude and direction at the point The Altimeter setting identifies any non-standard barometric setting used for prediction The TCP Type identifies one of several enumerated types of TCP The Reference Point links the trajectory back to the route, if applicable RWY TOD MET – Wind/Temp 4DT points Lat/long/alt/time IAS Type of TCP GS Altimeter setting Reference Point Estimated runway arr time To route RWY Estimated runway dep time The 4DT points are a sample of a curvilinear trajectory prediction.
23
The 4DT is related to lots of other data
Trajectory-related data can be: Not trajectory-specific (e.g., aircraft make, model and series) Trajectory-specific (e.g., a route) You cannot change trajectory-specific data without obtaining a change in the 4DT. B1-FICE Requires 4DT Prediction FIXM needs to have items to support that prediction A “trajectory group” can be used to contain trajectory- specific data including the 4DT © 2013 The MITRE Corporation. All rights reserved.
24
Why do we need these groups?
Trajectory Negotiation, Coordination and Feedback Provision of Trajectory Options and Desired Trajectory Three types of groups are proposed: The agreed trajectory group Reflects known constraints, known clearances, known requests (e.g. planned step climbs) and trajectory plan (e.g. descent, planned arrival procedure) The negotiation trajectory group Provides a means to exchange trajectories with proposed modifications The sequence is expected to be transient The ranked trajectory group (highest-ranked is desired trajectory) A sequence of trajectories expressing preferences for routing against departure delay Rankings beyond the desired exist only pre-departure in the B1 timeframe © 2013 The MITRE Corporation. All rights reserved.
25
What should be in these trajectory groups?
Route Expanded Route Route Elements sequence of Each element contains Clearances Point name 4DT Trajectory-specific 4DT-related data Slot Information Lat/long Constraint(s)/Targets Altitude(s) Requested altitude Speed(s) Requested airspeed Not always included Cleared altitude Each ranked trajectory also includes TOS data Negotiation trajectories include source & sequence number Cleared airspeed This data is used as input to trajectory prediction © 2013 The MITRE Corporation. All rights reserved.
26
This is the copyright work of The MITRE Corporation and was produced for the U.S. Government under Contract Number DTFAWA-10-C and is subject to Federal Aviation Administration Acquisition Management System Clause , Rights in Data-General, Alt. III and Alt. IV (Oct. 1996). No other use other than that granted to the U.S. Government, or to those acting on behalf of the U.S. Government, under that Clause is authorized without the express written permission of The MITRE Corporation. For further information, please contact The MITRE Corporation, Contract Office, 7515 Colshire Drive, McLean, VA 22102, (703) The contents of this material reflect the views of the author and/or the Director of the Center for Advanced Aviation System Development, and do not necessarily reflect the views of the Federal Aviation Administration (FAA) or Department of Transportation (DOT). Neither the FAA nor the DOT makes any warranty or guarantee, or promise, expressed or implied, concerning the content or accuracy of the views expressed herein. 2013 The MITRE Corporation. The Government retains a nonexclusive, royalty-free right to publish or reproduce this document, or to allow others to do so, for “Government Purposes Only.” Fiscal Year: 2013 Outcome Number: 1 PBWP Reference: 1-3.G.1-5 © 2013 The MITRE Corporation. All rights reserved.
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.