Marijn
Active member
For landings on earth, I've been using BaseSync and AeroBrakeMFD for most of my flights. This always worked quite well, but I wanted some more control over the final approach with a pre-planned circuit. So, I had a go with the BaseSync and Glideslope combo. But I am not getting the results I was expecting. In fact, I end up almost 3000km short of the base. So I must be doing something very wrong.
Glideslope is configured for runway 15 on Cape Canaveral using the default 'XR Series' GS, which should be fine for an almost empty XR5 I'd say. The starting orbit is 190kmx190km with one orbit to go before passing over the base. I target 'GS2' in BaseSync and everything seems fine. I let de autopilot of BaseSync do the burn.
After leveling the horizon, I let the XR attitude autopilot follow the reference values as indicated on the DATA screen of the Glideslope MFD. AoA is around 41 degrees. At first things seem ok, but after a short while Glideslope indicated an energy problem. It starts as a small difference, but this escalates out of control quite rapidly.
The dEngy value becomes many times bigger than the reference value. During the whole re-entry, I am losing energy. This already starts at 100km of altitude. I was not expecting that. Why would a plane loose so much energy in such thin air? AeroBrakeMFD is confirming that following the AoA as dictated by the Glideslope reference value is a bad plan which will end up short. Another thing wich caught my attention is that Glideslope shows a reference value for VAcc=0. At 70km of altitude. How is it possible not to decellerate while flying at 70km?
Any ideas on what I could be doing wrong? Thanks.
GS v2.7
BS v3.3
Glideslope is configured for runway 15 on Cape Canaveral using the default 'XR Series' GS, which should be fine for an almost empty XR5 I'd say. The starting orbit is 190kmx190km with one orbit to go before passing over the base. I target 'GS2' in BaseSync and everything seems fine. I let de autopilot of BaseSync do the burn.
After leveling the horizon, I let the XR attitude autopilot follow the reference values as indicated on the DATA screen of the Glideslope MFD. AoA is around 41 degrees. At first things seem ok, but after a short while Glideslope indicated an energy problem. It starts as a small difference, but this escalates out of control quite rapidly.
The dEngy value becomes many times bigger than the reference value. During the whole re-entry, I am losing energy. This already starts at 100km of altitude. I was not expecting that. Why would a plane loose so much energy in such thin air? AeroBrakeMFD is confirming that following the AoA as dictated by the Glideslope reference value is a bad plan which will end up short. Another thing wich caught my attention is that Glideslope shows a reference value for VAcc=0. At 70km of altitude. How is it possible not to decellerate while flying at 70km?
Any ideas on what I could be doing wrong? Thanks.
GS v2.7
BS v3.3