Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Engine start strangenss

Featured Replies

Okay, so starting cold and dark. I go through all procedures to start the engines. When I get 20 N2 I give the fuel... Display shows engine powering up, although the sound is not there and when moving the throttle I get my alarm, the engines do not react and the egt, n1, and n2 gauges freeze. Only when I press cntrl-e do the sounds begin as if the engines begin spooling up and finally the throttles become responsive.??? Any thoughts... I do know I have the highmem issue where my external model disappears. But I don't know how this could be related?I also had an issue with vnav not working on the first flight, but selectable in the second flight. I checked my fmc vertical info, but didn't see anything different between the two scenarios.Oh, and the engine sounds are GREAT!!! especially at TOD and start up.

  • 1 month later...

I know this is a month and a half old, but i just experienced the exact same thing. First problem I ever had with the NGX. I'll start over the flight again and see if anything changes. I was getting normal engine readings (N2, N1, oil pressure, though no vibration indication), I was getting no duct pressure from engine bleed air, the engine generators were online, and I was getting an "Overhead" warning light on the glareshield.

Cristi Neagu

Introduce fuel at 25% N2. At 25% the main fan is just ticking over so vibrations will be zero. See if that works for you?

Mike Summers

I introduced fuel at somewhere around 22% N2. The vibrations were 0 at 60% N2, after starter cutoff and engine idle reached.

Cristi Neagu

I've had this problem for a long time now, and it seems to survive through all hotfixes.

Johan Nordqvist

Sorry post wrong way.

Jia-Hsing Fu

 

ACH0978.jpg

How are you loading the NGX? Are you loading it straight from the startup quick flight menu or are you loading up something else before hand. The recommended method is selecting the NGX directly from the quick flight set-up. If you've been flying something else prior to the NGX it may be wonkying-around with things....in this case it's like the PMDG code knows the engines are running, but the FSX code thinks there still off...hidden condition levers or something like that from a previous flight.

Patrick Houghton

Sig.jpg

How are you loading the NGX? Are you loading it straight from the startup quick flight menu or are you loading up something else before hand.
I always load it from the quick flight menu, as I did for that particular flight. I couldn't replicate it, and now I have hotfix 4 installed. If the problem occurs again, I'll do some more tests and try to pinpoint it. Thanks.

Cristi Neagu

20% is too soon, it should be 25% when you open the fuel. There's a little leeway there, but also if you let it run too long past 25% without opening the fuel cutoff, it will only "semi" start and not respond to the throttles (and you've pretty much broken the starter). Also make sure both L and R packs are off before starting. After they've started and the overhead ignition switches have both turned to off, that's when you turn the packs back on.

Gabe Keewaydin
 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.