FS2004 - Random engine/system failure (unplanned)

[jhoopes2]

I wanted to see if anyone else has had this issue. I dont think its occurring with just one aircraft and is really getting on my nerves.

While flying, after about 30-50 minutes, the aircraft will randomly shut down entirely. I've sat at my desk, watched all the MFD's on the Moach 737 go blank, and the aircraft start to fall. Restarting the engines solves it...But comon, I dont want to have to babysit the plane every second.

Has anyone else experienced this type of issue? My failures are all turned off, no crashes, just cruising along, and bam!, no systems/engines. I've reinstalled the aircraft and am not sure if a file somewhere needs to be rebuilt or what.

Any ideas would be great. Thanks!

PS: if you use the Moach 737 ("The experience") I have several nice pains (Delta, Janet, Israel) all coming soon

[Dijon76]

Alternators not On ?

[tommchowat]

I don't know how complicated the addon is in terms of realism, but make sure on the ground after engine start that you put both of the generators online. If the APU isn't simulated then the aircraft will be running off DC electricity from the battery which only lasts 30 minutes. Although that doesn't explain the engines failing, so I'm stumped...

[jgf]

I've experienced this problem also, but so rarely I assumed it was a system hiccup. Most recently a couple of months ago when the default 747 had all four engines shut down while climbing through 18k ft just after takeoff. Perhaps a year ago my PAD Twin Otter had both engines stop while cruising at 5k ft. Only difference from the OP is I've never been able to restart the engines so just abort the flight; and the avionics continue functioning. Have noticed this has never happened in a single engine aircraft.

[jhoopes2]

I've found that this happens with other aircraft as well, sometimes during a climb and sometimes just on the taxiway. Never really had this issue before though.

[opaplano]

I've found that this happens with other aircraft as well, sometimes during a climb and sometimes just on the taxiway. Never really had this issue before though.

The only time I have seen this happen is when a user has changed the default flight to a "cold and dark" situation - with the battery and avionics swicthes set to off.

If he or she then selects an aircraft that uses a panel that does not have those switches (the battery particularily) - the aircraft will fly but will crash when the battery charge has been exhausted - usually within 15 minutes. Why? Because the state of the battery (and avionics) have been passed on the the aircraft which he or she flies.

Load the default flight first - that assures the battery and avionics are "on" and those parameters will be passed on to whatever aircraft you decide to fly.

Hope these ideas are useful.