Trajectory-Based Operations (TBO) - Joint Planning and ...

More documents

Recommendations

Info

Trajectory-Based Operations (TBO) Study Team Report In merging and sequencing, the arrivals using OPDs are set up in the cruise segment of flight well before TOD. The sequence is continually refined and exchanged with the arrival TBO automation. En route TBO automation: • Supports arrival and departure airspace management integration, with sharing of flight object and intent • Supports en route access for GA through terminal airspace • Supports time-based metering into en route traffic streams • Receives departure-metered flights on RNAV and RNAV/RNP routes • Supports definition of, and operations within, flow corridors for high-density traffic • Supports a variety of separation standards, including three miles en route • Provides ability to request modifications of trajectories and support trajectory negotiation and conflict resolution • Provides procedures and safety algorithms for delegation of separation to the aircraft • Manages aircraft access to SUA and provides the military with boundaries and operating times for dynamically created SUA • Coordinates 4DT information with ANSP TBO evaluation services so that individual 4DT trajectories are synchronized • Provides tactical and strategic separation management • Provides wake turbulence separation performance in sequencing, as well as merging and spacing • Provides the means to meet en route environmental objectives, including supersonic boom management, emissions, fuel efficiency through cruise climb and best cruise speeds, and overflight of environmentally sensitive areas. OI-0307 Integrated Arrival/Departure Airspace Management OI-0309 Use Optimized Profile Descent OI-0310 Improved GA Access to Traverse Terminal Areas OI-0325 Time-Based Metering Using RNAV and RNP Route Assignments OI-0337 Flow Corridors - Level 1 Static OI-0343 Reduced Horizontal Separation Standards, En Route - 3 Miles OI-0360 Automation-Assisted Trajectory Negotiation and Conflict Resolution OI-0363 Delegated Separation - Complex Procedures OI-0365 Advanced Management of Airspace for Special Use OI-0368 Flow Corridors - Level 2 Dynamic OI-0369 Automated Negotiation/Separation Management OI-0370 Trajectory-Based Management - Gate-To-Gate OI-0387 Dynamic, Pair-wise Wake Turbulence Separation OI-6005 Environmentally and Energy Favorable En Route Operations - Level 1 OI-6022 Environmentally and Energy Favorable En Route Operations - Level 2 Joint Planning and Development Office 87
Trajectory-Based Operations (TBO) Study Team Report 17.10 Arrival/Approach and Landing TBO Automation This automation replicates all the functions first described for departures, and integrates the exchange of information relating to arrivals to the surface movement TBO automation. The capabilities are highly coupled with en route TBO automation. The big difference between the arrival/approach and landing TBO automation and en route TBO automation is the number of tools available to manage sequencing, and merging and spacing for OPDs, closely spaced parallel runway operations, wake turbulence spacing, and mixed equipage in the arrival streams. The information exchange between en route TBO automation and arrival/approach and landing TBO automation is essential for setting TOD due to the fact that this sequencing happens well into the cruise phase of flight, and is updated as aircraft get closer to their TOD position and time. There is a limited amount of time that can be gained or lost from TOD to touchdown. 25 Arrival/approach and landing TBO automation is continuously updating the landing sequence based on the flight object, current position, and intent for all aircraft being handled. The automation also identifies potential gaps in the arrival stream to handle aircraft being vectored that are not capable of TBO operations. Best-equipped aircraft get the benefits of TBO and less equipped aircraft must accept gaps in the arrival streams for high-density airports and metroplex terminal operations. Such gaps are allocated in planning stages and adjusted to account for uncertainty. The automation injects new gaps when needed and, to the extent practical, may delay non-equipped aircraft for which the gap is being created. Arrival/approach and landing TBO automation uses a combination of published arrival paths that are connected to approaches, metering fixes, dynamic merge points, and variable descent points at TOD to set the landing sequence and merge aircraft. Some aircraft are capable of doing their own merge and many aircraft are capable of sustaining spacing through the use of ADS-B and cockpit display of traffic information. The arrival/approach and landing TBO automation also has conformance monitoring that relies on the same parameters as used in climb, but with different, lower acceptable variability. To help manage the variability, the arrival/approach and landing TBO automation uses learning capabilities from the tracking and intent of previous flights, then leverages surveillance information to refine winds and compression on arrival. By using surveillance and knowledge of aircraft performance, winds can be estimated and corrections applied. In addition, using archived same day and same hour flight path information, algorithms can apply corrections in near-real time to refine to seconds of performance. 25 This is a rich area of research to identify the timing spread (+/-) for TOD and various other merge or metering points along the path from cruise to touchdown. Joint Planning and Development Office 88
Page 1 and 2:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Page 3 and 4:
Trajectory-Based Operations (TBO) S
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46: Trajectory-Based Operations (TBO) S
Page 71 and 72: 15.0 Phoenix To Bozeman Scenario Tr
Page 95: Trajectory-Based Operations (TBO) S
Page 145: Trajectory-Based Operations (TBO) O
show all

Trajectory-Based Operations (TBO) - Joint Planning and ...

Create successful ePaper yourself

Delete template?

Save as template?