Samhaho

This doesn't work for me

There is a button on the left side of the yoke that is supposed to control electric rudder trimming and elevator trimming. When I hover with the mouse on this button a left/right wheel arrows and a hand-finger appear. However I get no effect at all when I click or when I turn the mous wheel. Any idea what is the problem? Note 1: I can trim by binding a joystick/axis to the trimming function, but my question is specifically about the physical button on the yoke Note 2: The switch trim on the overhead panel is on

Hello, Thank you for releasing an update so quickly The access to this page was denied for me. Anything else I can do on my side? Sam

Thank you again Dave, this is very helpful. Now how to get The Planned descent rate/ground speed from the point where the initial vector is provide to the IAF?

Thank you Dave for the clarification. However I am still confused, in case of a vector assigned by ATC (P2ATC) who is responsible of managing the descent profile (clear the terrain), me (pilot) or ATC (P2ATC) ? The couple of times when vector was assigned instead of STAR I did not receive precise instructions for managing the descent profile and have missed barely (thanks to nice weather) crashing into the mountains! Sam

I understand (but I may be well wrong) that having ATC assign STAR and Approaches during the flight is closer to reality than forcing them (via the Config button), therefore this what I do in general. The question is if there is any way during the flight to request to ATC (P2ATC) to change the assigned STAR and/or approach (such as requesting another STAR/Approach call). On the other hand I am still not sure why P2ATC decided to select vectoring instead of STAR, did I do or configure something that caused this? (I am talking here about early vectoring and not the one typical in many cases that provides transition from a STAR to a final approach). Any clarification will be very helpful. Many thanks. Sam

Here is another flight from SACO to SCEL when I was vectored very early (without STAR) to the final ILS approach. I have several problems with this: 1) I am not sure of the benefit of this (vector vs STAR) since the vector follows roughly the direct route (no optimization) however with several turns few degrees right and left. Basically it is more load without any benefit that I can perceive; 2) The major problem with early long vectoring (as opposed to a STAR) is the lack of vertical guidance (where a STAR provides such guidance). During this flight I have been cleared from FL44 to FL16 in very high mountains area. I could avoid the crash only thanks to the high visibility (a beautiful sunny along with magnifiant mountains views) and to the fact that I had already done this route (using a STAR with very precise altitude restriction so the terrain can be cleared) 3) The final vector was given too high and in a way that i could not catch the ILS Again the major issue here is to clear high mountains area which is not possible with the vectors provided by P2ATC because of the lack of precise altitude guidance. Is there anyway (specific request to ATC for exemple) to avoid vectoring in such high mountains routes? Sam

Thank you Dave. I guess the log is for the last flight, then I'll have to redo the flight to get the log. I will do this. In the meantime if you can explain in general what are the cases when vector is provided instead of a STAR this would be helpful. Sam

I was flying KMIA to MKJP. More than 100 NM before arrival at FL 37 P2ATC started vectoring me to the approach (no STAR assigned). A first question at this point: When/Why P2ATC provides vector as opposed to continuing as per the flight plan while assigning a STAR? At some point later (around 50 NM before arrival) while providing vectors to the approach P2ATC instructed me to descend and maintain five thousand feet. Unfortunately the descent profile (although reasonable) does not clear the terrain obstacles (mountains) around the island/airport that can as high as 9000 feet. This would not have occurred if a STAR were assigned and the associated altitude restrictions were met. Is this situation an issue/bug on P2ATC side or did I miss something? Sam