January 31, 20242 yr New A300 pilot here with a question about approach flight plan course line. At Auckland NZAA I've selected the ILS 23L approach with D165M transition as my course. It has a really nice, long arc that I was looking forward to flying (or watching the nav ap fly): However when I programmed this into the A300 FMS, it gets all whacky and creates some crazy S curves that won't be flyable. Why is this? And will it actually try to literally fly this route or will it understand what it needs to do and fly more like the first image?
January 31, 20242 yr I would switch off the option for curved ND Tracks. The real A300's computer is incapable of drawing these kind of lines. And I would venture the guess that it will not be able to fly an arc, since the computer does not even know how to draw one.
February 1, 20242 yr I would fly the arc manually, then intercept the ILS. I'm not sure a real non-Epic A300 could fly an arc solely on the AP, it might require some HDG mode if staying in AP, or manual flying, although I don't fly one in real life that's my guess. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
February 1, 20242 yr Author 3 hours ago, Farlis said: I would switch off the option for curved ND Tracks. The real A300's computer is incapable of drawing these kind of lines. And I would venture the guess that it will not be able to fly an arc, since the computer does not even know how to draw one. 1 hour ago, Mace said: I would fly the arc manually, then intercept the ILS. I'm not sure a real non-Epic A300 could fly an arc solely on the AP, it might require some HDG mode if staying in AP, or manual flying, although I don't fly one in real life that's my guess. something more interesting: upon closer inspection of the two routes it seems the A300 has placed the D051M waypoint in the wrong place, which seems to have caused the crazy wavy line to poof out on the side. if you look at that waypoint on the map it's aligned with the runway heading. not sure why the discrepancy, but I discovered it by turning curved ND tracks off and it still made a super funky shape. Edited February 1, 20242 yr by dresoccer4
February 1, 20242 yr Am i right that the A300 is not using Navigraph Database but the in-sim one? If thats the case it might be a reason for the misaligned FIX. Intel i9-13900K | Gigabyte Z790 Aorus Master | RTX4090 | 2x16GB Corsair Vengeance DDR5-6000 | Be quiet! Pure Loop 2 FX AiO | Win 11
February 1, 20242 yr Author 18 hours ago, ThomseN_inc said: Am i right that the A300 is not using Navigraph Database but the in-sim one? If thats the case it might be a reason for the misaligned FIX. I believe you are correct, however I have upgraded both in-sim nav data and LittleNavMap data to latest 2401 airac so the should match. not sure whats going on. will move on and change it up manually now though Edited February 1, 20242 yr by dresoccer4
February 1, 20242 yr 18 hours ago, ThomseN_inc said: Am i right that the A300 is not using Navigraph Database but the in-sim one? If thats the case it might be a reason for the misaligned FIX. If you replace default MSFS NavBlue nav data with Navigraph MSFS core nav data then the A300 will be using Navigraph even though it does not have its own dedicated Navigraph database Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
February 2, 20242 yr This has happened to me with every arc approach I’ve added, it’s usually a DME waypoint out of place. Airplane is drawing it correctly it just is importing bad data I think You should provide this as feedback on their Discord. I was going to fly when I get home tonight so can maybe come up with some other examples and share as well. Edited February 2, 20242 yr by mspencer
Archived
This topic is now archived and is closed to further replies.