Joel S Posted February 24 Share Posted February 24 I'm testing RNAV functionality using RNAV Z 31L for KJFK (inibuilds). I set a direct to ZACHS instead of creating a direct path, it added a curved path (attached image). Secondly, the "3.0" descent angle at the FAF is missing from the flight plan. I believe that is the cause of P. DES. not arming. I duplicated the exact same approach on the A310 and the 3.0 appears and P. DES. arms as expected (see 2 attached images). Link to comment Share on other sites More sharing options...
Crabby Posted February 24 Share Posted February 24 Have you flown an RNAV with this plane? It is not like any other aircraft you have flown. Go to Youtube and search INI A300 RNAV tutorial. If you miss one step, it will not work just like in the real plane. As for the DCT TO, don't know never seen that. Mark "Crabby" Crabtree AAL311 | PHL I7-9700KF | 2070 Super | Honeycomb Alpha/Bravo | MFG Crosswind Link to comment Share on other sites More sharing options...
Joel S Posted February 24 Author Share Posted February 24 RNAV was fixed in an earlier version. I wanted to test it with the new 1.08. RNAV works the same way in both A310 and A300 and INIBUILDS has a YT tutorial on it. Link to comment Share on other sites More sharing options...
JetNoise Posted February 25 Share Posted February 25 Flew an RNAV into LFPG (Paris) this morning. Worked as expected, no issues. Oliver Link to comment Share on other sites More sharing options...
Joel S Posted February 25 Author Share Posted February 25 5 hours ago, JetNoise said: Flew an RNAV into LFPG (Paris) this morning. Worked as expected, no issues. Oliver Did you verify that the FAF had a "3.00" above it in the flight plan (same as my pic above)? Link to comment Share on other sites More sharing options...
Joel S Posted February 25 Author Share Posted February 25 Here is a screenshot from INIBUILDS YT video - EFB & Approaches - A310 | Part 2. I circled the "3.00" on both waypoints after the FAF. If this is missing from the flightplan, then I believe that's why the A300 will not arm P. DES. in blue. Link to comment Share on other sites More sharing options...
Crabby Posted February 26 Share Posted February 26 1 hour ago, Joel S said: Here is a screenshot from INIBUILDS YT video - EFB & Approaches - A310 | Part 2. I circled the "3.00" on both waypoints after the FAF. If this is missing from the flightplan, then I believe that's why the A300 will not arm P. DES. in blue. No, there are a number of reasons it won't arm. 1. Not at platform altitude and in some other mode other than profile. I am normally in ALT HOLD 2. Did not enter the MDA from the chart on the Approach page. 3. Did not activate the approach on the approach page. I never look at the legs page to set up and activate an approach. The 3.00 that is important is on the Approach page, and when you activate it will read how far above or below that 3.0 you are. Mark "Crabby" Crabtree AAL311 | PHL I7-9700KF | 2070 Super | Honeycomb Alpha/Bravo | MFG Crosswind Link to comment Share on other sites More sharing options...
Joel S Posted February 26 Author Share Posted February 26 (edited) 52 minutes ago, Crabby said: No, there are a number of reasons it won't arm. 1. Not at platform altitude and in some other mode other than profile. I am normally in ALT HOLD 2. Did not enter the MDA from the chart on the Approach page. 3. Did not activate the approach on the approach page. I never look at the legs page to set up and activate an approach. The 3.00 that is important is on the Approach page, and when you activate it will read how far above or below that 3.0 you are. While everything you say is true, those are not the reasons for this issue. I'm at platform altitude in ALT HOLD mode. I'm in NAV mode. I entered a MDA. I pressed FINAL 3.0. I saw the VDEV value indicating how much above or below profile the plane is. At that point I should be able to press PROFILE and P.DES. should arm in blue. It does not and I believe it's because the FMC doesn't have a -3.00 degree FPA programmed. I've now tried a dozen RNAV approaches at a few different airports and NONE of them have it programmed into the FMC. However, using the A310, ALL of these same RNAV approaches have 3.00 programmed into the FMC. I wish I kept a copy of v1.0.6 to rollback and confirm that it used to work. Edited February 26 by Joel S Link to comment Share on other sites More sharing options...
JetNoise Posted February 26 Share Posted February 26 10 hours ago, Joel S said: Did you verify that the FAF had a "3.00" above it in the flight plan (same as my pic above)? Yes Link to comment Share on other sites More sharing options...
JetNoise Posted February 26 Share Posted February 26 4 minutes ago, JetNoise said: Yes Disregard, i only checked for the FINAL 3 ... Link to comment Share on other sites More sharing options...
Joel S Posted February 28 Author Share Posted February 28 Looks like v1.0.9 fixed the RNAV issue. I can arm P.DES. in blue by clicking PROFILE. However, the MDCU still does not show the 3.00 in the flightplan. The DIRECT TO function is still buggy. It still creates an arc path to the waypoint even when the plane is pointed directly at it (see screenshot). Link to comment Share on other sites More sharing options...
Deleted Account Posted February 29 Share Posted February 29 Will look into the 3.00 missing in the flightplan, however I can't reproduce the DCT TO issue, you have any steps for me to reproduce it? Link to comment Share on other sites More sharing options...
Joel S Posted February 29 Author Share Posted February 29 I've tried so far with some waypoints leading to RNAV approaches for KJFK. I just hit DIR, select the waypoint, select *INSERT and I get what you see in the screenshot above. That example is the RNAV Z 31L approach. I use FSIPANEL 2020 to quickly place the A300 into position at RISSY. I then set a Direct To I never had an issue setting a Direct To ZACHS and you can see how the flightpath is drawn. The plane is facing ZACHS and should be a straight line. Instead there's a curve arc followed by a straight line. Link to comment Share on other sites More sharing options...
Joel S Posted March 3 Author Share Posted March 3 I did more testing and I believe the DIRECT TO issue I'm having is related to FSIPANEL 2020. I'll contact the owner,JP, and inquire. So the only issue (if you want to call it that) is to have "3.00" appear on the FAF of RNAV approaches. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now