Looking for feedback on my IFR and landing techinques.

[Gliptal]

 

(1080p60 available)

 

Correct ILS frequency was already set at startup.

 

0:00 - Instruments check and set up

0:30 - Calling approach

0:38 - Turn to apporach fix

0:48 - Descent to pattern altitude

1:41 - Turn to place the runway 40° fore

2:30 - Turn to intercept ILS glide slope

2:56 - Transition to landing configuration (gear, flaps, airbrakes, lights)

3:40 - Requesting permission to land (twice, ATC missed the first)

3:49 - ILS glide intercept

5:45 - The coast appears, I know I'm reaching the threshold

5:51 - Transition from IFR to visual landing

6:06 - Flare

6.14 - Full airbrakes and wheel brakes

6:47 - Flaps up

7:03 - Transition to taxi configuration

 

Some things I noticed myself:

- A bit harsh on the touchdown (I hit the right gear first because of the wind)

- I used MSL instead of AGL as reference for the 2500ft pattern altitude

- Didn't keep a constat AoA during descent

- Put the given runway bearing in the HSI without subtracting the magnetic drift

 

I don't know if I'm the only one, but flying IFR (and especially landing IFR) is really exhilarating.

 

For some reason the cursor wasn't picked up by the recording, thus it looks somewhat strange when the cockpit is clicked.

 

Any hints and feedback? Thanks!

[Joni]

It would have been much easier to select the correct heading in the course selector knob so the flight director can guide you.

 

here you have a document that shows all magnetic drift corrected course for each ILS that I integrated to Lino's file.

 

https://www.digitalcombatsimulator.com/en/files/585582/

 

the rest is good.

 

cheers.

[Gliptal]

It would have been much easier to select the correct heading in the course selector knob so the flight director can guide you.

 

here you have a document that shows all magnetic drift corrected course for each ILS that I integrated to Lino's file.

 

https://www.digitalcombatsimulator.com/en/files/585582/

 

the rest is good.

 

cheers.

Actually, I found that if STRPT is unselected from the NMSP the flight director only uses ILS datac (ignoring the course selection). The problem arises when STRPT is selected along with ILS, where the pitch bar uses ILS data and the steering bar uses HSI data.

 

I basically use it only to place the runway more or less 40° fore before intercepting.

 

Thanks for the link though!

[boomerang10]

Overall I thought it was fine; it got you on deck safely. Any corrections are minor and are just to improve an already solid approach.

 

The only things I really noticed were:

- You mention that you used MSL instead of AGL prior to the FAF. This is actually correct. Although an AGL altitude will be used to set the MSL altitude for the approach, the published altitude the pilot should be using is MSL. Think if you were trying to use AGL over mountainous terrain; you'd be chasing altitude the whole time.

 

- I thought maybe you gave up on the approach and transitioned to a completely outside scan a bit early and went past full deviation on the glideslope. Nit-picky, but personally I would've flown the needles until a bit closer and with more of the runway in sight.

 

- Fight for centerline on landing. Especially with a strong left to right wind, you don't want to be landing on the downwind side like you did.

 

Again, overall solid approach.

[Joni]

Actually, I found that if STRPT is unselected from the NMSP the flight director only uses ILS datac (ignoring the course selection). The problem arises when STRPT is selected along with ILS, where the pitch bar uses ILS data and the steering bar uses HSI data.

 

I basically use it only to place the runway more or less 40° fore before intercepting.

 

Thanks for the link though!

 

But the Flight Director will still use the course selector (known bug), that's why I pulled together the list.

[Gliptal]

Overall I thought it was fine; it got you on deck safely. Any corrections are minor and are just to improve an already solid approach.

 

The only things I really noticed were:

- You mention that you used MSL instead of AGL prior to the FAF. This is actually correct. Although an AGL altitude will be used to set the MSL altitude for the approach, the published altitude the pilot should be using is MSL. Think if you were trying to use AGL over mountainous terrain; you'd be chasing altitude the whole time.

 

- I thought maybe you gave up on the approach and transitioned to a completely outside scan a bit early and went past full deviation on the glideslope. Nit-picky, but personally I would've flown the needles until a bit closer and with more of the runway in sight.

 

- Fight for centerline on landing. Especially with a strong left to right wind, you don't want to be landing on the downwind side like you did.

 

Again, overall solid approach.

Thanks for the feedback.

 

The clarification about MSL vs AGL makes a lot of sense. Is there a document out there with the pattern altitudes of all the airports for DCSW? Until now I've heard mainly 2500ft.

[Joni]

The VAD chart on the defualt folder

[boomerang10]

One thing I forgot to mention is to use the RADALT to back you up. Set the altitude alert as appropriate, for instance set it to decision height, typically 200, for an ILS once established.

[Joni]

One thing I forgot to mention is to use the RADALT to back you up. Set the altitude alert as appropriate, for instance set it to decision height, typically 200, for an ILS once established.

 

How do you set up alert?

[Gliptal]

RDR ALT button on the UFC. Each depress cycles between AGL floor, ASL floor and ASL ceiling on the HUD; defaults are 500, 0, 0 respectively. You change the values using the DATA UFC rocker. I normally set AGL floor at zero as well during startup, because I find the warning distracting.

[=4c=Nikola]

That's a very nicely flown approach, good comments, nothing to add.