@flyinggreasemnky you have anything to add?
Would be neat if there was an industry wide newsletter publishedI was told by ASAP committee guy that it was a night visual into BTV runway 33 at night on the Q and they got a terrain warning. He didn't go any further into it. A memo came out the next day stating that the Q's are no longer allowed to perform night visuals into BTV. He did say that a breakdown of it will likely be in the FOQA/ASAP newsletter they put out.
Would be neat if there was an industry wide newsletter published
What's an ODP out of EAT?I will say that the Q's ground prox can be a little hyper-active sometimes. If you fly the published ODP as it is written out of EAT, you'll get an alert every single time.
Hah. Fair enough.What's an ODP out of EAT?
The Saab used to be the same way in and out of MVY if we were landing to the NE.I will say that the Q's ground prox can be a little hyper-active sometimes. If you fly the published ODP as it is written out of EAT, you'll get an alert every single time.
On the Q200 we would have to inhibit the terrain for the approach into Eagle and Aspen as the descent rates on each step down were so large (~1500-2500fpm) that it would set off the GPWS.I will say that the Q's ground prox can be a little hyper-active sometimes. If you fly the published ODP as it is written out of EAT, you'll get an alert every single time.
17' on the RADALT according to CDS download of flight data...
17' WOW! Why didn't they respond to the EGPWS call outs earlier?
In all fairness though, the RA on the Q400 is PA-THETIC, I've had it show anywhere from 0-2500ft at cruise. We've had issues with it causing "Pusher System Fail" cautions on landings because it scrolls through the #'s so fast on approach. Not saying the crew didn't get that close, but just an observation of the system.