Today I took the 737-600 on a flight of 1,5 hours up to ENBO. Everything working perfectly. I then turned around and headed back to ENGM. So far so good.

 

Descending on VNAV into Oslo I immediately noticed the N1 stuck at 67,4 %. The aircraft was following the VNAV path correctly but speed was too high for the CI 15 I had set.

 

Basically the throttle would not retard but stayed at a high N1 % during descent.

 

When I disconnected the A/T, the N1 went thru the firewall, so to speak. Tried to control the N1 by setting it manually from the MIP, but no success. Also the CDU N1 limit page did not work.

 

I have mostly been flying the 800- and 700- with no such issue what so ever. Funny thing is that I remember also getting the same problem on an earlier flight with the -600.

 

Win 7 64, FSX installed in c:, NGX properly installed and plenty hrs in the NGX. And, like I said, the only time the issue pops up is in the -600.

 

Has anyone seen this problem before, or have a clue about what is going on? I am baffled.

 

Thanks.

What was the position of your hardware throttles that whole time?

What was the position of your hardware throttles that whole time?

 

Hi Kyle, they were in idle. Just a Logitech joystick with a single throttle.

It's probably just because you flew up to Bodø, then. Nothing but crazies up there, and the plane got infected. Who else would live in such cold, sunless, wintery desolation?

(Part of my family is from around there, so I'm not actually trying to be mean)

 

In all seriousness, it sounds like you've tried everything else. Just to be doubly sure, I would try to disconnect the hardware throttle the next time it happens. If that doesn't fix it, run the installer (you don't need to uninstall it first). When you run it, there should be an option for repair mode. Try that first. Then, if nothing else works, you might try uninstalling and reinstalling (make sure you do so as an administrator).

It's probably just because you flew up to Bodø, then. Nothing but crazies up there, and the plane got infected

 

Haha.. that could be it!

 

I have very few flights in the 736 compared to the 738. Yet, the only time I get issues like is in the 736. Therefore, my feeling (not hard science) tells me it's not the hardware but "something" about the 736. Also, no problems with the 737 even if that is the same expansion pack... very mysterious, me thinks.

 

Will try the installer if I stumble across the problem again. Now, it's time to fly the -700

 

Thanks!

It happens to me exactly the same thing.

 

Silvino Rodrigues

It happens to me exactly the same thing.

 

Silvino Rodrigues

 

Hi Silvino. For lack of a better word, that's "good" to hear. Have you tried to do any troubleshooting on it?

I sent a ticket to PMDG to report the problem but got no solution.

I also have win7 64 and a simple joystick.

The solution I got was to start FSX after each flight.

 

Silvino Rodrigues

I flew the 736 from IAD to TXKF and back, and then around IAD/DCA/BWI for a few approaches before getting back to IAD before my sim rig died. Never had an issue. Definitely worth sending a ticket, though, if you can't resolve it.

The solution I got was to start FSX after each flight.

 

Yeah, it seems it always works fine on the first flight. Need more testing to confirm that though. Also it's not consistent, just like Kyle is reporting no problems with multiple sectors.

 

Looks like I might have to send a ticket as well..

 

Hope that other people that might have the same problem chime in. That way we might see if there is a pattern to this.

Do you us FSUIPC? I have had the same issue and tracked it to FsUIPC. After changing the throttle through to FSX I have not had issues.

 

 

Do you us FSUIPC? I have had the same issue and tracked it to FsUIPC. After changing the throttle through to FSX I have not had issues.

 

Hi Paul! Yeah, I have FSUIPC (full/paid version). I don't use it for the flight controls though. Did you have this problem with the -600 only, or the other NGXes as well?

I saw this the last few times I flew the -600. During VNAV descent the engines just would not spool down to idle, but stayed at a high N1 and thus the aircraft deviated from the vertical path and it became....difficult....to get the aircraft in a low enough energy state to perform the approach.

 

Switching to V/S would get the engines to cut down to idle, but something about VNAV wouldnt do it.

Switching to V/S would get the engines to cut down to idle, but something about VNAV wouldnt do it.

 

Interesting, I will test V/S next time around the problem shows up. However, I should mention I tried autopilot disengage, A/T disengage, and recycling FD... well, pretty much anything except pulling the fuel shutoff. ^_^

Weird.. I fly the 600 a lot, as it's my converted private BBJ so to speak..

Never have seen that problem with mine. Neither the 600 or 700.