I'm new to the program, and I really like it. Having flown the 737NG for a while, I do have some insight, however.While coming in for an approach, I really like to keep an eye on the V/B and I use the VSR to gauge my descents if I'm not in VNAV. That said, the sim really doesn't seem to be very accurate with these tools. The VSR seems to be all over the place and V/B seems to be way off with a simple 3-1 mental math check. Anyone else have that problem?Oh, and I'd really like to be able to put the runway on the descent page, rather than simply the next fix.Thanks,Matt Colles

I am not familiar with the acronyms V/B and VSR, thanks.

I'm new to the program, and I really like it. Having flown the 737NG for a while, I do have some insight, however.While coming in for an approach, I really like to keep an eye on the V/B and I use the VSR to gauge my descents if I'm not in VNAV. That said, the sim really doesn't seem to be very accurate with these tools. The VSR seems to be all over the place and V/B seems to be way off with a simple 3-1 mental math check. Anyone else have that problem?Oh, and I'd really like to be able to put the runway on the descent page, rather than simply the next fix.Thanks,Matt Colles

???

On the Descent page in the FMC there is data for the Vertical Bearing to the selected waypoint and a Vertical Speed Required to make that waypoint at the desired altitude. Very handy dandy.

Part of the reason I am lost is because I prefer 737 descents with manual control of MCP SPD and V/S, and use the green arc for reference. However, I am looking at a copy of the FMC SPD DES page in the manual and se TGT SPD and WPT/ALT but no such thing as vertical bearing. There are a couple of 737 experts that check into the forum often that are sure to respond.Winds in MSFS are always a problem in trying to achieve the desired descent path, so I assume speed descents have the same problem.

Hi Matt,I believe you are referring to the VNAV indicator visible on the ND. You can also see it in the FMC descent page, correct. Personally, I think the VNAV logic, if planned correctly, is quite accurate on the NG. However, as Dan mentioned, because of FS wind direction changes it might go off course which then requires V/S intervention.I frequently use VNAV for descents down to 10000 feet and even lower (rarely though). Most of the time it works well.I don't think it's possible to insert a runway as a waypoint in the FMC, you can only insert one in the RTE page or select one in the arrivals, I may be wrong though. Why not create a custom waypoint very near to the runway?Regards

Hi Matt,I believe you are referring to the VNAV indicator visible on the ND. You can also see it in the FMC descent page, correct. Personally, I think the VNAV logic, if planned correctly, is quite accurate on the NG. However, as Dan mentioned, because of FS wind direction changes it might go off course which then requires V/S intervention.I frequently use VNAV for descents down to 10000 feet and even lower (rarely though). Most of the time it works well.I don't think it's possible to insert a runway as a waypoint in the FMC, you can only insert one in the RTE page or select one in the arrivals, I may be wrong though. Why not create a custom waypoint very near to the runway?Regards

In the real world plane with U10.7, if you "grab" the runway from the legs page and put a "/" after it and then put it in the Descent page, the descent page will give info to that point. I haven't found a way to modify the fix in the descent page in the sim yet.The VDI (Vertical Deviation Indicator) on the ND is based on the same info, but it won't give you raw data, obviously. Maybe I'll upload a screen grab and we can dissect the math and see if it works.

Part of the reason I am lost is because I prefer 737 descents with manual control of MCP SPD and V/S, and use the green arc for reference. However, I am looking at a copy of the FMC SPD DES page in the manual and se TGT SPD and WPT/ALT but no such thing as vertical bearing. There are a couple of 737 experts that check into the forum often that are sure to respond.Winds in MSFS are always a problem in trying to achieve the desired descent path, so I assume speed descents have the same problem.

The "Green Banana" arc is useful, but it's based on the MCP alt, I believe. If you have a clearance to one altitude for a certain fix, but want to base your V/S off of another fix, the Green Banana doesn't help.

The FMS/CDU software dates from FS2002; and although it has been updated that was some time ago. They are working on a new FS9/FSX 737 with much better fidelity.Yeah, the green banana is only good to either the next fix or the MCP ALT, which isn't a problem for me using MCP SPD and V/S with the desired "green banana" target dialed into the MCP ALT. Onur is one of our resident experts, glad he was able to respond. I defer to him on most 737 issues, but I don't like the VNAV for descent at all... I only use for for climbs.

I don't understand the question about the runway not showing up as a waypoint. If it has been selected on the ARR/DEP page it will show up as a waypoint on the LEGS page along with the missed approach and approach waypoints if you select an ILS or LLZ. Preflight I always select the anticipated one but reassign it if ATC changes it. Now when you decrease the range of the ND to either 10 or 5 nm, don't recall, you'll see the double bar signature of the runway. If you select a LOC or ILS from the arrival runway list on the right side of the of the ARR screen after you LSK the ARR line, you'll get the approach altitudes and waypoints from the FMC database that you can use as a guide to select V/S.

The FMS/CDU software dates from FS2002; and although it has been updated that was some time ago. They are working on a new FS9/FSX 737 with much better fidelity.Yeah, the green banana is only good to either the next fix or the MCP ALT, which isn't a problem for me using MCP SPD and V/S with the desired "green banana" target dialed into the MCP ALT. Onur is one of our resident experts, glad he was able to respond. I defer to him on most 737 issues, but I don't like the VNAV for descent at all... I only use for for climbs.

If I remember correctly from testing, the r/w 737 pilots on the team related that VNAV was rarely used below 18K and almost never used below 10K. I think they also relayed that much of the time VNAV was not used for descents because ATC would typically be giving "descend to x alt" instructions based on traffic, wx, etc. Below 18K ATC decent instructions were also not usually way point based. I have similar experiences flying smaller GA aircraft as well.

If I remember correctly from testing, the r/w 737 pilots on the team related that VNAV was rarely used below 18K and almost never used below 10K. I think they also relayed that much of the time VNAV was not used for descents because ATC would typically be giving "descend to x alt" instructions based on traffic, wx, etc. Below 18K ATC decent instructions were also not usually way point based. I have similar experiences flying smaller GA aircraft as well.

Unless I'm on a STAR or doing RNAV/RNP approaches, I typically would use VNAV down to 10k and then LVL Change or - preferably to me - V/S.

I don't understand the question about the runway not showing up as a waypoint. If it has been selected on the ARR/DEP page it will show up as a waypoint on the LEGS page along with the missed approach and approach waypoints if you select an ILS or LLZ. Preflight I always select the anticipated one but reassign it if ATC changes it. Now when you decrease the range of the ND to either 10 or 5 nm, don't recall, you'll see the double bar signature of the runway. If you select a LOC or ILS from the arrival runway list on the right side of the of the ARR screen after you LSK the ARR line, you'll get the approach altitudes and waypoints from the FMC database that you can use as a guide to select V/S.

You're right that it'll show up that way, but to get the Vertical Bearing to the runway and a Vertical Speed Req'd, you need to take the runway from the LEGS page and insert it into the DESC page. That way, no matter what fix you're going to , you have a V/B to the runway.This isn't really a VNAV issue, as you're not in VNAV mode. It's more of a descent planning issue.

I don't doubt the validity of your point but I am wondering, are you 737 type rated? If so, great. It will be good to have one more visitor with line experience. There are several that pop in from time to time, not including the pmdg personnel.

I don't doubt the validity of your point but I am wondering, are you 737 type rated? If so, great. It will be good to have one more visitor with line experience. There are several that pop in from time to time, not including the pmdg personnel.

Yes. I've flown -4, -7, -8, -9s. It's kind of interesting having flown the plane and then going to FS2004. I've noticed a few things that are a little different from the aluminum version, but it's very good overall.Thanks everyone for the responses. I'm impressed to see so many responses in a short time.

It's certainly good to have another NG-rated member here. I think there was a couple of others but they don't chime in very often as Dan said.I hope Jose Luis (basa) shares his opinion with us, too, he knows a great deal on the NG FMC.I agree with VNAV not being using much in real life but since FS ATC is quite limited, I like to use VNAV down to 10000 feet then go to V/S as I find the LVL CHG to be not very practical unless I have a large margin.To add to what has been said above, from what I see on WAR DVDs, V/S is used most of the time, sometimes even on climb.EDIT: I've never done this before but I suspect it might work to some extent. Create a custom waypoint just 3NM out from the threshold on the same course with an altitude constraint of 1000 feet (no constraints for the other waypoints) and see if the VDI does the job...?