OnCourse Software

drumsart wrote: *

Thu May 18, 2017 4:15 am

Hi,

During approach to EDDW the center let me to 4000ft until the localizer is intercepted (frankly above the glide) !

I was forced to descend to VS 2000ft to catch the glide

Attached the logs.

Thank you and Regards,

Edit : I just found out that I had set previously there are some weeks (forgot that) the minimum FAF alt at EDDW to 19000ft !
So, maybe it's the problem. Thank you to confirm that or not.

Quote:

During approach to EDDW the center let me to 4000ft until the localizer is intercepted (frankly above the glide) !

vololiberista wrote: *

Thu May 18, 2017 9:19 am

drumsart wrote: *

Thu May 18, 2017 4:15 am

Hi,

During approach to EDDW the center let me to 4000ft until the localizer is intercepted (frankly above the glide) !

I was forced to descend to VS 2000ft to catch the glide

Attached the logs.

Thank you and Regards,

Edit : I just found out that I had set previously there are some weeks (forgot that) the minimum FAF alt at EDDW to 19000ft !
So, maybe it's the problem. Thank you to confirm that or not.

Quote:

During approach to EDDW the center let me to 4000ft until the localizer is intercepted (frankly above the glide) !

Your fpl cruise altitude was already 4,000ft!! you should have used the DENEN 2P approach which is also at 4,000ft and the FAF is 3,000ft. Also LBE has been renamed to LBV so you need to update that.
an alternative and more correct fpl would be RENSU LBV WSR GIBMA BMN
I strongly recommend that your cruise altitude be set higher say FL100 or FL120 Descend to be at 4,000ft by GIBMA.
Descend to be at BMN at 3,000ft. It is a hold. So in your wpt altitude page fix the altitude of BMN at 3,000ft and mark it as a hold. From there you fly either to ROGBO or BANIX to intercept the localiser depending on the rwy in use. Not forgetting to set your FAF to 3,000ft. So you actually fly to directly above the airport and then at a tangent to intercept the relevant localiser.

The fpl is similar to LSGG to LIPO in that there is a wypt directly over the airport. This can sometimes cause confusion. So you should have two alternative fpls that end in either ROGBO or BANIX. It's a short flight so the weather won't change much. Just make sure that the wind is not across the rwy as that confuses tha AI as well.

drumsart wrote: *

Fri May 19, 2017 4:24 am

vololiberista wrote: *

Thu May 18, 2017 9:19 am

drumsart wrote: *

Thu May 18, 2017 4:15 am

Hi,

During approach to EDDW the center let me to 4000ft until the localizer is intercepted (frankly above the glide) !

I was forced to descend to VS 2000ft to catch the glide

Attached the logs.

Thank you and Regards,

Edit : I just found out that I had set previously there are some weeks (forgot that) the minimum FAF alt at EDDW to 19000ft !
So, maybe it's the problem. Thank you to confirm that or not.

Quote:

During approach to EDDW the center let me to 4000ft until the localizer is intercepted (frankly above the glide) !

Your fpl cruise altitude was already 4,000ft!! you should have used the DENEN 2P approach which is also at 4,000ft and the FAF is 3,000ft. Also LBE has been renamed to LBV so you need to update that.
an alternative and more correct fpl would be RENSU LBV WSR GIBMA BMN
I strongly recommend that your cruise altitude be set higher say FL100 or FL120 Descend to be at 4,000ft by GIBMA.
Descend to be at BMN at 3,000ft. It is a hold. So in your wpt altitude page fix the altitude of BMN at 3,000ft and mark it as a hold. From there you fly either to ROGBO or BANIX to intercept the localiser depending on the rwy in use. Not forgetting to set your FAF to 3,000ft. So you actually fly to directly above the airport and then at a tangent to intercept the relevant localiser.

The fpl is similar to LSGG to LIPO in that there is a wypt directly over the airport. This can sometimes cause confusion. So you should have two alternative fpls that end in either ROGBO or BANIX. It's a short flight so the weather won't change much. Just make sure that the wind is not across the rwy as that confuses tha AI as well.

Thank you for your answer. I'm aware about you wrote, LBV is in the GTN750. For the rest my flight was without approach procedure, I wanted just a vector approach by PF3.

My question/confirmation related to my post edited was"Edit : I just found out that I had set a few weeks or months ago (forgot that) the minimum FAF alt at EDDW to 19000ft!
So, maybe it's the problem. Thank you to confirm that or not."

Anyway, I have my answer. Before I made the flight again, I corrected/canceled the minimum FAF alt at EDDW in the PF3 Sid/Star menu. This time the final approach altitude was 2000ft (I have the FAF altitude by default in the advanced options and INI File Tweaks menu put to 2000ft). So, it was a glitch of myself

Regards,

drumsart wrote: *

Fri May 19, 2017 2:52 pm

Except that my problem was related to the fact that the center had not ordered me to go down during the final approach and left me at 4000ft.

The reason it happened was not given by your answer . No disrespect, the answer was interesting but irrelevant to my question. That was the meaning of my previous answer. Btw I know I do need to look at the charts except when I decide to do just one quick flight for in this case tested the new Mce (very promising)...!

Thank you and Regards,

Quote:

My question/confirmation related to my post edited was"Edit : I just found out that I had set a few weeks or months ago (forgot that) the minimum FAF alt at EDDW to 19000ft!
So, maybe it's the problem. Thank you to confirm that or not."

RALF9636 wrote: *

Sat May 20, 2017 9:53 am

Quote:

My question/confirmation related to my post edited was"Edit : I just found out that I had set a few weeks or months ago (forgot that) the minimum FAF alt at EDDW to 19000ft!
So, maybe it's the problem. Thank you to confirm that or not."

Yes, that most probably caused your initial problem.

If you want to set the FAF for each airport depends on how accurate or realistic you want it to be.
For me the default general setting is good enough in most cases.

I even use the SimRandomizer to have a slightly different default FAF altitude and FAF distance every flight.