Jump to content

Strange Managed Speed problem


Bernd E.

Recommended Posts

Hi all,

 

I have no idea why this happend in this flight, probably I missed something. On the last 10 flights, no problem.

If I set to managed speed, it goes down to 134. Approach Phase is not activated.

 

Please login to display this image.

Please login to display this image.

 

Flying the A321 CFM Sharklet Version (latest Version).

 

Routing: EDDF SOBRA Y180 NISIV UY180 DIK UN857 GIMER UT300 PON UN872 ERIGA UN741 LOTEE DCT AGADO DCT VERAM Q205 PECKY UQ146 EPAKA LPMA

Link to comment
Share on other sites

  • Replies 70
  • Created
  • Last Reply

I have just had the same problem in cruise. Managed speed drops, I have had to turn off the Autothrottle.

Something not quite right with the latest update it seems V1.2.1.3.A320 model All other flights have been without problems.

 

Keith

Link to comment
Share on other sites

I managed to get into the situation depicted in the first screenshot yesterday while flying EFHK/LOWI. I was messing with the arrivals while on cruise when suddenly the managed speed went to approach speed. I loaded up second flight plan and everything was well again.

Link to comment
Share on other sites

I've had this twice now on a flight from ESSA to ENTC. First on climb out of 01L, target speed went from correct 250 to V2 on it's own. Second issue on cruise with a change to the arrival, suddenly target speed went to V2 or there about again.

Please login to display this image.

Please login to display this image.

Link to comment
Share on other sites

I also have the same Problems.

I´ve had to stop the managed control and put the Hand on normal Autopilot Speed - managed route heading is working - and the Altitude by selecting manuell the climb and descent rate.

This happened now for two flights...

Greets Bob

Link to comment
Share on other sites

This sounds like possibly the same issue I reported here:

 

 

Ultimately, I wasn't able to successfully use managed speed until final approach.  Even at around 10,000 feet, it was still targeting low; about 230 kts even though there was no speed restriction in the FMC.

 

Curiously, in an attempt to solve an unrelated issue, I reloaded an autosave that had been saved during cruise, at a point well after the problems began and just for curiousity's sake I pushed into managed mode and voila - it was working properly (!); targeting either M0.78 or 0.79 (I forget which, exactly).  I'll be attempting the return leg to KFLL probably tomorrow, so I'm curious to see if it happens again - or if I should just be boring and put it in manual mode after TOD!

 

I can't discount that the issue is related to the 1.2.1.3 update as I don't believe I had flown an entire flight of the A321 IAE since its initial release (which worked just fine, vertical profile issues notwithstanding, on a similar duration flight of 3+ hours).

Link to comment
Share on other sites

On 11/10/2018 at 6:53 AM, chum said:

Any news? Same Problems here.

 

Matthias

Per response on my thread it is a known issue and being looked at...

 

For now the work-around is to use managed speed mode or "rebuild" the flight plan using SEC F-PLAN.

 

 

Link to comment
Share on other sites

8 hours ago, Mathijs Kok said:

We are still unable to recreate this following all correct procedures. Do make 100% sure the MCDU is fully filled because something missing there could cause this.

That would mean that when I install the latest full download it works but the last 2 updates I suddenly don't use the MCDU correctly. I will be again uninstall it and reinstall the last download before the updates until someone can fix it.

Link to comment
Share on other sites

The same happened to me yesterday night...the only strange thing I noticed was that i forgot to set the "engine start selector" to the middle position. I was flying with the selector on Start position.

I don't know if this could be the cause of my problem.

Link to comment
Share on other sites

Hi all,

 

short update from my side: I did not have this issue on the last 20 flights. 

No Idea which behaviour does affect this strange "issue".

 

vor 42 Minuten, qfuso sagte:

The same happened to me yesterday night...the only strange thing I noticed was that i forgot to set the "engine start selector" to the middle position. I was flying with the selector on Start position.

I don't know if this could be the cause of my problem.

Cant belive that this can cause this but I will do a test flight today if this is affecting the speed 😀

 

 

Best Regards

Bernd

Link to comment
Share on other sites

Hi Flyingpilot1740,

I was flying from EDDF TO LIRF AT FL380; This is how i prepar my flight (for a complete test):

1) i have a pre-saved flight on EDDF airport as the default airbus product (engine running ready for take off)

2) once loaded from Prepard 3d I change time of flight and then I select Cold and Dark state panel.

3) I wait 2 minutes waiting everithing is off till engine sounds go off then I power up the airbus.

Maybe not but I think that testing from saved flights is different from direct loading aircraft.

If you check you will also notice that during the flight control check the ailernos will not deploy fully

thank you very much

Stefano

Link to comment
Share on other sites

I'm having the same issues. Managed speed is completely messed up. In Climb Phase the Init Page says Managed 331/.78 however FMGS commands 201 until Alpha Floor, in Cruise Phase the Speed is even set to 113, Decent Phase 201 again. Correct weights have been entered, wind has been uploaded.

 

Flight:   LIMC EDDF, FL320, CI 48, pax 138, cargo 6.0, fuel 6.4, ZFW 57.3, ZFWGC 26.0

 

Addons:  AS for P3D4, Aerosoft A319 latest update (no experimental updates), Aerosoft LIMC and EDDF, Ultimate Traffic Live, Time Zone Fixer, GSX v1

 

Btw, this was just the recent flight, I've been having the same issues for a while.

 

Thanks for figuring out what went wrong!

 

 

Please login to display this image.

Please login to display this image.

Please login to display this image.

Please login to display this image.

Please login to display this image.

Please login to display this image.

Link to comment
Share on other sites

@Irishcurse  Well that much was obvious! The bug didn't occure from the beginning, so clearly one of the updates must have caused the fault. Reinstalling without updates can't be the solution since the updates solved other bugs and/or brought more features to the bus.

Link to comment
Share on other sites

I found a solution for my described problem:  The Load and Fuel Page of the AS A319/320 calculates the wrong ZFWGC and Trim, the Fuel Planner comes up with different numbers. I used them instead and didn't have those issues described earlier. I noticed before that the Load and Fuel Page always showed ZFWGC 26.0 and Trim 0.8, I guess there's the bug. Just use the figures from the Fuel Planner and it should work.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use