RADIAL INTERCEPTION: GEOMETRY AND IMPLEMENTATION BOUNDARIES
Fenix V3 documents revised lateral path construction and intercept rendering. The supplied Thales standard explains a particular RADIAL IN/OUT interface, but the current primary evidence used here does not verify every corresponding V3 field and branch. This topic therefore explains the geometry and guidance-state distinction. It supplies no legacy menu recipe or binding presented as a current Fenix operating procedure. [66, PDF pp. 351-356] [82, V3.0.0.7438; lateral-intercept path construction/rendering]
1. Define the actual clearance geometrically. A radial is a line referenced from a place; an inbound path along it is different from an outbound path and need not share its numerical heading. Identify the intended reference and direction before modifying the flight-management route. Confusing radial number with an inbound heading can produce a geometrically valid-looking line pointing in the wrong operational direction. [66, PDF pp. 351-356] [82, V3.0.0.7438; lateral-intercept path construction/rendering]
2. Separate direct-to from interception. A direct clearance concerns a path towards the target from present position. An intercept requirement concerns joining a specified line. The manufacturer's model treats them as separate functions. That distinction remains useful when reading a V3 ND preview: identify which path is actually being proposed, rather than choosing a command because it happens to contain the right waypoint name. [66, PDF pp. 351-356] [82, V3.0.0.7438; lateral-intercept path construction/rendering]
3. Distinguish armed from captured guidance. The source's intercept examples show why a desired line can exist while NAV remains armed and heading/track guidance is active. A map line alone is not mode confirmation. Read the actual V3 FMA and trajectory response. An unachievable intercept is not corrected merely by clearing a message or making the line appear continuous on another page. [66, PDF pp. 351-356] [82, V3.0.0.7438; lateral-intercept path construction/rendering]
4. Preserve termination meaning. An outbound line can require a manual termination and a separately established onward route. It is not automatically a complete continuation to the destination. When inspecting the loaded V3 plan, read its actual leg type, continuation and discontinuity. Retain current clearance and chart context rather than assuming that an older manufacturer's example defines the complete current simulator sequence. [66, PDF pp. 351-356] [82, V3.0.0.7438; lateral-intercept path construction/rendering]
5. Keep unsupported interface detail out of the procedure. The exact availability, input grammar, preview and insertion behaviour of a V3 radial-specific function require current implementation evidence before being published as keystrokes. Until that is established, this topic is the technical interpretation layer alongside the verified current direct-to/intercept guidance. It does not prescribe old radial-entry numbers, recovery messages or a simulated workaround from a pre-V3 build. [66, PDF pp. 351-356] [82, V3.0.0.7438; lateral-intercept path construction/rendering]