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

More documents

Recommendations

Info

Trajectory-Based Operations (TBO) Study Team Report 18.15 Benefit of Imposing a 4DT Gate-to-Gate The surface aspects of TBO assume that time is important and can be met with sufficient precision as to increase airport throughput. The challenges may outweigh the benefits, and surface TBO raises some research and performance issues: • Surface TBO is primarily an issue over the precision of timing. Is this a flow issue or a separation issue? • How good does the takeoff time have to be and what factors are driving the precision? • Should the focus be on preferred performances in surface movement and leveraging surface movement learning 29 to make surface movement more predictable? • Is it necessary to use TBO for runway exit and taxi-in, especially after using surface movement learning to help reduce runway occupancy times? • How should surface TBO be used for intersection de-confliction and runway crossings? • What human-machine interface (HMI) is needed to provide guidance cues on progress toward meeting takeoff time and expediting runway exiting for both the pilot and the ANSP? • What HMI is needed to support sequencing and de-confliction of surface movement traffic for the ANSP? The benefits of the surface segment of gate-to-gate are less queue delay, sequencing of departures for optimal throughput, environmental gains by reducing emissions at the airport, fuel savings for the users, improvements in deicing, and prioritizing flights for the airspace requirements. Recommendation TBO-28 The TBO Study Team recommends a more detailed analysis of precision time performance on the airport surface in terms of safety, efficiency, capacity, and environmental benefits. 18.16 HMI Considerations for Surface Movement The TBO Study Team recognizes that surface movement is a visual activity, even in low visibility. The mix of electronic information on displays and out-the-window current operations can lead to headsdown time that may not be appropriate for surface movement. The current implementation of electronic flight bags in various positions and configurations for surface moving maps is starting down the path of more heads-down time. Will surface TBO drive a forward field of view requirement? What credit will be given for equipage for forward view? Recommendation TBO-29 Research on the concept of surface TBO needs to address the interface between the pilot and the automation in terms of placement, content, visual cues, techniques for identifying time progress, braking to exit, and other techniques to reduce runway occupancy times. 29 Surface movement learning refers to the process of using surface surveillance to learn aircraft behaviors like taxi time by operator, aircraft type, and gate, as well as preferred exits (wet, dry, day, night) from the runway, queue length optimization, taxi-out variability, etc. This information is then applied in surface movement automation. Joint Planning and Development Office 103
Trajectory-Based Operations (TBO) Study Team Report 18.17 Staffed and Remote NextGen Towers TBO is highly dependent on communications, navigation, and surveillance on the surface and in the equivalent of terminal airspace. Staffed and remote towers are alternatives to providing ANSP services at lower-activity airports. TBO is built on a concept that is flexible in providing RCP, Required Surveillance Performance (RSP), RNP, and now RTP. It can be adjusted for traffic density or airport/airspace complexity. The question is, how good does TBO have to be to support staffed and remote NextGen towers? The scenarios identified use of merging and spacing for arrivals and the possible use of departure times to meet merging into en route flows. TBO has benefits in eliminating the one-in-one-out operations in areas without surveillance coverage and for sequencing arrivals. However, these benefits may be small due to the density of traffic when compared with equipping staffed and remote towers with the necessary automation tools. Recommendation TBO-30 The TBO Study Team recommends creating a baseline staffed and baseline remote tower traffic model that can be used for answering operational questions at the lower traffic densities expected. These models can then be used to help define procedures, identify benefits, and integrate GA traffic more fully into TBO. 18.18 Time-Based RTA vs. Merging and Spacing The TBO Study Team began their deliberations with the understanding that there would be one RTA set in the FMS, consistent with today’s FMS capabilities. In RTP, the objective is to meet the required time with a precision consistent with the density of traffic. The key advantage throughout the concept is that the more precise the time performance the more precise the separation. In high-density airspace, another advantage is the reduction in variability on arrival and approach to actually produce additional arrivals per hour for the same runway. However, there is a balance between actual time performance and RTP. RTP occurs in merging and spacing. An RTA may only be valid at TOD for the case where the ANSP then asks the aircraft to merge, space, and follow another aircraft. At that point, the following aircraft shifts from absolute to relative time. As the sequence is developed for arrivals, and these arrival streams merged for the approach, an RTA to the initial approach fix becomes immaterial. In this case, the pilot is managing the interval between herself and the aircraft being followed. Recommendation TBO-31 Technology needs to be matured to integrate aircraft capabilities and controller practices relating to airborne merging and spacing. Interleaving of capable and not capable aircraft is an issue that requires procedural and decision support automation development, so that during the transition, TBO benefits can be realized on arrivals and approach. The capable aircraft will be able to merge and space on any aircraft, however, procedural research and development is required to understand how merging and spacing will work in both mixed equipage and high-density operations. 18.19 OI for Closely Spaced Runways Existing OIs on closely spaced runways fail to identify the targeted runway separation distances and do not cover the benefits of TBO in terms of getting aircraft aligned and sustaining separation during the maneuvers. Joint Planning and Development Office 104
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:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62: Trajectory-Based Operations (TBO) S
Page 71 and 72: 15.0 Phoenix To Bozeman Scenario Tr
Page 111: 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?