320 kts below 10,000 ft?

[Sinandgrin 0]

I was wondering if there was a way in the FMGS to tell the aircraft that I want to accelerate above 250 below 10,000 in the managed speed mode? So for example if the transition altitude was at 6000 feet and I wanted to accelerate to my 320/.78 climb speed sooner than 10,000 ft, could i delete the restriction somehow?

[Emi 5161]

The transition altitude is not related to the 250kt limit. In most countries of the world it is 250 below FL100/10.000ft. There are some very rare exeptions such as the United Arab Emirates where it is 8.000, but that's really very rare.

Nevertheless, just fly it in selected mode. Why always make things difficould if they can be done so easy?

[Sinandgrin 0]

The transition altitude is not related to the 250kt limit. In most countries of the world it is 250 below FL100/10.000ft. There are some very rare exeptions such as the United Arab Emirates where it is 8.000, but that's really very rare.

Nevertheless, just fly it in selected mode. Why always make things difficould if they can be done so easy?

Thanks for the reply, I will fly it as suggested. I was just wondering if I was missing something or if the aircraft in real life was capable and it was just a feature that was not modeled.

[ramon.cutanda 21]

Hi,

I like to fly with FSAirlines, which uses a client that registers some information about the flight and penalises you if don't follow some rules. One of them is the 250 knots limit under 10,000 feet. Sometimes, because of sudden wind changes or turbulences, the air speed temporaly goes up by 5-6 knots, but that's enough to trigger a penalisation, so I tend to do the climbings and descents at 245 knots.

Clicking in the right button of any of the waypoints I can see the standard speed restriction at the left (250/FL1000) but I haven't been able to figure out how to change that value. If I try to type over 245/FL100 or 245/10000 nothing will happen. Any other value, such as 245/ triggers a "BAD FORMAT" message. If I use the CLR button I can delete that speed; but then it is not possible to enter any other value, so the limit just disappears.

Right now I'm using P3D v2.3 (same behaviour with 2.2) Am I missing something, is it a bug, or that function is not implemented in the Airbus X? (it works in Blackbox Simulation Airbus Prologue)

Thanks for any hint on this.

Kind regards,