Recent posts

#1

Hangar 7 / Re: AT and FD behaviour with t...

Last post by Hardy Heinlin - Wed, 7 Jun 2023 12:19

AT HOLD mode goes to THR REF and ref at this point is GA.

Sorry, I don't understand this sentence. What exactly happened?

#2

Hangar 7 / Re: AT and FD behaviour with t...

Last post by osss - Wed, 7 Jun 2023 12:00

HOLD engaging THR REF with landing flap? That would be entertaining! - but I can't see why it would happen, I will try it out - but I'm not scheduled in sim until later this month..
Peter

Did you try this? The whole discussion switched to another topic. Meanwhile I do remember this special feature:

We flew our visuals at Lufthansa Flight Training center.

Instructor: If you use AT during takeoff do not forget to disconnect AT somewhere before base. Because it will surprise you when turning final you extend flaps past 20. AT HOLD mode goes to THR REF and ref at this point is GA.

We: yes!

Then both of us forgot about it at least twice.

#3

Hangar 7 / Touchscreen behaviour on "pres...

Last post by Kurt - Tue, 6 Jun 2023 21:10

Hi.

My PSX setup is based on 3 PSX instances stretched over 7 pcs of touch monitors (plus scenery via FS2020 now on one 65" tv but very soon on 3x65" inch TV´s ) and I am after a long time of use now used to use the "double tap" gesture to make continuous turns of rotaries and other interactions like starting the APU etc - BUT to have the optimal immersion it would be optimal if we did not need to do the double tap but instead just "press and hold" to turn the rotaries and do similar continuous actions in the PSX cockpit. (I have disabled "press and hold" to "mouse right click" already in Win 11)

I searched the forum and google for hints on how to do this but no success so far - maybe some registry hack needed - wonder if anyone in the forum have solved this?

Thanks in advance

Kurt

#4

Tutorials / Re: PSX Layouts: An Annotated ...

Last post by evertdb - Tue, 6 Jun 2023 20:46

This is a great help!!  THX Will!

#5

Accessories / Re: Aeromap 0.1.2 - Detailed m...

Last post by vnangli - Tue, 6 Jun 2023 14:39

One more impressed user...@will had already asked my question regarding the North being UP and not the Heading being UP....Nevertheless, this addon has made me even more happier..Thank you

#6

Hangar 7 / Re: KORD - RWY 10L (LOCalizer ...

Last post by vnangli - Tue, 6 Jun 2023 14:23

Why HDG SEL?

Wanted to check if LOCalizer would go active at BURKE, if I were to intercept at a larger angle.

This is what I was doing till I ran into this question.
1) Flight from KSDF to KORD.
2) STAR - WYNDE TWO arrival
3) After crossing POSSM, I had chosen HDG SEL (to replace Vectors) to intercept RWY 10L Approach at or before ARIST
4) Engage LNAV at around ARIST
5) After crossing ARIST, I would arm LOC. Thats when I would notice LOC not active till PRATT

After understanding from your response, I was going to switch from LNAV to HDG SEL (approximately 007 deg) at around POSSM to intercept BURKE and arm LOC to and see if Localizer would go ACTIVE without waiting to reach PRATT.

I wish I could share the situation file. I am at work and couldnt resist replying to the post :-)

#7

Hangar 7 / Re: KORD - RWY 10L (LOCalizer ...

Last post by Hardy Heinlin - Tue, 6 Jun 2023 14:03

Why HDG SEL? Why do you want to leave the STAR? You're not supposed to capture the ILS that early.

The STAR is not wrong. That slight offset is intentional. Just follow it with LNAV.

#8

Hangar 7 / Re: KORD - RWY 10L (LOCalizer ...

Last post by vnangli - Tue, 6 Jun 2023 13:46

...on this LNAV route via BURKE on 093° the intercept angle is just 1°...

Thank you...

I will try with HDG SEL and intercept the APPROACH at BURKE with a larger angle. Will report back.

Used AEROMAP for the first time, it is a good addon. Thanks to the Developer.

#9

Hangar 7 / Re: KORD - RWY 10L (LOCalizer ...

Last post by Hardy Heinlin - Tue, 6 Jun 2023 06:47

Just tested it. It's like I wrote in my previous comment.

Only at 12 nm the LOC diamond is close enough to the center for a capture. It would capture earlier if you were on a greater intercept angle. But on this LNAV route via BURKE on 093° the intercept angle is just 1°, so the LOC diamond will move very slowly. At that point the diamond is off-center by almost half a dot. After CARLE the route track changes to 094°.

I would say this is all normal. You don't want to track the 094° localizer while your STAR still instructs a 093° track to CARLE.

There may be rounding errors in the track numbers on the LEGS page due to locally differing magnetic variation, but the true-north track on the ND map shows the truth: There you can see the difference between the runway heading (white dashed line) and the LNAV route (magenta). There's a tiny little difference.

#10

Hangar 7 / Re: KORD - RWY 10L (LOCalizer ...

Last post by Hardy Heinlin - Tue, 6 Jun 2023 06:20

A situ file that shows the problem is always the best basis for a discussion.


As far as I recall, the LOC capture condition is not just "deviation from center" but also deviation rate. I.e. when the LOC diamond is close to the center but moving very slowly, it may be not close enough for a capture yet. Otherwise, an early capture at a low closure rate would cause the aircraft to make an undesired S-turn instead of a smooth intercept.