Skip to content

Commit e09926b

Browse files
docs(disco): add warning about SID and en-route discontinuity
* docs(disco): add warning about SID and en-route discontinuity * move content and add suggestion from slein * typo indicated by shomas * move sid admonition above star * formatting + add "further" below to tip * slein review * slein review 2 Co-authored-by: Sleinmaster <[email protected]> --------- Co-authored-by: Sleinmaster <[email protected]>
1 parent 33f8a8e commit e09926b

File tree

1 file changed

+29
-9
lines changed
  • docs/pilots-corner/advanced-guides/flight-planning

1 file changed

+29
-9
lines changed

docs/pilots-corner/advanced-guides/flight-planning/disco.md

Lines changed: 29 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -14,25 +14,19 @@ There are basically two types of discontinuities:
1414
- Discontinuities between two waypoints in the flight plan
1515
- Discontinuities after a MANUAL leg (Manual Termination)
1616

17-
### Special Case
18-
19-
!!! warning "STAR and Approach Discontinuity - Inaccuracy"
20-
If your STAR contains other waypoints after the IAF (initial approach fix) that you have selected via an approach transition (VIA), the FMS will not automatically connect the STAR to the approach at the IAF.
21-
22-
This is a small problem with our current implementation. It will be corrected when we update to version 2 (fms-v2) of our implementation, which contains even better simulation of the Honeywell FMS.
23-
2417
## Discontinuities Between Waypoints
2518

2619
!!! warning ""
27-
These discontinuities **should not** be cleared from the flight plan in normal operations.
20+
Based on the [special cases](#special-cases) below these discontinuities **should not** be cleared from the flight plan in normal operations.
2821

2922
Typically, you will notice a discontinuity in the following instances:
3023

3124
- Between the SID and the rest of your route.
3225
- Between the STAR and the selected approach.
3326

3427
!!! tip ""
35-
Approaches that are radar vectored without a MANUAL will also have a discontinuity by design. Please be aware of these approaches and follow the principles outlined below.
28+
Approaches that are radar vectored without a MANUAL will also have a discontinuity by design. Please be aware of these approaches and follow the principles outlined
29+
further below.
3630

3731
Ideally, the NAV mode automatically reverts to the HDG (TRK) mode and pilots should follow ATC guidance (if on network) or use the DIR TO function to proceed to the next
3832
waypoint on your flight plan.
@@ -42,6 +36,10 @@ waypoint on your flight plan.
4236
!!! info "Normal Discontinuity in the MCDU F-PLN Page"
4337
![Normal Discontinuity](../../assets/advanced-guides/disco/mcdu-discontinuity-1.png "Normal Discontinuity")
4438

39+
### Discontinuity After Deleting Waypoints
40+
41+
If you delete a waypoint manually, a discontinuity will be inserted instead. This discontinuity can be deleted to connect the route back together.
42+
4543
## Discontinuities After MANUAL Leg
4644

4745
Sometimes discontinuities are also part of a procedure to indicate that manual guidance is required (mostly directed by ATC). The preceding legs are called MANUAL legs (Manual Termination leg).
@@ -89,6 +87,28 @@ If the aircraft is flying into a MANUAL leg, NAV mode remains engaged and predic
8987
!!! warning "MANUAL label to be removed!"
9088
The MANUAL label on the ND will be removed in a future version, as it is not displayed in the real aircraft.
9189

90+
## Special Cases
91+
92+
!!! warning "SID and En-route F-PLN Discontinuity - Inaccuracy"
93+
**In most cases**, a discontinuity between the SID and your route is something that doesn't happen in real life.
94+
95+
With our current FMS, the A32NX will sometimes create a discontinuity that wouldn't typically be there. In these cases it would be okay to CLR the discontinuity -
96+
<span style="color:red">**provided you fully understand your routing and can identify that it would not cause any en-route issues**.</span>
97+
98+
!!! danger ""
99+
There are some important reasons why you shouldn't normally clear a discontinuity:
100+
101+
- Narrow turn radii between the two waypoints, where the discontinuity is present, which could not realistically be flown by the plane
102+
- Different [leg types](leg-types.md), which are not compatible to be connected together
103+
Even if the waypoints form a direct line, it's not completely safe to remove a discontinuity unless you understand the above points
104+
105+
This is a small problem with our current implementation. It will be corrected when we update to version 2 (fms-v2) of our implementation, which contains an even better
106+
simulation of the Honeywell FMS.
107+
108+
!!! warning "STAR and Approach Discontinuity - Inaccuracy"
109+
If your STAR contains other waypoints after the IAF (initial approach fix) that you have selected via an approach transition (VIA), the FMS will not automatically connect the STAR to the approach at the IAF.
92110

111+
This is a small problem with our current implementation. It will be corrected when we update to version 2 (fms-v2) of our implementation, which contains an even better
112+
simulation of the Honeywell FMS.
93113

94114

0 commit comments

Comments
 (0)