Implement fly-by fixes and turn anticipation #183
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When navigating from fix to fix, the current physics rules fly the aircraft within 0.5 km of one fix before turning to the next. When larger direction changes are required, aircraft will often anticipate the turn and “fly by” the waypoint rather than flying close to the fix, particularly when larger changes of direction are required. This avoids overshoot of the fix. See #174, /cc @nielsvdweide.
For aircraft navigating between two fixes, this change calculates the turn initiation distance as an aircraft FMC would, and starts the turn to the next fix at that point (to a maximum distance of 10km from the fix).
For course changes of < 20 degrees at 200 knots, there is no noticeable change since the turn initiation distance is small. At 90 degrees/200 knots, the turn starts 2.4km from the fix and increases from there for sharper turns.