November 10, 20232 yr Author N1 as in applying max amount of available thrust related to what you set in the N1 Limit page on the FMC before takeoff.
November 11, 20232 yr 36 minutes ago, Carterflyz said: N1 as in applying max amount of available thrust related to what you set in the N1 Limit page on the FMC before takeoff. I see. Sounds like the issue is that the autothrottle is providing max thrust. Is it a temporary thing (meaning it lowers the thrust back down) or does it apply max thrust and maintains it?
November 11, 20232 yr Author It holds the power and completely deviates from the speed bug, also over speeds.
November 11, 20232 yr Sounds like it somehow commenced a go around? Maybe a keybinding issue here? Intel i9-13900K | Gigabyte Z790 Aorus Master | RTX4090 | 2x16GB Corsair Vengeance DDR5-6000 | Be quiet! Pure Loop 2 FX AiO | Win 11
November 11, 20232 yr Author checked that... also looked at some footage and found that aproximity a second after I commanded my FO flaps 25, (Im using FS2crew) the FMA displayed MCP ALT. This was after I had set the missed approached altitude.
November 11, 20232 yr 4 hours ago, Carterflyz said: Previous Page Next Page checked that... also looked at some footage and found that aproximity a second after I commanded my FO flaps 25, (Im using FS2crew) the FMA displayed MCP ALT. This was after I had set the missed approached altitude. Previous Page Next Page Got it. I recommend watching 737NG Drivers VNAV/LNAV tutorial. He explaines how to work the MCP during the approach to keep the AP from capturing the altitude when reaching minimums. Sounds like thats whats happening to you. Intel i9-13900K | Gigabyte Z790 Aorus Master | RTX4090 | 2x16GB Corsair Vengeance DDR5-6000 | Be quiet! Pure Loop 2 FX AiO | Win 11
Archived
This topic is now archived and is closed to further replies.