RED

Wenn du erst im "finalen Anflug" auf on speed gehst und vorher schon trimmst, aber noch schneller fliegst, dann musst du drücken. Das wird sich auch nicht ändern. Bei der Break ist es am besten nach den ersten 90 Grad bei 250kn zu sein. Mehr G und/oder Bremse raus helfen. Bevor du die 180 startest: Landecheckliste abgehackt und definitiv On Speed.

Unterrichtseinheit mit Schmirco? :smilewink: Klappen raus muss nicht bei jedem Muster eine steigende Nase bedeuten. Wer da mit der FA-18 kämpft -> unter 250 kn Klappen voll raus, Fahrwerk raus (dirty) -> Throttle zurück, 1-2s bevor auf on speed verlangsamt Throttle wieder vor für 90-100% RPM Wer kann, trimmt dabei auf On speed 8.1 AOA. ->Danach Nase mit Schub steuern, mit Stick+Trimmung die 8.1 AOA halten. Wem die Nase wegsteigt, gibt egal bei welcher Geschwindigkeit zu viel Schub in Relation zu seiner Stick+Trim Position. Half Flaps werden nur benutzt, wenn ein Triebwerk ausfällt oder der Wind am Träger sehr stark ist.

+1

You may want to upload the track file. Maybe there is a bug.

I also don't get why you would use the pitch trim. Saying you should fly the real deal with no helpers is also not helpful unless the person has an extended and precise stick. It helps to have some experience in formation flight. Learning to stay in the observation area first and then refueling is probably more effektive than to start with refueling first.

Did you turn the radar altimeter on? Turn the little knob on the radar altimeter right and set a minimum altitude. If you do you initially get the low altitude alert sound.

Jain, anscheinend wurde der Sensor am Fahrwerk vorne verändert. Mehr bremsen, dann geht's. Was nicht mehr geht sind RB75 im Nav modus. Man macht nen Wegpunkt Update anstatt den suchkopf zu bedienen. Attack Modus geht. Kann aber auch ein Bedienfehler von mir sein.

+1 and also add functions that are currently only available in SP like rocket ripple/single(18) as well as all the functions that need to be changed through the kneeboard like the laser code for GBU-12s(F5). The performance data for the specific load out would be handy, too (T/O distance, asymmetric trim for launch,...)

After shooting all 9X missiles the symbol goes back to "0 9M" and not "0 9X".

+1 Alp, still great missions! Had a lot of fun in the Viggen and Albatros :thumbup:

Beim starten von der Piste, Carrier? Oder einfach im Flug? Fahrwerk oben?

Wahrscheinlich ein Bug. Am besten speicherst du den track und machst einen Bug report, wenn es immer noch nicht geht.

As windy said - it's all about knowing if your are in a 1C or 2C fight. For 2C keep it between 350 and 450, for 1C pull until below 200 kn and then keep it between 20-22 alpha. That worked for me. An EM- diagram would be nice and there is always Tacview to generate our own numbers. My advice: keep the tally and listen to the alpha. If you keep the tally and have the speed in the right ballpark, the fight is half won.

Auf "Meine Bestellungen" Bonus Points zu Wird im deutschen nicht so ganz klar, was gemeint ist.

Nein. https://forums.eagle.ru/showpost.php?p=3585169&postcount=1

You can choose to not allow that as a mission designer at least for the mirage. Razbam is one step ahead. ED planes don't give you this option.

The radar is stabilized. If you point your nose up, that does not mean that the radar looks up. It will try to stay at the angle off the horizontal you set it to. In this picture you can see a vertical line next to a zero on the right side: I 0 this gives you a visual representation where the radar is looking. The number shows how many meters above or below your current altitude your are pointing the radar. Combined with the number at the bottom of the HUD you can search a specific point in space. The horizontal line at the bottom also shows if the radar is looking straight, left or right. As mvgas said, the best thing you can do is post a track. I also recommend doing the BI(T)test before every flight:

Discussing the problem: Seems like the model of the Co-Pilot doesn't disappear correctly.

Thank you very much. Is there any Angle of Attack given for minimum turn radius? I only understand the units given for the charts but not the explanations... :helpsmilie:

May you link the manual?

Genau das hatte ich auch schon. Per Paddle ausgeschaltet, dann war noch Attitude Hold drin, obwohl ich Baro aktiviert hatte. Per UFC ausschalten geht immer. Wenn du willst, probier mal aus, ob sich Attitude Hold ähnlich verhält.

:smilewink::helpsmilie: Ok, then that got lost in translation :doh: But that doesn't change that I see no discrepancy. The picture of P-816 shows CASE II. My focus is on how you fly it and not how it is defined. How I see it: CASE II: Leave Marshal, correct and intercept BRC before 12 nm. CASE III: same with FB. CV-1 ->No turn at 10 nm or intercepting the BRC after 10 nm for CASE II.

... :music_whistling:

May you show where this is described in P-816 or said anywhere else. I can not find anything like that. I also cannot find this. I don't see a discrepancy between the 2 documents. Maybe you read something i overlooked. My point of view: The pilots are interested where the marshal radial is. That's briefed and given to them as a radial and not relative to sth. They then need to take that info and figure out how much they need to correct to get on the BRC for CASE II and on the FB for CASE III during their approach. What i read - P816: CASE II: 2-19 ->ideally->You do have to make a correction. 2-21 No FB give to the pilots, only BRC CASE III: 2-23 ->CV1 ->FB.

That's CASE II. The approach course is the direction you need for landing (CASE II -> BRC for the Initial; CASE III-> CV1 with FB). The Marshal is relative to that course.