A320 - landing with GPWS blaring

[Slasher]

Does anyone know how you get a GPWS warning during the late landing phase on this thing? :confused:

I figured an EGPWS database error but it doesn't gel.


IA3F40TPUgM


PNH is flat as a tack (MSA 2000 in the approach sector).

[Jonty]

Airport not in the terrain database, would be my guess. The flatness of the surrounding terrain would contribute to the lateness of the activation.

[Cough]

Mis set QNH...

[hawk37]

Don't now the answer but if the airport not in database, caution and warnings start way earlier than 100 feet. I believe most TAWS use gps altitude now, so mis set qnh would not set off the alarm. The approach looks stabilized and on papi.

[flyburg]

Computer hickup??

[99jolegg]

Had something similar but not as prolonged into ZRH. No idea why.

[Denti]

We had nuisance warnings like that flying into several airports, LFMN being one of them, until honeywell fixed it with the next database cycle.

[Dani]

I had a very nasty indicent - it was not an Airbus but another highly automated fly-by-wire aircraft (SB20). There was a lot of slush on the runway, which was sprayed onto the lower side of the fuselage, some chunks of it must have frozen and stuck to the radio altimeter antennas.

We didn't find out until approaching destination. As soon as we lowered gear, GPWS didn't stopp yelling. Since we were severely CAVOK and had no other warning, we figured out that it must have been a nuissance.

I'm not sure now if we also found out that radio altimeter always stayed at zero height.

Dani