Well flown and well redeemed! Most of your confusion comes from changing nav sources. In FMS mode (purple needles on the HSI) the aircraft will navigate via your FMS flightplan. In LOC1/LOC2 (green needles on the HSI) it will navigate based off signals from the NAV1/NAV2 radios. You can change it with the 'nav source' button, top left of the left most touch screen. When you activated vectors to final it kicked you into LOC1 mode so all your subsequent FMS commands weren't followed which caused the issue. I'd say if you got to grips with how the nav sources work and also how to interpret the FMA (what the autopilot is doing) 95% of your issues would be solved. Happy to jump on a discord call for your next SF50 flight to be on hand if you need a pointer. Keep it up 💪
Thank you so much, and very kind of you. I'll shout if the Discord would be useful, but I think what you've put here anyway will help immensely! One question - if I'm adding the Procedure in, as I did, would it have tried to navigate me straight to the initial approach fix immediately if I'd pressed Load & Activate? Was Load (only) the correct call at that point?
@@trislanderadventures7831 that's exactly right. Load will add the procedure onto your existing flight plan in sequence at the end. Load and activate will load the approach and send you direct to the inital approach fix. Once you're on a localiser intercept heading you can change the nav source (or activate 'vectors to final') and arm the approach mode if you like then. The autopilot should intercept the localiser and decend with the glideslope when it comes in. (This is for ILS approaches. RNP approaches use FMS guidance so the procedure is slightly different).
I believe from memory in the SF50 it will switch automatically from FMS to LOC1 once captured. You shouldn’t need to manually change the OBS source manually.
Your landing lights are meant to pulse like that. There are a few business type aircraft that have that function 🤓 It’s great when you start feeling more and more comfortable with an aircraft type - I’ve been recently clocking hours in the Maddog MD-82. It’s been a rewarding VATSIM challenge, for sure! 😅 Still very much enjoying the content - keep ‘em coming!
To avoid the take off trim warning, you want to set your trim to the green band, it's just to the right of the gear indicators, should be set to about 6 degrees if I remember correctly.
I would also advise while you’re in the STAR prior to Approach enabling the speed bug references so you have your minimums marked on your speed indicators. Also you can set the decision height in the minimums so it announces for your decision point as well as marking it on the PFD altitude display
More hints! I'm at 16:01 right now, and I noticed you had vnav on, and then turned on vs. It would have been easier to just leave it in vnav, and let the plane do what it wants. if you notice, it starts the decent before you put on vs mode. What you want to be looking at in the mode annunciator is when you change selected altitude, you'll first have "v path" in white and get the purple guidance arrow on your altitude tape, you just want to make sure that that one stays centered as the ap does its thing, because that means you're on the calculated decent path. Once that purple arrow is in the center, it should have "vpath" in green, showing that that's the active mode, and it will start the decent. And with autothrottle on in fms mode, it should follow speed constraints as well.
Another tip I’ve not seen mentioned: on your PFD the AP modes in green are active and the AP modes in white are armed, ready to activate. You ought to be able to leave VNAV enabled the entire way. You then use FLC to make changes to your altitude rather than VS. If you need to intercept a GS or a VNAV PATH from above or below you can use FLC to pass in to it. Same applies to HDG vs NAV for horizontal movement, if you press HDG to insert a vector and that vector intercepts a NAV path then it will switch to NAV on interception if you haven’t disabled NAV.
Well flown and well redeemed! Most of your confusion comes from changing nav sources. In FMS mode (purple needles on the HSI) the aircraft will navigate via your FMS flightplan. In LOC1/LOC2 (green needles on the HSI) it will navigate based off signals from the NAV1/NAV2 radios. You can change it with the 'nav source' button, top left of the left most touch screen.
When you activated vectors to final it kicked you into LOC1 mode so all your subsequent FMS commands weren't followed which caused the issue.
I'd say if you got to grips with how the nav sources work and also how to interpret the FMA (what the autopilot is doing) 95% of your issues would be solved. Happy to jump on a discord call for your next SF50 flight to be on hand if you need a pointer. Keep it up 💪
Thank you so much, and very kind of you. I'll shout if the Discord would be useful, but I think what you've put here anyway will help immensely! One question - if I'm adding the Procedure in, as I did, would it have tried to navigate me straight to the initial approach fix immediately if I'd pressed Load & Activate? Was Load (only) the correct call at that point?
@@trislanderadventures7831 that's exactly right. Load will add the procedure onto your existing flight plan in sequence at the end. Load and activate will load the approach and send you direct to the inital approach fix. Once you're on a localiser intercept heading you can change the nav source (or activate 'vectors to final') and arm the approach mode if you like then. The autopilot should intercept the localiser and decend with the glideslope when it comes in.
(This is for ILS approaches. RNP approaches use FMS guidance so the procedure is slightly different).
Thank you so much!!! @@fpt9694
I believe from memory in the SF50 it will switch automatically from FMS to LOC1 once captured. You shouldn’t need to manually change the OBS source manually.
Your landing lights are meant to pulse like that. There are a few business type aircraft that have that function 🤓
It’s great when you start feeling more and more comfortable with an aircraft type - I’ve been recently clocking hours in the Maddog MD-82. It’s been a rewarding VATSIM challenge, for sure! 😅
Still very much enjoying the content - keep ‘em coming!
Thank you! So is the trigger for them being in a steady state the fact the gear is down?
@@trislanderadventures7831 I believe so. Worth a little pop out the cockpit to see if they modelled that 😁
To avoid the take off trim warning, you want to set your trim to the green band, it's just to the right of the gear indicators, should be set to about 6 degrees if I remember correctly.
Amazing, thanks!
I would also advise while you’re in the STAR prior to Approach enabling the speed bug references so you have your minimums marked on your speed indicators. Also you can set the decision height in the minimums so it announces for your decision point as well as marking it on the PFD altitude display
Thanks, Simon, for all these extra useful tips. I've just come down with a bug, hence I'll look at them properly in a few days' time
More hints! I'm at 16:01 right now, and I noticed you had vnav on, and then turned on vs. It would have been easier to just leave it in vnav, and let the plane do what it wants. if you notice, it starts the decent before you put on vs mode. What you want to be looking at in the mode annunciator is when you change selected altitude, you'll first have "v path" in white and get the purple guidance arrow on your altitude tape, you just want to make sure that that one stays centered as the ap does its thing, because that means you're on the calculated decent path. Once that purple arrow is in the center, it should have "vpath" in green, showing that that's the active mode, and it will start the decent. And with autothrottle on in fms mode, it should follow speed constraints as well.
And the reason vs came off at 21:28 was because you ahd intercepted the vpath, so the plane went back to doing its calculated decent.
Thank you!
Watching your videos and finding myself in the background a lot haha (I was the Loganair) good to see you last night
Excellent! The ATR? :)
Yes, it is nice to fly but takes a little bit of getting used to
Another tip I’ve not seen mentioned: on your PFD the AP modes in green are active and the AP modes in white are armed, ready to activate. You ought to be able to leave VNAV enabled the entire way. You then use FLC to make changes to your altitude rather than VS. If you need to intercept a GS or a VNAV PATH from above or below you can use FLC to pass in to it.
Same applies to HDG vs NAV for horizontal movement, if you press HDG to insert a vector and that vector intercepts a NAV path then it will switch to NAV on interception if you haven’t disabled NAV.
The landing light behaviour incorrect: th-cam.com/video/O7WwEcMFaps/w-d-xo.htmlsi=3YEE1KY9ry-GRYbp&t=1626