• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

Wrong ILS Procedure Turn following

Scheduled Pinned Locked Moved RJ Professional
5 Posts 3 Posters 334 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • sg_aviationS Offline
    sg_aviationS Offline
    sg_aviation
    wrote on last edited by
    #1

    Hi y'all,

    I just arrived at Iqaluit, NU (CYFB) ILS 33 via YFB VOR and decided to fly the outbound leg & procedure turn by FMS/LNAV and noticed a strange flight path that shouldn't happen despite limited FMS capabilities:

    unknown_2024.11.13-23.48.png

    The red line marks the ILS Localizer that should be followed inbound right after the procedure turn. Instead it appears that the lateral path is offset by several degrees to the right inbound TIBEG (yellow line). Since TIBEG is already past the intercept altitude of 2100 ft it lead to a difficult situation where GS was captured before LOC.

    The same could be observed on the navigation display:

    unknown_2024.11.13-23.50.jpg

    It appears that the intercept waypoints like D161D are displaced, but can't tell if that comes from the general Navigraph AIRAC data or interpretation by the aircraft.

    Any input is appreciated.

    Regards,

    Stefan

    1 Reply Last reply
    0
  • M Offline
    M Offline
    mmcmah
    wrote on last edited by
    #2

    I'm not sure about your questions, but I'll highlight a few things that I notice as I look at the chart and your pictures:

    1. I think the approach is ILS34 with a course of 341. There is actually supposed to Beno circling on the side of the red line that you're trying to be on (and possibly delimited by the yellow line, as shown in the chart:

    image.jpeg

    1. TIBEG is the first waypoint on the approach and the autopilot seems to be trying to get you to that point to intercept the localizer and continue on the right course.

    2. The intercept altitude is not 2100. It's actually supposed to be interceptedno higher than 2100, but at TIBEG, The intercept altitude is 1690:

    image.jpeg

    image.jpeg

    sg_aviationS 1 Reply Last reply
    0
  • sg_aviationS Offline
    sg_aviationS Offline
    sg_aviation
    replied to mmcmah on last edited by
    #3

    @mmcmah said in Wrong ILS Procedure Turn following:

    Thanks for your detailed input.

    1. I think the approach is ILS34 with a course of 341. There is actually supposed to Beno circling on the side of the red line that you're trying to be on (and possibly delimited by the yellow line, as shown in the chart:

    I believe this is coincidence, since the no circling line relates to RW34, not TIBEG.

    1. TIBEG is the first waypoint on the approach and the autopilot seems to be trying to get you to that point to intercept the localizer and continue on the right course.
    2. The intercept altitude is not 2100. It's actually supposed to be intercepted no higher than 2100, but at TIBEG, The intercept altitude is 1690:

    The default intercept altitude is 2100 and for this I need to be on the LOC before TIBEG. For this reason the virtual waypoint D161D is inserted before TIBEG, however due to the offset the whole procedure cannot not work.

    The main question is, why is D161D entered with an offset? I think I will re-post this over at Navigraph to see if it relates to their source data.

    1 Reply Last reply
    0
  • sg_aviationS Offline
    sg_aviationS Offline
    sg_aviation
    wrote on last edited by
    #4

    According to Navigraph, the fix D161D is not part of their database. This indicates that it is generated by JF Avro RJ to support the procedure turn.

    @Mark Kindly take a look at the mis-placement of the fix.

    1 Reply Last reply
    0
  • MarkM Offline
    MarkM Offline
    Mark JF Staff
    wrote on last edited by
    #5

    I have just checked this in the nav data and the "D161D" fix does appear in the AIRAC 2301 navdata that is included with the RJ (I haven't checked the latest 2411 cycle but I assume it will too):

    Screenshot (48516).png

    As far as I'm aware, all of the navaids used by the FMS (and displayed on the ND) are pulled directly from the navdata. We're not creating any additional navaids, or moving any of the existing navaids on procedures, we're just using whatever navaids are listed in the procedure and the coordinates associated with them.

    Mark - Just Flight

    Just Flight Development Assistant

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users