Innsbruck Circle to Land | Turbulent and gusty approach | Ultra settings P3D RTX4090 | FSLabs A319
HTML-код
- Опубликовано: 2 июн 2024
- Famous circle to land runway 08 at Innsbruck in A319, with JustSim scenery.
Not easy to do this procedure with a gusty and turbulent wind !
First video with my new RTX4090 settup.
Still working on my P3D settings to balance FPS stability, but it look like this scenery was badly optimized.
00:00 Approach
01:05 AP OFF
01:32 Downwind
04:25 Turn base
05:20 Final
06:20 Landing 
Игры
That's how pros do it. You did a very good job considering the weather. Impressive 👍🏻
Edit:- And I like how you don't crave for a butter landing and aim for only priorities, just like the real world pilots.
Thank you very much.
When I started flight simulation i was only aiming for butter landing, because people love that in videos and some people say that -300 fpm is a hard landing (spoiler alert they are wrong).
Given the fact that i always tend to practice with bad weather and short runway this behaviour of butter at all price make me done very poor/unsafe landing (landing at the end of touchdown zone or even overshooting him).
With time, i have understood that was a bad habit and now i i'm aiming -150 to -300 fpm landing and never exceeding 300' form aiming point marker (so i'm always between the aiming point and the next touchdown marker).
I'm so ashamed of this old bad habit that I deleted videos on my channel.
Safety first.
@@JaGna_ fpm is not at all a criteria which decides your touchdown smoothness. It is basically the g-value. I know you know that. You are now following the good practice. Safety first, indeed. Keep it up. All the best. 😊👍🏻
Nice approach, well done.
Pro tip (I’m a 320 pilot) what we usually do is load the visual approach into the secondary flight plan prior to the approach. It shortens how much time you need to spend on the box during the approach. Once you’re in heading mode, you can go in and activate the secondary with way less presses. Plus you can have already loaded the perf page in the secondary to save you that time too.
What you did was fine, it can just be shorter
I did it one time and it screw up all the primary flightplan, even the CF point wasn't load into the primary fpln, i was left with LOWI arrival point and wasn't able to select a new arrival.
Maybe i did something wrong on the secondary fpln but i was scared to do it again afterward x)
Fantastic approach and landing well done. Going to have to try this on my lives 😊
Good video .
Here’s a suggestion : Try avoiding giving pitch down inputs during the flare .. Also apply appropriate Pitch Up command during 10-5 ft .. that’ll help you in controlling your FPM (including your G-Load ) .. try it once
Good one! You can create more visual guidance by putting in three Fix Points.
1. OEV Radial 255, 075 Distance 4nm (Airbus didn‘t allow decimal values, the exact one would be 3.5nm)
2. RUM Radial 230
3. INN Radial 264
Don‘t overshoot the last radial INN, you where a bit too close to the mountains. The Distance Ring and the crosspoint of the INN Radial shows you the last turn, its almost above the axams church.
At least the correct STAR would be the LOC DME East approach to the circle to land.
Thank you for your interesting comment.
The LOC is not STAR, it's an instrument approach, that was following by a visual approach procedure.
Looking at the chart 19-10, special cicrcling procedure, this procedure can by following after the instrument approach 11-1, 11-2, 11-4, 12-2 et 12-21. 12-2 chart is the RNP E instrument approach, that i'm folloing. You even have MDA(h) for the visual approach (19-10) using this initial instrument procedure (12-2).
Then i was using the LOC OEV for my first training, but this scenery have wrong LOC data (using AIE i see wrong LOC course) and i was to lazy to fix it so i just followed an other instrument procedure that was allowed by the special visual procedure.
I was using some radial and radius fix info during my firsts training, resulting on poor manual flying, it's good for first training and learn for visual references but :
The ND was overload with information.
Don't forget it's a visual procedure, you have to use visual reference (as the chart 19-10 say).
They'r is no airspace restriction in the south side of the airport, so overshooting doesn't have the same consequence as overshooting in a restricted airspace, only visual reference is enough (an counter example is Queenstown NZQN that have a lot of restricted airspace around the visual circuit).
Then OEV radial 255° and radius D4 is conplitly unnecessary, once again just follow the 19-1 chart : If you use OEV LOC initial instrument approach, the 255° radial is unnecessary you are already folloing the LOC, for the radius you can simply use your PFD, LS is on, you can get the D4.2 OEV information ; If you use RNP approach the chart say "Having established external VISUAL reference (between D6.3 OEV/D4.4 OEJ and MAP) the flight shall be continued with visual reference [...]" here radius can be usefull, but you can also tune the LOC in the RAD page and turn LS on at MAP.
RUM is not use in the chart you don't need it for any fix and is unnecessary if you use D4.2 OEV fix and visual reference, plus you can see in the 11-2 chart (LOC instrument procedure) that you already passed RUM at D4.2 OEV fix.
Finaly INN Radial 264 is a good one, but this one is funny, i was "cheating" using my navigraph simlink to see my position on the chart, this scenery also have misplaced INN... And look closely the charts the visual circuit passes over the mountain cliff.
So because i was cheating... oupsi... i can say that i never overshooted 264° INN radial...
One radius that i used but you don't mention is the base leg fix (D3.5 OEV or D14.1 OEJ).
Nice views !