August 6, 201114 yr I've only down 3 flights so far and it seems to me that it is quite difficult to get the aircraft to slow below 200kts. On one flight I was unable to get my get my engines below 40.2%. I took off auto throttle and autopilot and the engines would not go below 40.2%. The next flight the engines dropped to about 32%ish.... In order for me to slow down I seem to have to drop gear and flaps at their max speeds, 20nm out in order to get the a/c slowed down in time to land. Anyone else have this issue ? Thanks,Chad
August 6, 201114 yr Its how the real thing flies. Its very clean.....aerodynamically speaking. Try to plan your descent earlier so its not as steep. FAA: ATP-ME, 737 CA, enough time in the 757/767 to be dangerous 🤠 Matt Kubanda, 7950X3D, 64GB RAM, RTX 5090@4k, MSFS 2024
August 6, 201114 yr Its a slippery plane. You have to manage your energy to be able to land cleanly Johan Pettersen
August 6, 201114 yr At around 200kts, you can drop some flaps and it will help slow you down. As you slow, keep dropping flaps, but don't go below Flaps 15 until you drop the landing gear. Robert Yunque
August 6, 201114 yr I just did an approach into MMUN and found out the same, very fast speed at slow altitude, power on minimum.Anyone else know a fix for this? Teofilo Homsany
August 6, 201114 yr I spent a lot of time testing this and comparing it to the real planes performance. They got it pretty much perfect. The 737 really is difficult to slow, especially in a descent. At 200 knots on a 3 degree glide slope I usually have at least flaps 5. to stay on glideslope at 180 knots it often takes flaps 10. Oh and the 737 has different idle settings depending on the configuration. That is why you see different numbers from time to time. Tom Landry
August 6, 201114 yr This is a problem that real 737 drivers face. It's not a bug. You need to be about 10,000 feet about 35 miles from the field. 20 miles out, start slowing. If all else fails, drop the gear - it makes a great speedbrake. Matt Cee
August 6, 201114 yr are you all flying the plane by hand without ap ? never tried it before, maybe I should try it too ... P.L. TranAMD Ryzen 5800x; 32 GB Ram; EVGA GeForce RTX 3090 FTW3; Win10 64 Bit
August 6, 201114 yr During ILS when actual glideslope rises through 1/2 notch below (the indication descends), lower flaps from 10-15 to full, every aircraft. Regards, Opher Ben Peretz
August 6, 201114 yr This sounds like the same issue as I'm having, and it's NOT due to the aircraft fde being modelled correctly, but I think due to a hardware confliction with the NGX (see my post in the forum). When the engines are stuck above 40% N1, retard your physical throttles manually whist watching the NGX throttles. After a second they will make an uncommanded movement back up to 40% N1. i7 2600k @ 5.1Ghz, ASUS Sabertooth P67, 8GB Corsair Vengeance DDR3 1600Mhz, EVGA GTX 580 @ 950MHz, OCZ Vertex II 240GB, ASUS Xonar DG, Thermaltake Toughpower XT 875W PSU, Antec KÜHLER 620 W/C, Corsair 600T SE White My FS9 Screens - http://fs9screens.blogspot.com/ Callum Richardson
August 6, 201114 yr This sounds like the same issue as I'm having, and it's NOT due to the aircraft fde being modelled correctly, but I think due to a hardware confliction with the NGX (see my post in the forum). When the engines are stuck above 40% N1, retard your physical throttles manually whist watching the NGX throttles. After a second they will make an uncommanded movement back up to 40% N1. What do you think the minimum flight and approach N1 indications should be? On the plane (RW) the EEC is keeping the N2 schedule based on this logic: http://imageshack.us/photo/my-images/117/737ngidlecontrol8wx.jpg/ I'd guess that the sim is trying to do something approximating how the plane acts with FADEC and a better throttle sensing. Matt Cee
August 6, 201114 yr Try the -900, apparently it's less slippery and easier to slow down (I haven't tried it yet). Jay Vorkapic
August 6, 201114 yr i highly doubt not being able to slow the airplane down is a bug. I think its just operator error. FAA: ATP-ME, 737 CA, enough time in the 757/767 to be dangerous 🤠 Matt Kubanda, 7950X3D, 64GB RAM, RTX 5090@4k, MSFS 2024
August 6, 201114 yr I just did an approach into MMUN and found out the same, very fast speed at slow altitude, power on minimum.Anyone else know a fix for this? Yeah, practice and following correct descent/approach procedures. Shane Gavin
August 6, 201114 yr What do you think the minimum flight and approach N1 indications should be? On the plane (RW) the EEC is keeping the N2 schedule based on this logic: http://imageshack.us...control8wx.jpg/ I'd guess that the sim is trying to do something approximating how the plane acts with FADEC and a better throttle sensing. This has got nothing to do with the EEC. Of course the idle N1 is dependant on temp/alt/speed, but just to illustrate to you that it is actually an issue with hardware; with physical throttle connected, idle N1 is 35-40%. With no throttle connected it is 25-30%. There is a problem somewhere, not just a case of operator error as everyone is so ignorantly confident of. i7 2600k @ 5.1Ghz, ASUS Sabertooth P67, 8GB Corsair Vengeance DDR3 1600Mhz, EVGA GTX 580 @ 950MHz, OCZ Vertex II 240GB, ASUS Xonar DG, Thermaltake Toughpower XT 875W PSU, Antec KÜHLER 620 W/C, Corsair 600T SE White My FS9 Screens - http://fs9screens.blogspot.com/ Callum Richardson
Create an account or sign in to comment