Engaging the autopilot for an ILS approach??
-
Love this aircraft and have figured out how to add ILS approach. I understand why there is no RNAV obviously. So, Im curious what is the procedure to activate the ILS approach. I programmed with the ILS frequency into the the NAV 1 and put it in manual mode not auto. When i was at the correct ILS frequency altitude I activated APPR mode on the AP. However, the plane just flew past the glide slope and the plane did not pick up the GS and had to fly it in manually. Thanks again.
-
Check in the CDU if your nav source was VOR1 or FMS.
I'm not sure if it is the right procedure but what I do is:Close to the ILS I sync the heading and switch to heading mode in an intercept course to the localizer. Then in the CDU I switch nav source to VOR1, I check if I have the right frequency and course. Then I press APP, loc is captured almost immediately if you are close enough and then the glideslope is captured.
Hope it helps.
And please anybody correct me if the procedure is wrong. -
Actually, I was reading the real star ship manual and it seems you can in fact fly RNAV approaches with it. It seems like sort of a challenge though as the FMS waypoint sequencing has to be, or will put it self in manual. As to whether this is legal today, I'm not sure.
-
Check in the CDU if your nav source was VOR1 or FMS.
I'm not sure if it is the right procedure but what I do is:Close to the ILS I sync the heading and switch to heading mode in an intercept course to the localizer. Then in the CDU I switch nav source to VOR1, I check if I have the right frequency and course. Then I press APP, loc is captured almost immediately if you are close enough and then the glideslope is captured.
Hope it helps.
And please anybody correct me if the procedure is wrong.@lrargerich said in Engaging the autopilot for an ILS approach??:
Check in the CDU if your nav source was VOR1 or FMS.
I'm not sure if it is the right procedure but what I do is:Close to the ILS I sync the heading and switch to heading mode in an intercept course to the localizer. Then in the CDU I switch nav source to VOR1, I check if I have the right frequency and course. Then I press APP, loc is captured almost immediately if you are close enough and then the glideslope is captured.
Hope it helps.
And please anybody correct me if the procedure is wrong.interesting okay. Ill try and give that a shot. Thank you
-
Actually, I was reading the real star ship manual and it seems you can in fact fly RNAV approaches with it. It seems like sort of a challenge though as the FMS waypoint sequencing has to be, or will put it self in manual. As to whether this is legal today, I'm not sure.
@Sunake said in Engaging the autopilot for an ILS approach??:
Actually, I was reading the real star ship manual and it seems you can in fact fly RNAV approaches with it. It seems like sort of a challenge though as the FMS waypoint sequencing has to be, or will put it self in manual. As to whether this is legal today, I'm not sure.
Really? I thought the Starship does not have RNAV or GPS reading capabilities? Would love to know how lol
-
This is one of the biggest misconceptions I have seen posted all over the place this week.
Starship was originally produced without GPS; however, it had onboard systems for position estimation that allowed it to fly "RNAV" procedures, back when these would have otherwise been flown with something like the KNS-80 in my other aircraft.
Since then, all Starships have been outfitted with GPS, and many other updates to their avionics. The current owners also keep their aircraft updated with current navigation and approach data. This makes today's Starship flying experience very similar to any other light aircraft with GPS and an FMS. You can load RNAV procedures and fly to any intersection in the database. The only limitations are...
- No automatic loading of SIDS/STARS (you can still enter all waypoints)
- No entry of airways by name (you can still enter all waypoints)
- No holds or procedure turns
- No vertical guidance on approach
I hope that clears things up, but I also must add one caveat. I have gathered from recent interactions that European pilots may have a slightly different connotation to the the word "RNAV" than we do in the US. If that is the source of the confusion, then perhaps the only solution is for me to embed with the RAF for a few months and then come back. Always happy to answer your excellent questions!
-
This is one of the biggest misconceptions I have seen posted all over the place this week.
Starship was originally produced without GPS; however, it had onboard systems for position estimation that allowed it to fly "RNAV" procedures, back when these would have otherwise been flown with something like the KNS-80 in my other aircraft.
Since then, all Starships have been outfitted with GPS, and many other updates to their avionics. The current owners also keep their aircraft updated with current navigation and approach data. This makes today's Starship flying experience very similar to any other light aircraft with GPS and an FMS. You can load RNAV procedures and fly to any intersection in the database. The only limitations are...
- No automatic loading of SIDS/STARS (you can still enter all waypoints)
- No entry of airways by name (you can still enter all waypoints)
- No holds or procedure turns
- No vertical guidance on approach
I hope that clears things up, but I also must add one caveat. I have gathered from recent interactions that European pilots may have a slightly different connotation to the the word "RNAV" than we do in the US. If that is the source of the confusion, then perhaps the only solution is for me to embed with the RAF for a few months and then come back. Always happy to answer your excellent questions!
@Black-Square said in Engaging the autopilot for an ILS approach??:
Since then, all Starships have been outfitted with GPS, and many other updates to their avionics. The current owners also keep their aircraft updated with current navigation and approach data. This makes today's Starship flying experience very similar to any other light aircraft with GPS and an FMS. You can load RNAV procedures and fly to any intersection in the database. The only limitations are...
- No automatic loading of SIDS/STARS (you can still enter all waypoints)
- No entry of airways by name (you can still enter all waypoints)
Better clarification- are you saying current owners have installed a GPS unit such as 430s or 650s or how are they loading RNAV procedures?
Second question- you CAN enter the waypoints for the SIDs/STARs but from what I can tell is this isn't a legal solution as the SID/STAR must be line-selectable from a database.
I'm going to open a new topic on this re: Simbrief
-
-
This is the other misconception I have seen a lot. The GNS 430 is only there for reference and convenience in the real aircraft, and is not connected to the autopilot. However, I asked the owner who maintains the fleet, and he said that the type of autopilot coupling that I implemented was very possible. For the "onboard" GPS capability, the aircraft have a Collins LRN-85 "Long Range Navigation System" LRU (From the best I can tell. I didn't lay eyes on it myself). You can monitor the status of this GPS from the "LRN STATUS" screen of the CDU.
-
I can only speak to this in the FAA world, but yes, databases are required for these procedures since something like 2005. I can ask one of the owners what equipment code they file with. My guess would be /L (RVSM+GNSS) with "NO SID/STAR" in the remarks. We're already introducing VATSIM controllers to the ICAO code "STAR", so might as well hit them with the "NO SID/STAR" and /L or /Z too!
I will be curious if you learn anything definitive from the Simbrief community. Let me know.
-
-
For sure. I'm a VATSIM controller and threw this at a couple more controllers with more knowledge than I and we all agree, that it can be /Z since it does have RNAV capability, but if you cannot select SIDs/STARs its best to file as a /W and that will "register" for the controllers moreso for VOR/VOR navigation in terms of that will prevent inadvertent STARs placement, but the /Z with a note suffices as well I suppose
-
Thanks for sharing. I was thinking the same way when my real world aviation brain kicked in and asking what a controller would "expect" from each code, rather than what might be the most technically correct.
-
This is super interesting. Just so i understand there is no vertical guidance from the AP when the Plane catches the ILS glide slope correct? So bad weather flying or almost no visibility landings when runway is no where in sight its best not to fly in these conditions with the Starship?
-
This is super interesting. Just so i understand there is no vertical guidance from the AP when the Plane catches the ILS glide slope correct? So bad weather flying or almost no visibility landings when runway is no where in sight its best not to fly in these conditions with the Starship?
@jwilson0514 I believe that is not correct. The glideslope on the ILS does work. There is not vertical guidance for an RNAV approach.
Brian
https://www.flyaka.com
Alaska Adventures -
@jwilson0514 I believe that is not correct. The glideslope on the ILS does work. There is not vertical guidance for an RNAV approach.
@dadgametime This is correct. Your choices for vertical guidance are ILS, or the coupled GNS.
-
320 Sim Pilot has an ILS approach with GS in the last portion of this video:
https://youtu.be/z_r2WFCm2WI
-
320 Sim Pilot has an ILS approach with GS in the last portion of this video:
https://youtu.be/z_r2WFCm2WI
@Marionettework said in Engaging the autopilot for an ILS approach??:
320 Sim Pilot has an ILS approach with GS in the last portion of this video:
https://youtu.be/z_r2WFCm2WI
Perfect thank you
