Jump to content

Archived

This topic is now archived and is closed to further replies.

77west

Takeoff Config Warning - At 33000ft!

Recommended Posts

I hope this is easy to explain but on my last 2 NGX flights, one an -800WL and one a -700, I get the takeoff config "beep beep beep beep......" sound at random whilst mid-flight. After reloading from a saved point, it is quiet but returns a short time later. There are no visual lights, cautions or warnings, and even cycling the gear and flaps will not clear it.


Wes Meyer

Share this post


Link to post
Share on other sites

Yep sounds like pressurisation. Are your packs switched on? Bleed air from the engines?


Callum McLoughlin

Share this post


Link to post
Share on other sites

Remember Helios Flight 422... Tragic story.

 

Mistook Take-off Configuration Warning Horn with Pressurisation Warning


Best regards,
--Anders Bermann--
____________________
Scandinavian VA

Pilot-ID: SAS2471

Share this post


Link to post
Share on other sites

No the pressurization was definitely set, I have been flying the NGX for long enough and use the checklist, packs on, auto. After testing, I think it might have been a panel state bug, as after using a different panel state I managed to complete a full VATSIM flight without the embarrassment of disconnecting mid-flight! So I think it might have just been a random glitch at this point.


Wes Meyer

Share this post


Link to post
Share on other sites

EDIT: Just re-loaded the flight to double check, interestingly although the pressurization altitude was set and both packs on, the cabin alt had reached 10,000ft - which would explain the alarm. Now I DID NOT tail strike, and not sure if tail-strike depressurization is even modelled on the NGX like it is on the -200LR, I am going to chalk it up to a corrupt panel state that I created myself a week or two ago. Because my successful flight used the default CLDDRK panel state. Thanks for all your tips however!!


Wes Meyer

Share this post


Link to post
Share on other sites

Did you set cabin alt?

Failing to set FLT ALT correctly will not cause a high cabin altitude. The system is smart enough to keep it within limits. You may however experience uncomfortable cabin rates of change if it is set wrong though. 


Tom Landry

 

PMDG_NGX_Tech_Team.jpg

Share this post


Link to post
Share on other sites

EDIT: Just re-loaded the flight to double check, interestingly although the pressurization altitude was set and both packs on, the cabin alt had reached 10,000ft - which would explain the alarm. Now I DID NOT tail strike, and not sure if tail-strike depressurization is even modelled on the NGX like it is on the -200LR, I am going to chalk it up to a corrupt panel state that I created myself a week or two ago. Because my successful flight used the default CLDDRK panel state. Thanks for all your tips however!!

Does your computer have an ASUS motherboard by chance? Some models are known for having a dodgy CMOS clock, which can produce strange problems in some PMDG aircraft. I believe that pressurization problems without obvious cause are one possible symptom of this issue.


Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

Share this post


Link to post
Share on other sites

Does your computer have an ASUS motherboard by chance? Some models are known for having a dodgy CMOS clock, which can produce strange problems in some PMDG aircraft. I believe that pressurization problems without obvious cause are one possible symptom of this issue.

Hi Jim, no I use Gigabyte. I am usually the first to suggest ASUS CMOS issues in cases like this! Now after thinking about it, I did have some overheating issues yesterday morning due to a blocked CPU heatsink (damn cat fur) I usually clean it more often but sort of forgot after moving. But I realized I made some changes to my custom panel state yesterday BEFORE fixing my overheating issue, and wonder if perhaps this is why the panel state was dodgy.


Wes Meyer

Share this post


Link to post
Share on other sites

Could well be a dodgy save state... but just to be sure: In addition to packs being on, are your engine bleeds on, and is the pressurisation mode selector set to auto?

 

What is the indicated position of the outflow valve? What is the cabin VSI showing?

 

Can you post a screenshot of the overhead?

Share this post


Link to post
Share on other sites

Could well be a dodgy save state... but just to be sure: In addition to packs being on, are your engine bleeds on, and is the pressurisation mode selector set to auto?

 

What is the indicated position of the outflow valve? What is the cabin VSI showing?

 

Can you post a screenshot of the overhead?

I am pretty much 100% certain it was a dodgy save as I have subsequently completed test flights with no issues. I can assure you that engine bleeds were ON, packs ON, Isolation Valve AUTO, Pressurization mode set to auto, correct altitude dialled in. I would have to reload the flight to get a screenie. 


Wes Meyer

Share this post


Link to post
Share on other sites

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    50%
    $12,660.00 of $25,000.00 Donate Now
×
×
  • Create New...