I recently reinstalled Windows 7 and FSX, and the PMDG 737 base and expansion packs and a bunch of other addon aircraft, then I restored my backed up aircraft folder and let it overwrite the files since the backup had the updated files for my aircraft than the original files. Before doing all this, the 737 would start it's engines automatically. Now the engines won't start and Ctrl E does not work. I read the tutorial and it mentioned nothing on how to start the engines. Did something screw up the original 737 NGX installation when I was restoring the FSX aircraft folder from my backup and letting it overwrite files? The reason why I restored from my backup is because I have liveries installed and updated aircraft.cfg files to correspond to the liveries to make restoring my aircraft easier. Doing it this way saved me time from re-editing aircraft.cfg files since I had modified views and additional liveries installed for my aircraft. What I basically did was restore my backup over the original installation and letting my restored backup overwrite files.

Ok, I uninstall the 737 NGX base pack and expansion pack, deleted the folders, reinstalled the 737 NGX base pack and expansion pack, ran the livery manager to install other liveries, but this time I did not restore the backup over the original installation. Still the engines won't start at startup. I get engine failure lit up in the instrument panel a few seconds after the initializatiion process.

Okay... Let me take a deep breath so I don't come across too mean, but REALLY? You drop $100 for the 737 and you're using Ctrl-E? Try and do the tutorial flight or RTFM!

OK....whew...Lets start off with a physical checklist...1) They're all over Avsim2) Most all nicely doneWith the engines, there is a page in the CDU called Panel Load, and you can get the engines to start after a countdown of 20 secondsI believe it is PMDG Options->Panel Load->NGX Short, or whatever is there.

Edited January 24, 201214 yr by Wendall

Amazing.* Orest

LOL, I sitting in the left seat of one of our 737-890's right now, and no matter how hard I look I just can't seem to find a keyboard, switch or button labeled 'Control E'.PMDG builds flight/system simulators. There is no Control E my friend.

Edited January 24, 201214 yr by 559AS

LOL, I sitting in the left seat of one of our 737-890's right now, and no matter how hard I look I just can't seem to find a keyboard, switch or button labeled 'Control E'.PMDG builds flight/system simulators. There is no Control E my friend.

Common misconception about CTRL + E. In the early 1990's Boeing modified the common "Quick Start" method of using CTRL + E (or Space then E on the FMC) at the request of PAN AM to reduce the risk to ground crew and maintenance guys on the ramp caused by accidental "Quick Starts". I believe, as of 1994, the current "Quick Start" procedure is to push the thrust levers all the way forward while raising the gear lever to the Up position and toggling the seat belt chime 4 times in a row. Once you've done this the purser or any qualified FA must flush the FORWARD lavatory toilet twice. This will get the pneumatic systems going and your engines will start.I'm pretty sure that's what the manual said. :(

Edited January 24, 201214 yr by WestAir

I recently reinstalled Windows 7 and FSX, and the PMDG 737 base and expansion packs and a bunch of other addon aircraft, then I restored my backed up aircraft folder and let it overwrite the files since the backup had the updated files for my aircraft than the original files. Before doing all this, the 737 would start it's engines automatically. Now the engines won't start and Ctrl E does not work. I read the tutorial and it mentioned nothing on how to start the engines. Did something screw up the original 737 NGX installation when I was restoring the FSX aircraft folder from my backup and letting it overwrite files? The reason why I restored from my backup is because I have liveries installed and updated aircraft.cfg files to correspond to the liveries to make restoring my aircraft easier. Doing it this way saved me time from re-editing aircraft.cfg files since I had modified views and additional liveries installed for my aircraft. What I basically did was restore my backup over the original installation and letting my restored backup overwrite files.

forget your installationyou can't start the engines because you have no clue the depth of simulation you actually purchased

I'll spare you the sarcasm, I believe you had your share already.Try the tutorial step by step and if that doesn't work, let us know.Bert Van Bulck

Okay I read the tutorial and pretty much did what it said except I didn't add a flight plan to the FMC or set N1 limits, and flap settings, and a few other things as I'm not going load a flight plan. I also tried different panel states and all of them had engines failure at start. However I tried the 737-800wl and my engines started automatcally and engine responded to the throttles. It was a Westjet 737-700wl and a Westjet 737-600 that I had the problems with the engines. Also I want to add that the FO side of the cockpit, the engines info screen stays off but it stays on on the 737-800wl. I didn't have these issues before reinstalling Windows.

forget your installationyou can't start the engines because you have no clue the depth of simulation you actually purchased

I don't know about that, this problem didn't happen in my previous Windows 7 installation. Also for the 737-800wl, engines started up without failure. I'm not a pilot and FSX is the closest I'll ever get to flying a 737.

SpeedPilot,The info screen on the FO panel is off because it's not being powered by a power source (APU, Engine Generator, or Ground Power). On your 7378WL it's on because (I am assuming) the engines or the APU are running, as per panel startup config.Try this:1.) Load the 737-700 WL2.) On the overhead panel near the light switches, start the Auxillary Power Units (APU) by flipping the switch to start. (The button should be on the Captains side of the overhead, right above the front window).3.) Wait about 60 seconds then go slightly above that on the overhead to the part of the panel that reads "BUS TRANS" you should also see APU GEN APU right below it. Flick both switches to 'ON' - you should see the FO panels activate.4.) Look around the cockpit for any switches that have a yellow-orange annunciation. Turn them all to the on position to extinguish said lights. (IMPORTANT: Make sure the ENG 1 and ELEC 2 switches on the HYD PUMPS panel are on, along with the fuel pumps)5.) On the far right middle of the Overhead panel, turn the APU Bleed switch to "ON" and the Isolation Valve switch to "AUTO". Turn the R PACK and the bleed switch below it to "AUTO" and "ON" respectively. IMPORTANT: Leave the L PACK and it's bleed switch off.6.) Next to the APU start switch from direction # 1, turn the Engine Start Switch to "GRD" and flick the switch that says "BOTH IGN L" or "IGN B" to "IGN B". That switch should be to the right of the APU Start switch.7.) Flip the #2 / RIGHT Fuel Cut-Off lever below the throttle to "ON"--Your Right Engine should start.8.) Go back to direction #5. Do everything the same, but for the L PACK and Left Engine switches respectfully.--Your Engines should now be started--There's probably a lot more to it then that, but if you just want the engines running and don't care about pneumatics, electrical settings, etc etc, just do the above.

SpeedPilot,The info screen on the FO panel is off because it's not being powered by a power source (APU, Engine Generator, or Ground Power). On your 7378WL it's on because (I am assuming) the engines or the APU are running, as per panel startup config.Try this:1.) Load the 737-700 WL2.) On the overhead panel near the light switches, start the Auxillary Power Units (APU) by flipping the switch to start. (The button should be on the Captains side of the overhead, right above the front window).3.) Wait about 60 seconds then go slightly above that on the overhead to the part of the panel that reads "BUS TRANS" you should also see APU GEN APU right below it. Flick both switches to 'ON' - you should see the FO panels activate.4.) Look around the cockpit for any switches that have a yellow-orange annunciation. Turn them all to the on position to extinguish said lights. (IMPORTANT: Make sure the ENG 1 and ELEC 2 switches on the HYD PUMPS panel are on, along with the fuel pumps)5.) On the far right middle of the Overhead panel, turn the APU Bleed switch to "ON" and the Isolation Valve switch to "AUTO". Turn the R PACK and the bleed switch below it to "AUTO" and "ON" respectively. IMPORTANT: Leave the L PACK and it's bleed switch off.6.) Next to the APU start switch from direction # 1, turn the Engine Start Switch to "GRD" and flick the switch that says "BOTH IGN L" or "IGN B" to "IGN B". That switch should be to the right of the APU Start switch.7.) Flip the #2 / RIGHT Fuel Cut-Off lever below the throttle to "ON"--Your Right Engine should start.8.) Go back to direction #5. Do everything the same, but for the L PACK and Left Engine switches respectfully.--Your Engines should now be started--There's probably a lot more to it then that, but if you just want the engines running and don't care about pneumatics, electrical settings, etc etc, just do the above.

Thanks for your help. I'll try that. Strange that I didn't have to do all that in my previous FSX/PMDG 737NGX installation.

Make sure you let N2 motor up to 25% BEFORE you introduce fuel.

Thanks for your help. I'll try that. Strange that I didn't have to do all that in my previous FSX/PMDG 737NGX installation.

Okay now this time the 737-600 engines started up without failure. All I did was restart FSX and load the same flight again after trying it with the 737-800wl for the first time that didn't exhibit these problems. Weird. Maybe something about loading and activating the 737-800/900 base pack was required to get the 737-600/700 extenson pack to work properly even though I did activate the extension pack prior to activating the base pack?