Trajectory-Based Operations (TBO) - Joint Planning and ...
Trajectory-Based Operations (TBO) - Joint Planning and ...
Trajectory-Based Operations (TBO) - Joint Planning and ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Trajectory</strong>-<strong>Based</strong> <strong>Operations</strong> (<strong>TBO</strong>)<br />
Study Team Report<br />
The concept of vertical performance will likely need to start as boundaries of vertical airspace, similar<br />
to what is used in an instrument approach:<br />
These boundaries would represent known constraints that the aircraft would be capable of meeting, but<br />
would allow the aircraft to set the most optimum climb or descent profile to pass through these<br />
boundaries of vertical space. The vertical boundaries are tied to a 2D point in space. This waypoint<br />
could have a time performance, as well. The ANSP would use these boundaries for conformance<br />
monitoring, <strong>and</strong> the vertical airspace boundaries would represent conformance constraints. In selecting<br />
the altitude windows that become conformance boundaries, the ANSP would initially use information<br />
in the flight object relating to the requested climb profile provided in flight planning. After takeoff, as<br />
the aircraft begins its climb, it could provide a new vertical intent to the ANSP to narrow the airspace<br />
that must be reserved for the flight.<br />
7.0 The Fourth Dimension of Time<br />
<strong>TBO</strong> is dependent on time, <strong>and</strong> this time must be the same in automation, both in the air <strong>and</strong> on the<br />
ground. At a minimum, clocks must be synchronized to the nearest second <strong>and</strong> set before taxi out.<br />
Time can be derived from GNSS, uplinked as part of a broadcast message, or set manually using an<br />
approved source of time. This synchronization is verified by the transmission of onboard time in data<br />
link messages. While the time precision of flight performance is greater than a single second, seconds<br />
of precision are specified for certain airspace <strong>and</strong> traffic density.<br />
RTP varies with the flight operation <strong>and</strong> the density of traffic. Representative time performance<br />
considers significant reductions in variability over the current NAS that, by itself, will gain capacity<br />
<strong>and</strong> efficiency. For example, a reduction in l<strong>and</strong>ing runway occupancy time—from over the threshold<br />
to exiting the runway—from 60 seconds to 45 seconds can produce 20 more arrivals per hour for that<br />
runway. To realize this reduction in variability, <strong>TBO</strong> plans <strong>and</strong> provides for the time precision required<br />
for the situation.<br />
As an example, on departure, a time to reach a position in space may be provided as a controlled time<br />
of arrival, expressed in seconds, to avoid or merge with crossing traffic, or to enable an uninterrupted<br />
climb without intermediate level offs <strong>and</strong> greater power requirements. Time becomes the controlling<br />
element for de-conflicting traffic <strong>and</strong> managing downstream flows.<br />
There are two types of time: absolute <strong>and</strong> relative. In absolute time, the aircraft is proceeding to a<br />
defined location in space at a prescribed time (hours, minutes, seconds of coordinated universal time<br />
<strong>Joint</strong> <strong>Planning</strong> <strong>and</strong> Development Office<br />
20