Post by Markoz on Jan 4th, 2014 at 2:18am
I'm curious about which Transition you used for ILS34R? I chose ILS34R.SONDR to go with HAWKZ3.BTG because SONDR was the last waypoint for HAWKS3.BTG and it is also the first waypoint for the approach to ILS34R:
This meant there was no need to use VECTORS to capture the ILS/GS (or to use VECTORS to reach the first waypoint of the approach on ILS34R (which are CIDUG or SONDR):
Did you remove some waypoints from the STAR or APPROACH? Personally, I would probably wanted to remove the waypoints ARVAD and FOURT as well as VECTORS, so that my route was direct from LACEE to SONDR, which would mean there was no need to backtrack away from KSEA to be able to reach the TRANSITION waypoints of ILS34R.
Note: Failure to select the approach transition, means your route ends at the last waypoint of the STAR (VECTORS in this case).
[timestamp=1388810939] - I flew your route using IL34R.SONDR as my approach. After passing FOURT, I turned right to a heading of 185o, and flew that heading, while descending to, and holding 6000 feet (the SONDR altitude constraint of /6000A) until I was about 2nm beyond being parallel to SONDR, then I turned towards it. Once I was heading directly towards SONDR, I copied it into the scratchpad, then pasted it into LSK1L (CDU LEGS Page) and pressed EXEC. I then turned LNAV back on. After passing SONDR, I then descended to 5000 feet, and once I reached NEAL, I pressed the APP button. I immediately captured both the ILS and GS and continued on to land in the centre of runway ILS34R. It never deviated from the path. Straight in and right in the centre!
I forgot to answer the following questions. So here they are:
Quote:
Not when I captur the ILS and GS, but once the LAND3 lights up, all three AP CMD buttons activate (illuminate).
Quote:
I always use the centre (C) CMD button when flying the 767 (or 757) - It's just my preference. It should not matter whether you are using the left (L), centre (C) or right (R) CMD button to control the AP!
Quote:
No! Once the ILS Localizer is captured, the MCP should automatically set the heading to the ILS Localizer heading (343o in this case).
Hope this helps.
This meant there was no need to use VECTORS to capture the ILS/GS (or to use VECTORS to reach the first waypoint of the approach on ILS34R (which are CIDUG or SONDR):
Did you remove some waypoints from the STAR or APPROACH? Personally, I would probably wanted to remove the waypoints ARVAD and FOURT as well as VECTORS, so that my route was direct from LACEE to SONDR, which would mean there was no need to backtrack away from KSEA to be able to reach the TRANSITION waypoints of ILS34R.
Note: Failure to select the approach transition, means your route ends at the last waypoint of the STAR (VECTORS in this case).
[timestamp=1388810939] - I flew your route using IL34R.SONDR as my approach. After passing FOURT, I turned right to a heading of 185o, and flew that heading, while descending to, and holding 6000 feet (the SONDR altitude constraint of /6000A) until I was about 2nm beyond being parallel to SONDR, then I turned towards it. Once I was heading directly towards SONDR, I copied it into the scratchpad, then pasted it into LSK1L (CDU LEGS Page) and pressed EXEC. I then turned LNAV back on. After passing SONDR, I then descended to 5000 feet, and once I reached NEAL, I pressed the APP button. I immediately captured both the ILS and GS and continued on to land in the centre of runway ILS34R. It never deviated from the path. Straight in and right in the centre!
I forgot to answer the following questions. So here they are:
Quote:
| Do all three A/Pīs lit (engage) when you "catch" the GS and Localizer? |
Quote:
| In my case only the left one (L) lits as it does during the flight. |
Quote:
| Do I have to dial the CRS (343 in this case) in the HDG of the MCP? |
Hope this helps.