Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Weird decompression in the cruse

Featured Replies

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.

"Military Intelligence is a contradiction in terms"

Paul Yates

  • Commercial Member

Sounds like you let FS2Crew work with the packs off takeoff, but never went through the motions required to return to normal operations. Chances are there's an alternate workflow for packs off, and you may have tried to continue on the normal checklist. I'd check the FS2Crew manual/forums to see if that has any guidance for the different operation.

 

I've never done a packs off takeoff with FS2Crew, but I imagine there are a different series of prompts you must go through, when compared to the normal checklist.

 

Also, just a side note: you can run the APU at altitude (this is required when flying ETOPS - I forget the service ceiling). It'll run up there, you just can't start it at altitude (it can be started when in the air, just not at altitude because of the air density).

Kyle Rodgers

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

 

Well there's your problem.....lol

Dave Swanson

  • Author

Well there's your problem.....lol

 

mmmm, what? autopilot being on? in lnav and vnav ? why's that my problem? or am I missing something?

"Military Intelligence is a contradiction in terms"

Paul Yates

  • Commercial Member

mmmm, what? autopilot being on? in lnav and vnav ? why's that my problem? or am I missing something?

 

I didn't get it either.

 

I think the biggest issue is that the packs were probably still off. I don't think it was a failure of the systems as much as a failure to double-check everything was set properly. I may be assuming, but at the same time, I didn't pick up on any of your post actually pointing to the fact that the packs were back on. The APU being on also lends a hand to that idea. It just makes me think nothing ever got cleaned up after the packs off takeoff.

Kyle Rodgers

get it? 350,000 , was it real dark outside?

 

Eric Wallace

  • Author

get it? 350,000 , was it real dark outside?

 

Eric Wallace

 

Ahhhhh, now I get it, typo obviously unless I was using a solid rocket booster add on. LOL

 

I didn't get it either.

 

I think the biggest issue is that the packs were probably still off. I don't think it was a failure of the systems as much as a failure to double-check everything was set properly. I may be assuming, but at the same time, I didn't pick up on any of your post actually pointing to the fact that the packs were back on. The APU being on also lends a hand to that idea. It just makes me think nothing ever got cleaned up after the packs off takeoff.

 

Your probably correct, I don't recall a pacs on call from the FO after takeoff.

"Military Intelligence is a contradiction in terms"

Paul Yates

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.