This may be pilot error, I'm still not sure......

Notable circumstances:

FS2Crew was being used

It was a packs off take off (handled by fs2crew)

CMD A On in vnav and lnav modes FLT ALT was set to 350000 on the pressurization panel

Step to FL370 was entered into the the FMC

MCP was then set to FL370

Aircraft continued climb pas initial FL350 to FL370

 

At this point I got a master caution but was confused by the lack of any system annunciator lights. It took me a while to figure out that the "Auto Fail" was lit on the pressurization panel and the pax oxy had deployed. Rather than carry out an emergency decent (which of course I would do in the real world;)) I decided to try and figure out what was going on, I set the pressurization mode selector from Auto to ALTN, then manual and altered the dump valve position until I got an acceptable cabin pressure and differential. (All good so far) I then noticed that for some reason the APU was on, strange I thought as I didn't think it ran at FL370.... after checking that the APU generators were off and the Engine generators were on, I shut down the APU at which point I departed from controlled flight and crashed (very quickly)

 

The PMS WAS set to auto wen I took off. So Questions:

Why did the auto pressurization fail? could the setting of 35000 in the panel and climbing past that level to FL370 cause it to fail?

Why was the APU on? possible fs2crew failed to turn it off?

Why did I depart when I switched off the APU?

 

I'm not expecting a full explanation of any of this as I cant give you my exact actions and system states, unfortunately there is no flight data recorder.... I would however appreciate feedback from anyone who has had a similar experience and uses FS2Crew.

This may be pilot error, I'm still not sure......

Notable circumstances:

FS2Crew was being used

It was a packs off take off (handled by fs2crew)

CMD A On in vnav and lnav modes FLT ALT was set to 350000 on the pressurization panel

Step to FL370 was entered into the the FMC

MCP was then set to FL370

Aircraft continued climb pas initial FL350 to FL370

 

At this point I got a master caution but was confused by the lack of any system annunciator lights. It took me a while to figure out that the "Auto Fail" was lit on the pressurization panel and the pax oxy had deployed. Rather than carry out an emergency decent (which of course I would do in the real world;)) I decided to try and figure out what was going on, I set the pressurization mode selector from Auto to ALTN, then manual and altered the dump valve position until I got an acceptable cabin pressure and differential. (All good so far) I then noticed that for some reason the APU was on, strange I thought as I didn't think it ran at FL370.... after checking that the APU generators were off and the Engine generators were on, I shut down the APU at which point I departed from controlled flight and crashed (very quickly)

 

The PMS WAS set to auto wen I took off. So Questions:

Why did the auto pressurization fail? could the setting of 35000 in the panel and climbing past that level to FL370 cause it to fail?

Why was the APU on? possible fs2crew failed to turn it off?

Why did I depart when I switched off the APU?

 

I'm not expecting a full explanation of any of this as I cant give you my exact actions and system states, unfortunately there is no flight data recorder.... I would however appreciate feedback from anyone who has had a similar experience and uses FS2Crew.

 

Hi steve,

 

Pilot error basically it sounds like, Did you make the "climb thrust call" ?

 

 

call “CLIMB THRUST” at the thrust reduction altitude depending on your NADP profile (this is a verificationcall only). This triggers the F/O to put the packs back on.

 

3 causes for AutoFail to illuminate are

1) loss of AC power for more than 15 secs, (if it's less than 12 it goes back to AUTO)

2) cabin alt exceeds 13,875ft

3)excessive cabin rate of pressure change (1890fpm or 1.0psi per min)

 

With the packs off at that altitude you're surely gonna get into some trouble,

 

Also, when doing a step climb set the new altitude in the flight altitude window BEFORE starting the climb.

 

Yes your F/O didn't turn the off because you failed to make the climb thrust call

 

I don't quite understand the last question though,..but hope i help you to understand.

 

Regards

Yup, probably missed the "climb thrust" call as that's the trigger for the FO to restore the bleeds/packs.