A321 TOGA LK after T/O

[Michael_LOWW 4]

hey!

after take-off from eggw runway 08 with the a321 at 75.383 kg tow in flaps 3 configuration and with t/o flex +36 °c the commanded speed is in the yellow band and TOGA LK is activated before reaching the acceleration height. i used the fmc calculated v speeds. your advice is greatly appreciated.

best regards,

michael

[Michael_LOWW 4]

thanks for the prompt reply. will this bug be fixed in the next update?

[Lenair 9]

Hi

Got same problem here after installing the hotfix 018c...

[nakis03 3]

me to the same problem with 18c ALPHA FLOOR and then TOGALOCK

18b was better

[Cheyenne Chief Pilot 829]

A321 with HF018c now is o.k. for me.

[Lenair 9]

LSZH: RWY16, Conf2, 72.000t

HEGN: RWY34, Conf3, 73.300t

[Max Reverse 344]

Same here. I just finnished my testflight in LSZH and can confirm what "---" writes. And I am not a Pro just a small single piston jockey.

I had 500 kg less T/O weight, but the same results. There is no chance for TOGA LK

[Lolo75020 0]

Hello,

Same pb for me as well :

I think I found where is the bug :

Dubai (OMDB)

A321: 46.9t/25.0%

Fuel: 3.1t

TOW:50.0t

Speed: 124/134/137

Flex:No (TOGA)

Flaps:2

Accordingt to FMS, F speed is 131kt, but just after rotation VLS= 145 !! and Vstall=140 kt with a weight of 50.0 t, it is non sense !

So of course when i take off with a heavy aircraft (more than 84,0t), the VLS become higher than the VFE and the A-floor mode is triggered, the speed scale is red every where.

So very interesting now :

I did the same departure with the same parameters, every thing the same... except the flight plan :

and then everything is ok:

VLS= 110kt

V stall= 101 kt

In my first example I have inserted a long flight plan:

OMDB/LFPG:

OMDB (0.0nm) -SID-> NADIL (32.2nm) -M557-> NABOP (44.6nm) -M557->
OBRID (68.6nm) -M557-> EMAGO (78.5nm) -M557-> VUVOK (104.9nm) -M557->
TUMAK (123.4nm) -M557-> VEDOM (149.3nm) -M557-> VELAK (176.0nm) -M557->
ALTOM (197.6nm) -M600-> DASOS (203.3nm) -M600-> ALMOK (214.8nm) -M600->
VEDOS (251.0nm) -M600-> MEMKO (266.4nm) -M600-> RAKAK (283.8nm) -M600->
RAMSI (303.7nm) -UL602-> MUNTI (348.2nm) -UL602-> LOVAK (360.4nm) -UL602->
IVONI (373.2nm) -UL602-> DAVUS (401.2nm) -UL602-> BOXIK (430.7nm) -UL602->
RALKA (476.5nm) -UL602-> TASMI (517.1nm) -UL602-> GADSI (567.1nm) -UL602->
ALPET (626.3nm) -UL602-> ITBIT (681.3nm) -UM860-> ULIMA (711.0nm) -UM860->
LONOR (736.4nm) -UM860-> SEPTU (775.0nm) -UM860-> ITOVA (782.2nm) -UM860->
PUTSI (794.9nm) -UM860-> TAGRU (857.6nm) -UM860-> UMESA (909.7nm) -UM860->
SEVKU (962.2nm) -UM860-> EMIDO (1006.4nm) -UM860-> KABAN (1037.9nm) -UT334->
ESOTA (1090.1nm) -UT334-> ULSAB (1127.8nm) -UT334-> EKMIN (1142.2nm) -UT334->
ASPUL (1169.6nm) -UT334-> UMLEN (1180.9nm) -UT334-> NULRU (1213.7nm) -UT334->
ETESU (1230.3nm) -UT334-> ELNEM (1295.5nm) -UT334-> UTURI (1308.0nm) -UT334->
ASVOD (1330.3nm) -UT334-> ERVAK (1376.9nm) -UT334-> ORVOR (1433.1nm) -UT334->
UVULU (1494.7nm) -UT334-> INB (1538.3nm) -UL852-> UDROS (1684.2nm) -L746->
NUVDI (1837.6nm) -UL746-> BALBI (1931.3nm) -UM747-> ENIMA (1969.0nm) -UM747->
NERDI (2021.6nm) -UM747-> AGNEP (2054.0nm) -UM747-> NEKUL (2070.2nm) -UM859->
MOPUG (2157.9nm) -UM859-> EBORO (2189.9nm) -UM859-> MAVIR (2197.1nm) -UM859->
SOGMO (2286.5nm) -UM859-> NIKAB (2292.2nm) -UM859-> DIMLO (2338.7nm) -UT23->
NIDLO (2357.7nm) -UT23-> GRZ (2381.9nm) -UM19-> OBEDI (2471.3nm) -UM19->
ARTUS (2515.5nm) -UM19-> ERKIR (2526.4nm) -UL608-> KOGOL (2551.6nm) -UL608->
KPT (2594.7nm) -UQ163-> LUPOL (2628.1nm) -Z714-> PELOG (2637.5nm) -UM164->
UTABA (2646.2nm) -UM164-> LUPEN (2716.0nm) -UM164-> OBORN (2737.2nm) -UM164->
POGOL (2757.8nm) -UM164-> OBAKI (2768.5nm) -UM164-> EPL (2783.6nm) -STAR->
LFPG (2928.9nm)

In my second example, just a basic airfield pattern: OMDB/OMDB

Notice that this bug appeared only twith V18c, not V18b.

And when I want to reload my flight by using in FSX menu Flights/Reset, I have a message error I never had befor V18c

"

RUNTIME ERROR

Program: C:\Program Files...

R6031

- Attempt to initialize the CRT more than once.

This indicates a bug in your application

"

HAve a good day

[Lolo75020 0]

I found very shame as well :

• the aircraft could take off so easily to high level with heavy weigh, as it is not possible in real life. (however the time to reach a normal flight level is correct). For instance, if you take off at 89.0t (A321), you can reach F380 with no problem. The green dot is moving according to the weight, but not the VLS/Vstall, this is shame. At high altitude VLS is very close to green dot. With this weight the A321 can hardly reach FL330.
• I would be happy to have a REC MAX altitude as well. I think it is not too much difficult to code as the green dot speed is already coded according to weight and FL.

[nakis03 3]

Hello

I agree with you

There is a bug with a long routes

Decrease a lot SRS speeds So the ALPHA FLOOR and then TOGALOCK is the result

If you look ONLY FOR LONG ROUTE FOR example LGAV-EGLL the take off speeds and then look FLIGH PLAN PAGE the speed near INTCPT will more less than V2 so the mystery is solved dear AEROSOFT

Regards

Same pb for me as well :

I think I found where is the bug :

Dubai (OMDB)

A321: 46.9t/25.0%

Fuel: 3.1t

TOW:50.0t

Speed: 124/134/137

Flex:No (TOGA)

Flaps:2

Accordingt to FMS, F speed is 131kt, but just after rotation VLS= 145 !! and Vstall=140 kt with a weight of 50.0 t, it is non sense !

So of course when i take off with a heavy aircraft (more than 84,0t), the VLS become higher than the VFE and the A-floor mode is triggered, the speed scale is red every where.

So very interesting now :

I did the same departure with the same parameters, every thing the same... except the flight plan :

and then everything is ok:

VLS= 110kt

V stall= 101 kt

In my first example I have inserted a long flight plan:

OMDB/LFPG:

OMDB (0.0nm) -SID-> NADIL (32.2nm) -M557-> NABOP (44.6nm) -M557-> OBRID (68.6nm) -M557-> EMAGO (78.5nm) -M557-> VUVOK (104.9nm) -M557-> TUMAK (123.4nm) -M557-> VEDOM (149.3nm) -M557-> VELAK (176.0nm) -M557-> ALTOM (197.6nm) -M600-> DASOS (203.3nm) -M600-> ALMOK (214.8nm) -M600-> VEDOS (251.0nm) -M600-> MEMKO (266.4nm) -M600-> RAKAK (283.8nm) -M600-> RAMSI (303.7nm) -UL602-> MUNTI (348.2nm) -UL602-> LOVAK (360.4nm) -UL602-> IVONI (373.2nm) -UL602-> DAVUS (401.2nm) -UL602-> BOXIK (430.7nm) -UL602-> RALKA (476.5nm) -UL602-> TASMI (517.1nm) -UL602-> GADSI (567.1nm) -UL602-> ALPET (626.3nm) -UL602-> ITBIT (681.3nm) -UM860-> ULIMA (711.0nm) -UM860-> LONOR (736.4nm) -UM860-> SEPTU (775.0nm) -UM860-> ITOVA (782.2nm) -UM860-> PUTSI (794.9nm) -UM860-> TAGRU (857.6nm) -UM860-> UMESA (909.7nm) -UM860-> SEVKU (962.2nm) -UM860-> EMIDO (1006.4nm) -UM860-> KABAN (1037.9nm) -UT334-> ESOTA (1090.1nm) -UT334-> ULSAB (1127.8nm) -UT334-> EKMIN (1142.2nm) -UT334-> ASPUL (1169.6nm) -UT334-> UMLEN (1180.9nm) -UT334-> NULRU (1213.7nm) -UT334-> ETESU (1230.3nm) -UT334-> ELNEM (1295.5nm) -UT334-> UTURI (1308.0nm) -UT334-> ASVOD (1330.3nm) -UT334-> ERVAK (1376.9nm) -UT334-> ORVOR (1433.1nm) -UT334-> UVULU (1494.7nm) -UT334-> INB (1538.3nm) -UL852-> UDROS (1684.2nm) -L746-> NUVDI (1837.6nm) -UL746-> BALBI (1931.3nm) -UM747-> ENIMA (1969.0nm) -UM747-> NERDI (2021.6nm) -UM747-> AGNEP (2054.0nm) -UM747-> NEKUL (2070.2nm) -UM859-> MOPUG (2157.9nm) -UM859-> EBORO (2189.9nm) -UM859-> MAVIR (2197.1nm) -UM859-> SOGMO (2286.5nm) -UM859-> NIKAB (2292.2nm) -UM859-> DIMLO (2338.7nm) -UT23-> NIDLO (2357.7nm) -UT23-> GRZ (2381.9nm) -UM19-> OBEDI (2471.3nm) -UM19-> ARTUS (2515.5nm) -UM19-> ERKIR (2526.4nm) -UL608-> KOGOL (2551.6nm) -UL608-> KPT (2594.7nm) -UQ163-> LUPOL (2628.1nm) -Z714-> PELOG (2637.5nm) -UM164-> UTABA (2646.2nm) -UM164-> LUPEN (2716.0nm) -UM164-> OBORN (2737.2nm) -UM164-> POGOL (2757.8nm) -UM164-> OBAKI (2768.5nm) -UM164-> EPL (2783.6nm) -STAR-> LFPG (2928.9nm)

In my second example, just a basic airfield pattern: OMDB/OMDB

Notice that this bug appeared only twith V18c, not V18b.

And when I want to reload my flight by using in FSX menu Flights/Reset, I have a message error I never had befor V18c

"

RUNTIME ERROR

Program: C:\Program Files...

R6031

- Attempt to initialize the CRT more than once.

This indicates a bug in your application

"

HAve a good day

[nakis03 3]

Dear AEROSOFT and everybody

TRY to flly from LGAV-EGLL for test flight .... PLEASE AEROSOFT do my favorite...))

Regards

[Cheyenne Chief Pilot 829]

Is this a long-route bug or a high-weight bug?

I tried with short routes, but high T/O weights and couldn't reproduce the issue, neither in the A320 nor in the A321.

Does that mean those V2 and F speeds change independently of weight, but with the change to longer routes?

[nakis03 3]

the only way i i have found is to reset IRS from overhead and after seconds the speeds are normal please try it... 3 IRS OFF from over head and then ON and realingn irs

[nakis03 3]

TRY to clear one way point from fligh plan and dont programm your arrival star in your fmgs .

Your speeds after that will be normal ...afer take off you can fix your flight plan .... i havent fount other way to fix this bug temporarily ... i hope from Aerosoft in the future ti check the long routes ..

[Lenair 9]

TRY to clear one way point from fligh plan and dont programm your arrival star in your fmgs .

Your speeds after that will be normal ...afer take off you can fix your flight plan .... i havent fount other way to fix this bug temporarily ... i hope from Aerosoft in the future ti check the long routes ..

Tryed that, no alpha floor but afterwards when i want to put the star in the FMGS (inflight) i got a CTD. Beautiful... I hope that it will be fixed asap, it's anoying.

[Emi 5161]

Tryed that, no alpha floor but afterwards when i want to put the star in the FMGS (inflight) i got a CTD. Beautiful... I hope that it will be fixed asap, it's anoying.

Please open a seperate thread for the CTD and make sure to explain when exactly it happens and also post the Event Log.

[Chris0410 3]

After having installed the 1.16 with latest Hotfix I flew the tutorial flight of the documentation (EDDF to LOWW) to make sure not to miss something and.... everything went fine.

Had a nice flight without any Toga LK.