I don't think I said it was, but fine: restriction or prediction. There's a whole bunch of problems going on here, but deceleration with N1 of 37% sounds like a problem to me. The 1519ft above is a symptom, so to speak.

Sorry Matt, I thought you meant it was a restriction. It was the way I read your comment about EH607 wanting that speed. Yes, 1519 ft high is a symptom of the cause, what I meant was it's the main problem as shown by the picture. 37% N1 might be the cause, but in VNAV PATH the aircraft would just descend faster. However the pictures don't show VNAV in use.Kevin Hall

"restriction or prediction." Big difference.You are right, there are a bunch of problems but N1 idle at 37% isn't one of them, as that is a pretty normal descent idle and one I often see.

Agreed: There is a difference between restrictions and predictions. On a STAR of SID, there is a huge difference. On an RNP, it could mean life or death.37% idle N1 on approach may be common, but it isn't normal. I was at 29.7% F5 joining the LOC at KSEA last time. I actually looked just to see what it should be. It isn't 37%. Common =/= Normal.

Sorry Matt, I thought you meant it was a restriction. It was the way I read your comment about EH607 wanting that speed. Yes, 1519 ft high is a symptom of the cause, what I meant was it's the main problem as shown by the picture. 37% N1 might be the cause, but in VNAV PATH the aircraft would just descend faster. However the pictures don't show VNAV in use.Kevin Hall

In two of the pics, they show VNAV SPD. I'm not sure if NGX simulates Common VNAV, but unless you're on the approach, VNAV PATH will revert to VNAV SPD when you get too high or too fast, such as the case here. Combine that with a false idle N1, and you're got problems.So, he is in VNAV, but in VNAV SPD and probably through reversion caused by the overspeed/high which was in turn caused by N1 being to high. (Colonel Mustard in the Kitchen with the Candlestick.)

In two of the pics, they show VNAV SPD. I'm not sure if NGX simulates Common VNAV, but unless you're on the approach, VNAV PATH will revert to VNAV SPD when you get too high or too fast, such as the case here. Combine that with a false idle N1, and you're got problems.So, he is in VNAV, but in VNAV SPD and probably through reversion caused by the overspeed/high which was in turn caused by N1 being to high. (Colonel Mustard in the Kitchen with the Candlestick.)

Doohh, I'm from the steam cockpit generation, forgot to look at the FMA. Would 37% N1 alone be enough to cause VNAV PATH to switch to VNAV SPEED? Maybe it would in a -800.It is indeed taxing on ze little grey cells.Kevin Hall

I'm writing down each one your advices. Tomorrow I'll do again, step to step under manual. Also I'll check if my physical hardware, may be here would I have some problem.So, if I arrive over arrival airport without flaps, gear dup, to high, to fast etc.. that is caused because jet does not comply with the predictions, may be it is my fault... could be.I'm sure I don't know to flying as well as you this jet, I'm beginning on this plane with.Please other question too, This afternoon I have flown from LEBL to LEPA, practically VNAV has been made manually by me. I've gotten to arrive at last point very fine, FL 4300 and speed 180knts fifteen milles before IF. CDU marks on the legs 220/4300 then I have attemted to change 220/ to 180/ and Exect, CDU recalculates without problems, so I pushed VNAV button again, well, aircraft starts to increase speed until 243Knts. Why does the plane do iEdit: Did you actually read Tabs post when he suggested you try the same thing in a -900? He was very politly telling you that you had a pebcak error.I didn't yet, I haven't go all time of the world, but I want to try it.Thanks again.

Please other question too, This afternoon I have flown from LEBL to LEPA, practically VNAV has been made manually by me. I've gotten to arrive at last point very fine, FL 4300 and speed 180knts fifteen milles before IF. CDU marks on the legs 220/4300 then I have attemted to change 220/ to 180/ and Exect, CDU recalculates without problems, so I pushed VNAV button again, well, aircraft starts to increase speed until 243Knts. Why does the plane do i

The CDU is telling you what the FMC calculates the speed will be at each waypoint, but if you don't extend flap then that schedule is not possible as the aircraft would be flying too slow and in danger of stalling. To get lower speed you must extend the flaps in stages. Each flap extension will reduce the minimum airspeed you can safely select (shown by the bug on the PFD). However, you certainly shouldn't be trying to control airspeed using the FMC CDU speed constraints. Just press speed intervention on the MCP and use the IAS control. You don't have to go through each flap detent position, I tend to use Flap 1 and 10 on the approach, 15 (and gear down) at glideslope capture and landing flap soon afterwards.Kevin Hall

If the flaps aren't extended down, neither gear, that's Jet is unable to reduce its speed. Can I extend flaps down when speed is over 240knt? For long time I'm using breakspeed during descent, but plane doesn't reduce its speed. I expect minimun speed to start down flaps but I have never gotten it.Thanks a lot.Gabriel.

If the flaps aren't extended down, neither gear, that's Jet is unable to reduce its speed. Can I extend flaps down when speed is over 240knt? For long time I'm using breakspeed during descent, but plane doesn't reduce its speed. I expect minimun speed to start down flaps but I have never gotten it.Thanks a lot.Gabriel.

In picture 3 the flight plan shows DECEL circles indicating it is soon to decelerate ready for flap/gear extension. In pictures 1 and 2 this has already happened but you haven't extended flap in response. In all three cases you are too high to make the approach. I suspect the NGX is going too fast to have time to slow down, leading you to be above the planned descent path. This comes back to your problem with excessive airspeed during descent. A few screenshots covering the whole descent might help give a clue. Perhaps one above 12000 ft, one below 10000 ft and one above 5000 ft. Also check whether the thrust levers in the VC are actually at the idle stop during descent. 37%N1 is a high value for idle in clean configuration.Kevin Hall

I'm writing down each one your advices. Tomorrow I'll do again, step to step under manual. Also I'll check if my physical hardware, may be here would I have some problem.So, if I arrive over arrival airport without flaps, gear dup, to high, to fast etc.. that is caused because jet does not comply with the predictions, may be it is my fault... could be.I'm sure I don't know to flying as well as you this jet, I'm beginning on this plane with.Please other question too, This afternoon I have flown from LEBL to LEPA, practically VNAV has been made manually by me. I've gotten to arrive at last point very fine, FL 4300 and speed 180knts fifteen milles before IF. CDU marks on the legs 220/4300 then I have attemted to change 220/ to 180/ and Exect, CDU recalculates without problems, so I pushed VNAV button again, well, aircraft starts to increase speed until 243Knts. Why does the plane do iEdit: Did you actually read Tabs post when he suggested you try the same thing in a -900? He was very politly telling you that you had a pebcak error.I didn't yet, I haven't go all time of the world, but I want to try it.Thanks again.

Given the dialogue and the screenshots I believe these posts could be helpful:http://forum.avsim.n...uring-approach/http://forum.avsim.n...edbrakes-video/http://forum.avsim.n...page__hl__video ***http://forum.avsim.n..._1#entry2176294

After differents checkings I decided to install back FSX since 0, namely, deleting all folders, files, libraries...etc.I installed FXS, FXS Acceleration (FSX_SP2) and PMDG, namely without others adds, for exemple, FSPassenger, Saitek, IVAO, and no others extra aricrafts.Result has been too much, any problem more. I did more flights to certify it what problems were gone. Fortunately I can confirm this.So, I have installed drivers for Saitek. Once the drivers are installed, problem starts again.I don't have any problem with IVAO, the 737-800 runs very good, but with FSPassenger its behavior is strange to.Until this point I'm satisfied, I know now the game works fine, another thing is if the game can play joined to others addons.In conclusion, I deduce that there are some incompatibilities between PMDG and other games added.What do you think?In any case, thanks everyone.Without your help I would not have achieved and learned something new.Gabriel