pospel 9 Posted November 20, 2014 Share Posted November 20, 2014 How can I fix it? Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted November 20, 2014 Deputy Sheriffs Share Posted November 20, 2014 Sorry, no idea what you are talking about. Please work through the step-by step-guide. And next time please describe in detail what you are seeing (screenshot) and more detailed what you have done, which phase of flight, what you have entered into the left MCDU and in the FCU (best would also be screenshots). Link to comment Share on other sites More sharing options...
pospel 9 Posted November 21, 2014 Author Share Posted November 21, 2014 Sorry. I made video with alarms of airbus. http://youtu.be/xC-YMy1R_JI?t=6m49s Terrain ahead when straight only sky. http://youtu.be/xC-YMy1R_JI?t=8m26s Leaving a given height. http://youtu.be/xC-YMy1R_JI?t=9m52s 2500ft on radio altimeter. I hope now more clear. Oh! A have airbus v1.10 Link to comment Share on other sites More sharing options...
PikalaxALT 19 Posted November 21, 2014 Share Posted November 21, 2014 200 is too high of an initial climb speed. Suggest setting no more than V2+20. Furthermore, your initial climb rate was unusually low. Normal rates are in the range of 2000+ fpm. You also started to lower the nose at 200 feet; you should maintain minimum climb speed until at least 1000 feet above ground level to ensure terrain clearance. Because you were departing into terrain set above the field and you were not climbing fast enough to avoid it, the terrain alarm sounded. That altitude warning horn sounds when you pass your selected altitude. That is normal. To silence it, simply select a new altitude. The repeated "2500" warnings occur when you are just at the cusp of activating the radio altimeter. This indicates uneven terrain and is normal. The repeated beepings are from the overspeed warning (too fast for current configuration!!) Link to comment Share on other sites More sharing options...
pospel 9 Posted November 21, 2014 Author Share Posted November 21, 2014 200 is too high of an initial climb speed. Suggest setting no more than V2+20. Furthermore, your initial climb rate was unusually low. Normal rates are in the range of 2000+ fpm. You also started to lower the nose at 200 feet; you should maintain minimum climb speed until at least 1000 feet above ground level to ensure terrain clearance. Because you were departing into terrain set above the field and you were not climbing fast enough to avoid it, the terrain alarm sounded. That altitude warning horn sounds when you pass your selected altitude. That is normal. To silence it, simply select a new altitude. The repeated "2500" warnings occur when you are just at the cusp of activating the radio altimeter. This indicates uneven terrain and is normal. The repeated beepings are from the overspeed warning (too fast for current configuration!!) I hope that you have no relationship to develop. Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted November 21, 2014 Deputy Sheriffs Share Posted November 21, 2014 Again, work through the step-by-step guide to learn how to fly an Airbus. Link to comment Share on other sites More sharing options...
pospel 9 Posted November 21, 2014 Author Share Posted November 21, 2014 Again, work through the step-by-step guide to learn how to fly an Airbus. Everything is as it should work? Link to comment Share on other sites More sharing options...
Cheyenne Chief Pilot 829 Posted November 21, 2014 Share Posted November 21, 2014 The repeated GPWS callouts (radio altimeter) at too short intervals are a known issue. Your EGPWS indications ("terrain warnings") seem highly unusual - but so do a lot of details of your flight. As that sort of terrain warnings has not occurred during tests so far, can you confirm this issue happens with a clean, by-the-book installation of the Airbus? Link to comment Share on other sites More sharing options...
pospel 9 Posted November 21, 2014 Author Share Posted November 21, 2014 The repeated GPWS callouts (radio altimeter) at too short intervals are a known issue. Your EGPWS indications ("terrain warnings") seem highly unusual - but so do a lot of details of your flight. As that sort of terrain warnings has not occurred during tests so far, can you confirm this issue happens with a clean, by-the-book installation of the Airbus? Ok. I will try make clean installation. Link to comment Share on other sites More sharing options...
Joshua Che. 1601 Posted November 21, 2014 Share Posted November 21, 2014 http://forum.aerosoft.com/index.php?/topic/67438-step-by-step-flight-videos-now-available-version-110/ Video to help you if you dont like reading Link to comment Share on other sites More sharing options...
pospel 9 Posted November 21, 2014 Author Share Posted November 21, 2014 http://forum.aerosoft.com/index.php?/topic/67438-step-by-step-flight-videos-now-available-version-110/ Video to help you if you dont like reading Understood. I don`t can fly A32x and reinstall don`t help me. Thanks. Link to comment Share on other sites More sharing options...
Emi 5161 Posted November 21, 2014 Share Posted November 21, 2014 I hope that you have no relationship to develop. I hope I either midunderstood this post, or you won't make such a post again, otherwise you'll run into troubles. As the poster of the post you replied this to already told you the alert is normal if you leave the altitude dialed into the FCU and there is nothing to be fixed. It works completly correct. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted November 22, 2014 Aerosoft Share Posted November 22, 2014 Just start with the step by step flight and you will soon be flying the busses. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.