Trajectory-Based Operations (TBO) - Joint Planning and ...
Trajectory-Based Operations (TBO) - Joint Planning and ...
Trajectory-Based Operations (TBO) - Joint Planning and ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Trajectory</strong>-<strong>Based</strong> <strong>Operations</strong> (<strong>TBO</strong>)<br />
Study Team Report<br />
It is important to emphasize that <strong>TBO</strong> is about choices. Once received, choices are negotiated,<br />
accepted, <strong>and</strong> then executed with precision. As the airspace traffic density increases, there is greater<br />
need for precision performance. But <strong>TBO</strong> can function at any level of precision. It is the execution of<br />
the agreement that assures separation. Strategically, automation must provide choices to the<br />
operator/user that resolve downstream conflicts <strong>and</strong> address flows. Weather is integrated into the<br />
decisions that must be made both strategically <strong>and</strong> tactically. As the number of strategic decisions rise,<br />
the number of tactical interventions will diminish, balancing workload both in the air <strong>and</strong> on the<br />
ground. However, the amount of pre-planning for the flight will likely increase, <strong>and</strong> the interchange<br />
between airline operations <strong>and</strong> the ANSP will rise as trajectories are used to strategically manage the<br />
volume of traffic.<br />
In communications, <strong>TBO</strong> is highly dependent on ground-ground connectivity for network-centric<br />
operations <strong>and</strong> data link for negotiations, agreement, <strong>and</strong> validation of execution of any given 4DT.<br />
But one data link pipe does not represent a single solution. Because <strong>TBO</strong> communications are mostly<br />
in a strategic time frame, the urgency of connectivity is unnecessary for a majority of the transactions.<br />
Multiple paths of communications can be used. The Study Team has made several recommendations<br />
on developing the messaging content <strong>and</strong> requirements for <strong>TBO</strong> because of the urgency in getting to a<br />
set of requirements. The requirements are more about the information flows between systems than<br />
about the performance of the link. A total of 46 recommendations have been offered for further action,<br />
ranging from better definitions of operational improvements to initiating the safety case for <strong>TBO</strong>.<br />
With respect to aviation security, <strong>TBO</strong> represents one of the layers of adaptive security. Intent is a<br />
powerful tool in monitoring conformance. Likewise, in flight planning there are opportunities to build<br />
in authentication, from submittal of a plan to starting the aircraft. In-flight performance puts bounds<br />
around the aircraft <strong>and</strong> deviations from these bounds have separation consequences that must be<br />
addressed.<br />
Environmentally, <strong>TBO</strong> provides an opportunity to meet improved noise performance by more closely<br />
defining flight tracks. <strong>TBO</strong> offers savings in fuel burn, at the airport, during climb, through the use of<br />
cruise climb, <strong>and</strong> the optimized arrivals to an airport. Noise, emissions, <strong>and</strong> fuel savings translate into<br />
tangible environmental benefits <strong>and</strong> the procedures lead to saving cost of operations.<br />
Finally, The <strong>TBO</strong> Study Team recognizes that this is the start of a greater debate on the details of<br />
<strong>TBO</strong>. Our approach was to provide information on how <strong>TBO</strong> would work in the context of operational<br />
scenarios. Much work must follow. Critical among this work is the beginning of a safety case <strong>and</strong> the<br />
necessary analyses to reach decisions on fundamentally changing how aircraft are separated. This<br />
safety case is followed by the functional requirements for <strong>TBO</strong> <strong>and</strong> a significant discussion on<br />
definition of requirements for automation’s performance.<br />
<strong>Joint</strong> <strong>Planning</strong> <strong>and</strong> Development Office<br />
ES – 2