Hi Guys,

 

Finally brought the T7 into PANC today, and from about 2500 ft down, on the VNAV profile, the terrain avoidance warning screamed the entire way down.  I was over water most of the time.  I was using Aerosoft's PANC scenery....

 

Anybody else experience this?  Was there something I might have been doing wrong?

 

 

What flaps/gear positions were in place when it happened?

Gear up, flaps 15, slowing to approach speed of 147knots

Someone with more knowledge than me can confirm or deny this, but I believe that below 2,500ft the systems check to see if you're in landing config. Since gear up and flap 15 below 2,500ft isn't a landing config the system has to assume you're in a CFIT (controlled flight into terrain) and set off the terrain warning.

Thank goodness its working.

I had a similar occurrence once. GPWS accompanied me all the way down to the runway, first with "terrain" announcements and then "pull up." Gear was down, flaps 30, good landing speed. I still don't know what caused it and haven't been able to duplicate it since.

Ya, the warning continued right down through gear extension and flaps 30, all the way to the runway.  Luckily the inhibit button was not out of reach.

I have had nuisance terrain warnings as well.

I have also had no terrain warning while flying straight at a mountain!

 

The thing is, in real life, the GPWS uses a terrain data base.

I have updated FSX terrain with FSGenesis mesh worldwide.

Now what terrain data base does the PMDG777 database use?

 

Does it use a PMDG database that differs from the FSX database as well as my personal database?

Or does it use the standard FSX terrain database (which also differs from what I see out the window cause I use FSGenesis Mesh)

Or does it read and use my personal terrain database?

Someone with more knowledge than me can confirm or deny this, but I believe that below 2,500ft the systems check to see if you're in landing config. Since gear up and flap 15 below 2,500ft isn't a landing config the system has to assume you're in a CFIT (controlled flight into terrain) and set off the terrain warning.

That is probably windshear you are thinking of. The PWS (Predictive) starts scanning on approach from 2300ft. Windshear warnings are given once below 1500ft (or 1200ft in case of predictive windsear).

Ya, the warning continued right down through gear extension and flaps 30, all the way to the runway.  Luckily the inhibit button was not out of reach.

which means the warning was not due to flaps or gear. There are quite a few different aural warnings, all similar, but they all mean something different. Look in the back of the systems decription manual under Warning Systems. For instance the "TOO LOW TERRAIN' warning means "Descent below unsafe altitude while too far from any airport in the terrain database." And if PANC is not in the PMDG terrain database (or whatever database it uses) then you get a nuisance warning.

It occurred to me just now when landing at LXGB, and it has occurred for several times.

 

But I agree with fsgeek. 

I ve had the same problem on takeoff actualy right after the nose gear lifts off. Ive had this first time today but it happened 3 times.(i flew the t3 3 tiles). Whats actualy happens is the terrain warning kicks in while i takeoff and says "pull up, pull up" until some where 1500ft agl. And there is no terrain ofcours on the nd on my way.

Think this was a issue with the ngx as well, got  to do with the  scenery mesh

http://forum.avsim.net/topic/357566-terrain-warning-on-final-approach-and-landing/page-2?hl=%2Bterrain+%2Bwarning#entry2209911

http://forum.avsim.net/topic/407634-gpws-terrain-and-pull-up-warning-on-final-approach/?hl=%2Bterrain+%2Bwarning#entry2697849

I have had this occur to me as well, in full landing configuration and on an ILS.

It has happened at several airports, two I recall are EINN and EICK.

Roberto

 I've never had this with the NGX and only once in the 777 while approaching an landing at Innsbruck.

Ive solved my problem by switching the panel state from custom to the pmdg cld drk, i hope this helps.

Ive solved my problem by switching the panel state from custom to the pmdg cld drk, i hope this helps.

 Cold dark, and some custom states are going to be problematic.

 

Don't use cold dark. Use Long or Short.

http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread/