9 October 2025
desk@falconatc.com
Separation integrity engine
Before now no air traffic control simulator in the world could detect errors aside from basic separation losses of 1000 feet vertically and 3 or 5 miles horizontally. However, there are a few more rules than just “don’t put the planes close together.”
“We’re separated from the other cars, so separation is achieved!”
Future conflicts can be greedily predicted by using a predicted intercept vector (PIV). A PIV takes the tracks of two aircraft and returns the closest point they will be. While the tracks of two aircraft may overlap, they may not be a close encounter depending on where the aircraft are along the track.
The SIE uses a PIV to determine whether a horizontal separation incursion will occur, and determines that two aircraft are at risk of collision where vertical separation does not exist.
Determining vertical separation assurance
It’s okay to break horizontal separation so long as vertical separation is achieved. So the SIE needs to be able to also determine vertical separation. Assessing either separation standard, whether individually or together, is trivial. So long as aircraft are separated by at least 1000 feet (which includes the range between current and cleared altitudes) aircraft are considered separated.
Other rules
In a terminal environment there are a few rules on separation assurance. That is to say, a loss of separation can occur even if the aircraft are more than 3 or 5 miles and 1000 feet apart. A few examples are turning a jet into the path of an early turn propeller aircraft without vertical separation assured, or turning more than 135 degrees left or right from runway heading without vertical separation from an airport with tower release. The SIE is able to absorb near limitless rules and analyze errors.