Based on what others are reporting, this issue seems to be related to the amount of water in the vicinity of the arrival airport. LFMN, KSFO, KSEA, PHNL, KORD - all places where people are seeing the false terrain warnings, and all airports which are immediately adjacent to, or surrounded by, large bodies of water.

This is possible because all airports where it happened to me were close to the sea (LEBL, EGGP, LPFR). Yesterday I haven´t got the problem as I was aprroaching LEPA which is on an island. Probably because the approach was over the island (ILS24L) and I came not from the sea!?

Can you guys repeatedly get these errors? We saw something like this randomly early in testing of the EGPWS but I could never reproduce it. Please give us as much info as you can.

will post some pics tonight. had this last night during the approach into cairns by orbx flying into rwy15 and coming over the mountains on the coast (was the BING/BONG STAR, cannot remember its name right now :-)). If you follow that STAR to align with rwy15 for the ILS approach you come from the west and 'overshoot' the coast line to fly out over the sea before you turn right to capture the LOC. I was already clear of the mountains behind me and over the water when I still saw red terrain warnings ahead of me. besides that, what a great flight. what a wonderful scenery and what an amazing airplane. still learning a lot though, was not able to do an autoland so far as only CMD comes up but I will get that done soon. hopefully. just printed all the pdf manuals, a nice read in the offce ;-). if anything fails I will apply the autoland patch via FMC...

This is possible because all airports where it happened to me were close to the sea (LEBL, EGGP, LPFR). Yesterday I haven´t got the problem as I was aprroaching LEPA which is on an island. Probably because the approach was over the island (ILS24L) and I came not from the sea!?

interesting. this indeed corresponds to my findings above

the 05R approach at EDDL where it happened to me is over the river Rhine which is quite big and there's a harbor there as well.

just ran across this post http://forum.avsim.net/topic/342837-darn-that-global-warming/. I learned that the terrain warning uses a pmdg database and is not reading the actual mesh data from fsx. in my case this can be the reason why terrain is shown over water if orbx adjusted the coastline around cairns and while I am over water fsx (and hence the ngx) still sees me over the mountains. do the other who are experiencing this behaviour have also installed 3rd party scenery? not sure though how it translates to avhpilot's case over the rhine unless he uses also some 3rd party scenery which re/mis-placed the rhine.

not sure though how it translates to avhpilot's case over the rhine unless he uses also some 3rd party scenery which re/mis-placed the rhine.

as a matter of fact i forgot to mention that i have installed FS Global as well as FS Altitide Europe

as a matter of fact i forgot to mention that i have installed FS Global as well as FS Altitide Europe

I have FSGlobal Ultimate - but I don't think that's the cause of the problem. After landing last night at KBFI, I shut down to a cold & dark state, and saved my flight. This morning, I started back up from the saved situation, took off from KBFI, climbed back up to 4000 feet, and did a couple of circuits. I was following approximately the same path as I did last night on my arrival into the Seattle area, and landed on the same runway - 13R - but this time, no false terrain warnings. The terrain map did show some of the higher terrain east of the airport in yellow - but no red blocks in frot of the aircraft, and no "pull up" audio warnings. It does seem that the issue arises mainly after a longer flight. I don't know if it has something to do with the actual duration of the flight, or if the simulated EGPWS gets into a strange state once the aircraft has climbed up to a typical cruise level above 30,000 feet, and then begins a descent. As I mentioned in my previous post, a real EGPWS changes its operating mode and its audio and visual (mapping) mode of operation based on the aircraft's configuration. IF the aircraft was lined up for an approach to a runway, following the localizer and glideslope perfectly, BUT the flaps and gear were not extended, you would see an effect similar to what happens in this simulation after a long flight. The EGPWS would look ahead at the terrain in front of the aircraft, and knowing the aircraft's rate of descent, the predictive function of the system would "know" that the aircraft is going to fly into the ground when it arrives at the airport, and it would then start to turn the terrain surrounding the airport yellow, and then red, (even if the airport is on perfectly flat ground) and would give a "terrain ahead" warning, followed by a "pull up" message as the radar altimeter starts to detect the terrain beneath the aircraft getting closer and closer as the aircraft descends. However, when the gear is lowered, and the flaps extended, the EGPWS switches into a different mode. It no longer will give "pull up" warnings, just because the underlying terrain is getting closer - as that is a normal consequence of landing. It will still give warnings if the rate of descent is too high, or if the angle of descent is such that the aircraft would strike high ground before arriving at the runway - but other than that, it operates differently than it does when the aircraft is not in landing configuration. I may be barking up the wrong tree here, but it almost seems that after a long flight, with a climb to a high cruise altitude, and later descent for landing, the the NGX EGPWS does not recognize that the aircraft is in landing configuration - even when all procedures are followed... i.e., selecting an approach in the FMS, selecting a landing flap setting and VREF on the INIT page, properly tracking the localizer and glideslope, lowering gear and flaps, reducing airspeed etc. It seems as if it is reacting the way it would if the aircraft was simply descending into rising terrain while still in cruise configuration. That would explain why the terrain map starts to show all red, (even over bodies of water) as the aircraft gets closer to the ground... but it does not explain the large red blocks immediately in front of the aircraft. That would seem to indicate corruption in the terrain database - but, at least in my case, if I simply do circuits at an airport, while never climbing up to the flight levels, there are no terrain glitches on the display, and no audio warnings to pull up.

That would explain why the terrain map starts to show all red, (even over bodies of water) as the aircraft gets closer to the ground... but it does not explain the large red blocks immediately in front of the aircraft. That would seem to indicate corruption in the terrain database -

jim, basically agree. just want to throw in that I did not see generally all red over the water, I saw your latter observation: peaks depicted by red blocks which seems wrong. I will double check tonight and post the pics I took last night (after a some hours flight from YSCH to Cairns) and then try the same approach at Cairns again from a traffic pattern to see whether it is really a matter of long(er) flights messing up with the system or not

I have to agree with Jim! When you see my pics (post #23) there are to completely different terrain ND´s at the same location. Second pic was a local airport circuit and apparently the terrain ND works correctly on this pic. I also have this problem only after longer flights in higher levels.

Can you guys repeatedly get these errors? We saw something like this randomly early in testing of the EGPWS but I could never reproduce it. Please give us as much info as you can.

Short final runway 25 EDDS (Aerosoft Stuttgart X scenery), perfectly on LOC/GS, yields a "Terrain/Pullup" warning from GPWS.

Just completed my first full flight with the NGX 800WL from KVCV to KBFI. The aircraft performed flawlessly in every regard with the exception of this terrain problem. Approaching KBFI on the Olympia 7 arrival, I started getting the red blocks and "pull up" messages as I descended below 4000 feet on a right downwind for a visual approach to runway 13R. Before departure from KVCV, I turned peaks mode OFF, and "show water as cyan" was also turned off. Time enroute was about 2 hours. Based on what others are reporting, this issue seems to be related to the amount of water in the vicinity of the arrival airport. LFMN, KSFO, KSEA, PHNL, KORD - all places where people are seeing the false terrain warnings, and all airports which are immediately adjacent to, or surrounded by, large bodies of water. Either that, or perhaps the simulated EGPWS is not transitioning to approach mode. The EGPWS computer receives status signals from the flaps and landing gear, and its response to terrain should change once the aircraft is configured for landing.

I think PMDG got this warning during landing on addon scenery as well. Check out the 10th picture starting from the top in this forum: http://forum.avsim.n...es-and-the-ngx/That's the one with the interior. As you can see, there is that Terrain written in yellow on the ND for a precaution.

Today´s 4h flight from Dublin to Lanzarote (Canary Islands). This time it was completely different! Where the terrain ND should show the island of Lanzarote there was just nothing :-( I wanted to take a picture but my FSX crashed and it was caused by the PMDG NGX. Was my first CTD with NGX. Before the crash I have noticed that loading of textures (wingview for example) need longer than it is normal the case. Probably related to the terrain ND issue!?

jim, basically agree. just want to throw in that I did not see generally all red over the water, I saw your latter observation: peaks depicted by red blocks which seems wrong. I will double check tonight and post the pics I took last night (after a some hours flight from YSCH to Cairns) and then try the same approach at Cairns again from a traffic pattern to see whether it is really a matter of long(er) flights messing up with the system or not

This is what I meant: my yesterday's flight, right over the water turning to rwy15 at cairns. will try again now with just a traffic pattern.

I got the terrain warning going into 26R at ATL on the ILS at about 500 ft and it continued to about 150 ft. I got no RA callouts during the whole landing phase. TERR was selected off, and popped up with a red block in front of me, similar to what other people have shown. I don't think it's an issue being close to the water as ATL is hundreds of miles from any substantial body of water.

I got the terrain warning going into 26R at ATL on the ILS at about 500 ft and it continued to about 150 ft. I got no RA callouts during the whole landing phase. TERR was selected off, and popped up with a red block in front of me, similar to what other people have shown. I don't think it's an issue being close to the water as ATL is hundreds of miles from any substantial body of water.

still learning but I guess what you saw is the 'normal' GPWS behaviour, had terrain also pop up during approach mode with call outs when TERR actually off. on another side, yes. cannot be the water. did my ybcs approach again into rwy15 and now no red blocks over the water when turning after RAINY to final approach. all correct this time. again, this was a pattern thus a short flight.

I don't think it is the water because my pics I posted were at KPHX. I don't think there's much water there! It seems like such a small little problem. Hopefully it gets fixed and addressed because the rest of the simulation is superb! The strange thing is that when I flew to Anchorage from Seattle yesterday it didn't do it at all. And from everyone's experience it seems to be these long flights. Maybe it has to do with a certain switch on or when you configure yourself to land?