Using the operational segments browser
Who is this article for?
Users managing segments data.
Access to the segments browser is required.
The operational segments browser is a data browser accessible from the menu bar and toolbar, identified by the OPAS icon, which allows you to retrieve segment data and work alongside the operations browser.
1. Accessing the browser
The browser can be identified by the OPAS icon:
As with other browsers, you can open queries from this browser and retrieve data, as well as fill other browsers. The operational segments browser is most useful in tandem with the operations browser.
The image above shows an example with segment data retrieved.
2. Understanding standard columns
The browser displays the following columns:
- ID – unique ID number generated for each segment
- (Segment) Name – the name of the segment
- Operation No – the operation number or 'OpNum' the segment is related to
- Start Date – the time that the aircraft began the specific segment
- End Date – the time the aircraft ended the specific segment
- Duration – time in seconds that the aircraft spent in the segment
- Separation – the time in seconds between the start time of the current segment and the start time of the previous segment of the same type and on the same runway
- Next Segment – the ID of the next segment of the same type and on the same runway
- Prev Segment – the ID of the previous segment of the same type and on the same runway
- Runway – the runway the operation used
- Entry/Exit – this label is pulled from the zones defined as runway exit and entrance, and is determined by whether the track left the runway or entered the runway, depending on operation type (if the track cannot be detected for any reason, this will be left blank)
- Detected – denotes whether or not a ground track has been captured and the operation was detected entering and exiting zones (if the column is not ticked, segments have been generated for the arrival or departure, but no data will be entered regarding time spent in segments)
- Cause/Reason – you can edit the properties of a segment by double-clicking on the row or using the right-click menu to select from a custom drop-down that allows application of a cause or reason for the delay
- Excess Time – you can define what constitutes excess time in any of the defined segments, excluding taxi phases and on stand (for arrivals), with the amount of excess time in seconds shown in this column
- Excess Impact – levels of impact for excess can be defined if the operation exceeds custom thresholds set by you (the three threshold limits are minimal, moderate and significant)
- Tags – data tags may be added manually or automatically to any segment to add extra data or for ease of search, and this column displays the tags
- Is Violation? – you can create URM (update rules manager) rules that will define segments as violations (in most cases this would be if a segment time was in excess of a set threshold)
- Start Position – latitude and longitude of the first radar point that enters or begins the segment
- End Position – latitude and longitude of the last radar point that exits or ends the segment
3. Understanding CANSO additional columns
According to the CANSO airspace efficiency update, extra columns that reference a broader airspace analysis have been included in the segment browser:
- Start Bearing – calculated for each segment, this is the degrees off north that the aircraft segment is from the ARP (for example, if the aircraft enters the airspace from a northwest direction, that arriving segment may read as 45 degrees)
- End Bearing – as with start bearing, given that segments can be curved and change direction, this is the degrees off north from the ARP that segment ends at
- Ideal Distance – represents the most efficient path from the airport out to a 100 NM ring, the terminal efficiency area (it is calculated from a suitable corridor end for arrivals and departures and is used as a comparison against the actual distance along a flight track)
- Ideal Duration – calculated by taking the average speed of the flight track and is a comparison against the actual duration of the flight, in seconds
- Holding Zone Name – the name of the holding zone that the segment spent time in
- Holding Zone Circuits – the number of circuits or 'laps' that the segment conducted, passing through the holding zone gate as detected
- Delay – the delay time is calculated if there is excess time over a nominated time frame (in this case more than 300 seconds, which represents airspace difficulties that are out of the control of ATC, such as heavy weather or military flights)
4. Customising the browser layout
As with all browsers, you can turn columns on or off and save the layout to retain the settings for individual logins.