Now, another confusion has to do with the recommended turbulence settings in AS16 and this clearly has to do with the misinterpretation of what each setting does. Otherwise, no reason to use Active sky at all. If you get a PWS warning during approach, you actually have to go around.
This however will make the radar just render some nice eye candy colorful images Īs for the Microburst/Windshear, I'm sorry you can't disable it. If for whatever reason you want to fly into a CB and continue your path/approach, you can uncheck the "Realistic thunderstorm up/downdraft" option in AS16 settings. With AS16 we apply up to a maximum of 2-3000 ft/min intentionally trying to destabilize the aircraft and try to make it lose control. In reality flying close to a CB (less than 20 miles margin) is definitely avoided, because updraft/downdraft events up to 10000 feet/min may be encountered.
The PF in this case went directly into the "reds". The main (but not the only) reason we did this was to troubleshoot any AP disconnect events (this way isolating them to a fault in the aircraft itself back then).Īn example of atmosphere instability is evident in the video linked previously. Based on all that during A320x beta testing we decided to recommend lowering the up/downdraft settings in ASN (btw with AS16 this is not needed, as we automatically adjust it based on the aircraft type now). You can see the applied air vertical speed in AS16 debug window (in a second monitor or if you run in a network). Now, the first 2 can be reduced by reducing the related options, but not the 3rd and 4th one. Atmosphere instability due to convective activity (including flying close/into CBs) Thermal generation (based on temperature, time of day, season and of course surface type) Terrain/winds (in contrast to what is assumed in a previous post) Updraft/downdraft implementation in Active sky is based on the following triggering conditions:
0 kommentar(er)
