Changing default aircraft from Cessna to Boeing 737 and saving as default flight solved engines V1 cut-off for me definitely.Try it.Regards,Vitaly

Can some of you other guys please explain to me your takeoff procedure? I see some with no A/T armed I see some with NO V2 set in the MCP! And I wonder if any of you are also arming the speed brakes on TO (not that this one matters but it is wrong)? Fast run down here fellas, please unless you are SWA you arm the A/T and no matter who you are you ALWAYS set V2 on the MCP speed window! At least we can eliminate these other issues AND the most important question would be HOW DO YOU KNOW WHEN TO ROTATE WITHOUT VSPEEDS SPEEDS? Certainly this can explaine at least a FEW of you with this issue (But not others)....[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/forum/betaimg.jpgAMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | WD SATA 80 GIG | 512 DDR 400 |

Just wondereed what weights and fuel and model you were using as I have just tried about every mixture I can think of and it doesnt happen. Crash detection IS turned on btw.Have the filures in the PMDG menu been cleared? Have you ever used them? Perhaps it happens after they are used and cannot be cleared.I guess more info is needed. Would be nice if everyone could duplicate the fault then we could help PMDG by at least giving them the basic problem.Kind regardsNigel Thomas-Smithhttp://www.precisionmanuals.com/images/forum/800driver.jpg

Hi,I have the engine failure during take off. This happened afterflying severalls flights with 737800 without a problem.I use the flight tutorial from Fred clausen. So I think I'll do less wrong. I use the FMC and I can see the V1,V2, bugs on my PFD.After reaching V1 i hear "engine failure" the engine stops, the aircrafts rolls out. There is no way to start the engine again.Even doing a cold and dark start. The only way to start up the engineagain is to reload the aircraft. But the engine-failure calls still persist when I reached V1. Use Fs2004, GAP4, FSMeteo 6.4, RC V3.1, FDC 1.5, FS Flightkeeper 2.0winXP pro. P4 3,06; TI 4600; AAx2, AFx2, 1 GB-RAM, swap-file system managed (before it was fixed to 1,5 GB; changed that after having CTD flying to VOR TRA -near LSZH, Switzerland, Europe)Constantin L.

Hi,I don't know if you can use this info:I can reproduce the engine failure:I have a saved flight with the 737-800. When I load the flight and take off everyting is ok. If I load the flight and then I change the livery (still same type of aircraft: here 737-800) I have the engine failure problem during take off. This happens changing from SAS-Snowflake to SAS-Scandinanvian.Hope this helps to solve the problem.GreetingsConstantin

I think this has been said many times beforeComplex add-ons have never really been good to have as default flights. This has been true for as long as I have can remember. ANd for many add-ons as wellUse a saved flight as with a default plane and any other settings of your choice. Then change to the NG of your choice and press "Fly now"This way you will minimize the risk of having the engine failure on the take-off run or any other peculiarities for that matter.Hope it helps,

Hi,yes I know. But I never had a problem with the 737-600 and -700 before. After landing and parking I love to change the aircraft and still go for are new "challenge" without reboot Fs9 or reload a new flight. It would be nice If the team of PMDG could fix the problem. GreetingsConstantin

It may be there is a small sim error somewhere but I have had no problems whatsoever in this sim with engine failures or anything else. Can only suggest that everyone make sure they are flying the Boeing in strict accordance with the Flight Manual - all switches and preflight setup correct. Anything else is not good enough and may well cause errors/failures.Brad Marshhttp://homepage.powerup.com.au/~speedy/pic...Hawaii_Crew.jpg

I too have V1 engine failure with the -900 series. I deleted the takeoff speeds from the FMC and the problem did not happen again. My feeling on it is there is a bug with the reference marker at "V1" which triggers engine failures.Andy Clapp

I have been having the same engine failures right after I updated to the -800/900 models. I tried most of the fixes here to no avail. The only way I was able to fix the engine failure problems was to completely uninstall the PMDG aircraft, including all folders, then re-boot and do a fresh install of the -600/700, update to ver 1.3, then the -800/900 update. I have flown approximately 20+ flights in all four models using different saves and loads with out one single engine failure. If any of you are still plagued with this problem you might want to give this a try. Worked for me!LyleATL Hub ChiefSunAir Express VAwww.sunairexpress.com

>Alan>>TRY THIS:>- Save a default flight with a default plane at an airport of>your choice. (preferably in your time zone, this way the FS>clock will show right time according to your system time when>you change aiports). >- The above only needs to be done once>- When getting the start up dialog. Select a PMDG craft.>Select any other settings of your choice. Press Fly now.>>Hope it helpsThanks Mats but I did a default after I first installed the 800/900 series. I'm not using any of my previous flights or plans. It's now getting more serious. I've tried different locations and places where I have no addon scenery installed. I don't start FS with the PMDG as the default aircraft.Now after a short while in a flight the screen goes black and after a while I get the dreaded MS problem window. This only happens with the PMDG plane. Considering that a lot of the 'donkey work' and time is done on the ground this is getting very dissapointing.I have a good system which handles FS really well apart from this.P4 3.2GhzRadeon 9800Pro1Ghz matched Corsair XMS3200 duel ram120Gb HD

Hello,proud to advise that never - so far & I AM TOUCHING WOOD - had an engine problem/failure on the 736,737,738 and 739 since "TSN"...Always start the FS9 (since recently) and when the selection window for location & aircraft comes up, i select my "73x", airport I'd like to depart from and time settings. Then it's the "FLY NOW" button and off we go..OK, this gives me "everything running" on the panel and plane, but am normally starting APU or take GND-PWR for some "juice" and then complete the shut-down procedure to have engines off.After that is pre-flight work and then start-up and push-back "down the book"... works fine - never a problem.Love the 73X plane, BUT MORE IMPORTANT - AWAITING PATIENTLY THE B747-400 - hopefully a -400F version... please please please ;-)Cheers,Norbert - CLX001www.virtualcargolux.org

Hi again,eventually I managed to do 2 flights now without probs. Did the following: 1. created a new startup situation with MS B737 (NOT with MS Cessna, that did not work for me!!!) 2. started engines and cut them off immediatly therafter. 3. Then I saved it as a new startup situation. 4. Restarted FS9 and loaded the new situation5. changed to PMDG B738. This really seems to work so far but probably some more testing will be required.Best regardsUlli

Hello,can anyone who has NO problem with the engine failure be so kind and try to do this:load your saved flight as usual and be on the runway cleared for take off...don't take off....NOW you should change your livery-NOT your type of aircraft- awake your aircraft to life again, load your fmc and after all your preflight checks pls. take off...engine failure at V1? :(Thanks a lot!Constantin

>Hello,>>can anyone who has NO problem with the engine failure be so>kind and try to do this:>>load your saved flight as usual and be on the runway cleared>for take off...don't take off....NOW you should change your>livery-NOT your type of aircraft- awake your aircraft to life>again, load your fmc and after all your preflight checks pls.>take off...engine failure at V1? :(>>Thanks a lot!>>ConstantinYou got a point there Constantin. Never had V1 failures before, and always started from previous saved flight (never used default cessna procedure and no problems at all). Tried your suggestion and BINGO, left engine quit at V1. Restarted (after unchecking the failures on fscof), tried again and failed again. Restarted left engine and on 3rd attempt, BOTH engines quit at V1. :-eekPMDG, try to duplicate the above mentioned, you guys may find out what the problem is. Regards,