As the topic suggests today I had my first failure modelled by FS2Crew and therefor spotted by the FO, must say it felt really cool and took me by 100% surprise but we worked it out together and was able to continue the planned flight :smile:

 

However I'm not sure if the flight would have went on IRL because we had the failure when still on the ground right after pushback and this puzzled me a bit because when I read in the Emergency manual for the failure we experienced it said the aircraft needed to be airborn for the FO to spot the failure which we clearly were not since we just completed out pushback...hmm...

 

The failure we experienced was:

 

ELECTRICAL -> GEN 1/2 DRIVE DISC

For that one, you'd probably want to return to the gate and have the engineers look at it   B)

Yep...I fully agree but I still don't understand how the FO was able to spot the failure since the documentation says you need to be in the air for him to spot it?

Was it a higher altitude airport you were at?

 

 

Sent from my Apple communications device.

No, this was at ESSA my home airport where the elevation is approx 140 feet.

Just a bug in the manual.  I'll update it.

Ok, got it.

Richard - may I ask what your failure settings in the next are? I have mine set to Random=yes, service baseed=no, 4 events pr 10 hours, and 1 event limit. Haven't had a failure yet? I'm using the NGX Short panel state as start up state...

 

Mas

I have it the other way around, that is random=no and service based=yes. I don't use any special panel state but always start with the panel as I (and my virtual FS2Crew FO) left the a/c last flight after running through the Secure Aircraft checklist.