When I am flying an RNAV approach, I hit Activate Approach and the computer will correctly fly me down to the final waypoint on the approach but then the plane levels out at that final waypoint’s altitude. It will continue to follow runway heading, but wont descend further down to close to runway level.
I have minimums set at decision height, but still the computer wont fly me down to that level.
Not sure if this is a glitch, or if I have something configured incorrectly in the FMS.
Are you pressing the approach key when you are on final? It should show GP (GlidePath), which is also known as Ground Pound, since it will fly you straight into the ground unless you eventually kill the autopilot and flare manually.
Yes. The approach activates and the plane intercepts and follows the glide slope down to the final approach waypoint (in this case 4200ft) the decision height is supposed to be 2900ft, so I set my minimums for 2900ft but the plane still won’t descend past 4200ft unless I take it off auto pilot.
“Activate Approach” in the flight plan is NOT the same as doing this, and happens earlier in the process. There is no such thing as a glide slope in an RNAV approach. The glide path is a simulated glide slope that uses something other than a ground radio beam (something like GPS or baro altimeter readings) to make your plane descend at a 3 degree angle to the runway. this is indicated when you see “GP” in the flight mode annunciator.
Oh ok, thank you for clarifying that! I didn’t know the APR button was different from the “activate approach button.” When I get home to the sim, i’ll try that out.
Also, yes I know there isn’t technically a glide slope in an RNAV approach like there is in a localizer approach, I was using the terms interchangeably.
There should be a visible bug that looks like a VNAV deviation indicator on the right hand tape. Once this shows up you should be able to arm APR. In absence of this (and I do find it to be a bit wonky in MSFS) I would arm it at the final approach fix.
As a rule of thumb, I set Approach mode on an autopilot after I have left the last enroute fix/waypoint on the descent, and am inbound to the first fix/waypoint on the approach, meaning where I have flight planned to join the approach. Many autopilot systems want you to be within 30 degrees or so with respect to the final approach course (or in the case of an RNAV approach the course of the approach segment that you are joining) to activate approach mode. All this means is that some autopilots will not allow any sharp turns between the enroute segment you are flying and the approach segment you are joining, so perhaps fight plan accordingly to make a smooth transition from enroute/descent to approach.
alright, I think I know the bug you’re talking about. So at what point do you generally activate the approach in the FMS? I usually do it as I’m about to hit the last waypoint in the descent, before I hit the first waypoint on the approach. Is that the proper timing?
For me, the question of when to arm APR (or LOC) modes on the autopilot has more to do with task loading than anything IRL. I find that when flying a Jet in MSFS, anything I can do sooner keeps me from getting task loaded later. This is a matter of personal piloting preference, however, things can move fast even in a VLJ like the HA420, and I may have other piloting tasks to tend to when the LOC or GS “comes alive” so I don’t want to take a chance on missing that. By arming the APR mode before the bugs come down, I am protecting myself from missing them should something else be happening the moment they do. A good practice but not the only to fly, so whatever works for one in the sim, go for it. However, later on if trying one’s hand at one of the airliners, it becomes a game of staying ahead of the airplane big time. Waiting to mode select might mean missing the approach, as things can happen fast. All good!
Yep, that’s what I was doing wrong. Followed what you said and it worked like a charm; took me right down to 2800ft, I disconnected the autopilot and landed it perfectly. One of my smoothest and best HA420 landings yet.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.
Yes
Which aircraft are you reporting an issue about? (Please also add the proper tag for it)
Hjet (no tag exists)
Brief description of the issue:
Only the left GTC is totally functional. It works as expected, including the knobs and buttons below it. The right GTC, OTOH, isn’t independently controllable. None of its knobs and buttons work and it always shows the same page as the left GTC. IOW, changing the page on the left GTC causes the same page to appear on the right GTC.
Detailed steps to reproduce the issue encountered:
Select a page on the left GTC and observe that the same page is selected on the right GTC.
Attempt to use the knobs and buttons below the right GTC and observe they do nothing.
Build Version # when you first started experiencing this issue:
1.34.16
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
I only hit VOR/LOC to intercept the localizer after ATC clears me for the final approach. I only activate APPR mode once established on the localizer.
Thing is, when intercepting the localizer the aircraft will deviate from an ATC commanded heading or otherwise lateral mode; this can impact the traffic situation around the airport, leading to dangers.
Alligning with the loc first before activating APPR will ensure that the aircraft decents through a clear glide path and wont hit any terrain it obstacles as it could risk when descending before being ligned up.
I do however use proATCx and Im unsure if default ATC gives a seperate final approach clearance.
This is by design when using one of the low fidelity liveries in order to optimize for performance. If you want them to be independent, then use one of the regular liveries. This is explained in the manual IIRC. Also, this forum is not for reporting bugs with the aircraft or getting support from the developer.
For anyone who wants to contribute on this issue, Click on the button below to use this template: