Procedural control
From Wikipedia, the free encyclopedia
Procedural control is a method of providing air traffic control services without the use of radar. It is used in regions of the world, specifically sparsely-populated land areas and oceans, where provision of contiguous radar cover is either prohibitively expensive or is simply not feasible. It also may be used at very low-traffic airports, or at other airports at night when the traffic levels may not justify staffing the radar control positions, or as a back-up system in the case of radar failure.
Contents |
[edit] Separation
In air traffic control, the risk of aircraft colliding is managed by applying separation rules. These rules require aircraft to be separated by either a minimum vertical distance, or, if for some reason they cannot be separated vertically, by a minimum horizontal distance defined by various means. One of the means of determining horizontal separation is by a controller observing the radar returns of the aircraft to be at least a minimum horizontal distance apart. This is the essence of radar control and is probably the form of air traffic control most familiar to lay people.
However in times gone by radar was not very common, and in certain parts of the world today it still is not common, on grounds of cost or technical feasibility. Procedural control is a form of air traffic control that can be provided to aircraft in regions without radar, by providing horizontal separation based upon time, the geography of pre-determined routes, or aircraft position reports based upon ground-based navigation aids, for those aircraft that are not vertically separated.
[edit] Techniques of Procedural Control
The central rule of procedural control is that each aircraft is cleared onto a predetermined route (airway), and no aircraft travelling on the same or intersecting routes at the same level shall come within 15 minutes' flying time of another. There are, however, many cases when this is reduced. For example, it is 10 minutes in areas where pilots can determine the position of their aircraft with some accuracy using radio navigation aids (navaids).
Using procedural control, the controller does not need to maintain a mental picture of the current location of aircraft. Instead, each aircraft's Flight progress strip containing its route, altitude and estimated time over reporting points is compared against all others in the sector to determine if there are any conflicts. For those that conflict, the controller issues an altitude, speed or routing change that both separates the conflicting aircraft from each other, while still remaining separated from all others. After all conflicts have been resolved in this way, the sector is considered "separated" and the controller only needs to check again for conflicts when new aircraft are added, if an aircraft needs to change its altitude, or if the aircraft reaches a reporting point significantly earlier or later than previously estimated.
There are two main techniques to organize flight progress strips to most efficiently detect conflicts: grouped together by altitude, or grouped together by route intersection points (fix posting area). Altitude grouping is the easiest and most common method when most aircraft in the sector tend to be level at a cruising altitude, such as in trans-oceanic sectors. Each aircraft's strip is placed in a "bay" (labeled section of the strip rack) depending on its altitude. Because aircraft cruising at different altitudes will never conflict regardless of route of flight or estimated times, they don't need to be checked against each other. Only aircraft at the same altitude (i.e. in the same bay) need to be further evaluated. If an aircraft needs to transition to a new altitude (whether changing cruising level, or descending to or climbing from an airport), it only needs to be checked against others in the bays between the current altitude and destination altitude.
The fix posting area method is easier however when there are a lot of altitude changes because of numerous departures and arrivals within the sector. This is a more obscure method today because most airports around the world with significant enough traffic to warrant this technique have at least a radar covering the climbout and arrival area, and only need procedural control for points between (in which case altitude grouping is likely more efficient).
Nevertheless, the fix posting area method was the main technique used in U.S. enroute system prior to the 1960's, for example, when enroute radar became more widespread. This method was evolved from similar techniques used in railroad dispatch. It simplifies conflict detection because of the fact that aircraft on different routes can only possibly conflict at intersection points with other routes, or with aircraft on the same route. Each intersection point ("fix posting area") in the sector is made into a separate bay on the strip rack, and multiple strips are printed for each aircraft, one per bay. The controller then sorts strips within each bay by the estimated time the aircraft is expected over that point. Only aircraft estimated to cross within 10 minutes of each other are considered possible conflicts, at which point altitudes are then compared to determine if there actually is a conflict. Aircraft on the same route however (in either direction) must be checked for conflict regardless of time over the intersection.
As new altitudes are issued, all of the strips for that aircraft must be noted with the new data and separation checked again at all of the intersections it passes through. This is more laborious than the altitude method of grouping where only one strip is needed, but possible conflicts between multiple aircraft climbing and descending are easier to discern or discard this way since all intersection points and times are precalculated and laid out separately. With the altitude grouping method, if two aircraft are determined to conflict based on altitude, the controller must then manually determine the intersection points and times to further determine or rule out the conflict.
[edit] Procedural approaches
Every runway used by IFR aircraft normally has a procedural approach defined and published. This generally involves the aircraft flying over a navaid (or 'beacon') on or close to the airport (where the aircraft can hold if necessary), flying away from the airport on a set track whilst descending (going 'beacon outbound'), then at some point approximately ten miles from the airport turning back towards the airport aligned with the runway to make an approach (becoming 'inbound track established' or just 'established').
In procedural approach control, separation is maintained by only allowing one aircraft to be making an approach at any one time - the proceeding aircraft must either be in visual contact with the airport or have landed before the next aircraft is allowed to leave the hold and go beacon outbound.
At airports equipped with radar, procedural approaches are only normally used in the event of an aircraft suffering a radio failure, or for training purposes. At non-radar airports or when radar is not available, these become the only means of IFR flights making approaches to the airport.
At some non-radar airports the procedural approach may be combined with aerodrome control, thus providing a control service for all aircraft at the airport, and all in and outbound flights within it's terminal airspace. As most aircraft will be flying to/or from the same point within this airspace (i.e. the airport), procedural controllers use a variety of seperation standards to achieve a safe and expeditious flow of air traffic to and/or from the airport. One commonly used seperation in these locations is track separation, which states that two aircraft on different tracks to/from an navigational aid will be seperated from each other provided at least one is a minimum distance from the navaid. The distance needed will vary dependent on how far apart the tracks are. For example, two aircraft on tracks that are 60° apart do not have to be far from the navaid to be clear of each other in comparison to two aircraft whose tracks are, say 13° apart.
[edit] Airspace capacity
En-route jet aircraft tend to fly at roughly 8nm per minute: 15 minutes' flying could therefore equate to 120nm. This contrasts with standard separation on radar whilst en-route, which is 5nm. A typical procedural approach allows one aircraft to land every 8 minutes, whereas with radar this could be less than one landing every 90 seconds. It is therefore easy to see what a large increase in airspace capacity the provision of radar-based air traffic control gives.
[edit] External links
- UK CAP493 Manual of Air Traffic Services Part 1 Section 1, Chapter 3, heading 8 onwards (note that the UK does not implement the ICAO 15 minute rule and instead uses a standard 10 minute rule)
- FAA order 7110.65 U.S. Air Traffic Control rules for procedural separation (called "nonradar" in the U.S.).
