Aye the features are looking good and all but yep, twisting thumbs during a flight, specially when so high the ground is hardly visible is not my style.
Gues this is one of the reasons the JF arrows are my most flown planes, steamgauge and amazing to handfly.
And from what i have seen so far the 146 seems to suit me a lot, with how the antiice also lowers thrust and you have to adjust for that and what i really like from what i have seen too is that it is so fast to configure. Just click the plackard for the speed calculations, bam, set.
And the EFB and the way it is open to connect to SB and NaviG is just so much easier then the competition.
The 82 is on my wanted list too, it is just an icon as well, but aye not nearly as pretty and the 146 just sounds a lot better. One thing i will give the 82 is that the cockpit ambiance is amazing.
But yeah, even without taxes it is more then the 146.
I love the Warrior and Turbo Arrow. When Iām doing GA IFR (or VFR) itās always those two I come back to. The 146 for VOR NAV is what the Warrior/Arrows is to VOR NAV ie built for it, and makes you want to do it (big rotary dials and clear & functional adf/vor/ils gauges). I never switch on the GPS unit on the Warrior or Arrow, & love them both.
JF do make quality aircraft (I also have the Hawk which is stunningly rendered & fun with great liveries, but Iāve not had time to learn it yet).
The A320 NX covers most short range automated flights for me. If I hanker after a Boeing cockpit I can always switch to the Asobo 787 (which I havenāt flown for months).
A few weeks back, I asked JF (on Facebook IIRC) whether we would be able to use the tiller for nosewheel steering a la FBW A32NX. While Iām happy to report that it can indeed be assigned to that function (and works on my Logitech Extreme joystickās Z axis), I have also found what someone else reported on the JF forum: the rudder rather interferes with the tiller steering, even if you do not touch the pedals. Ie the nosewheel is constantly being pushed back to the neutral position. However Iāve now come up with a simple if not exactly elegant solution until JF might perhaps implement a decoupling like FBW are offering: when I start taxiing, I just go ESC and switch the rudder controls preset to a new one Iāve set up with just toe brakes and no steering/rudder axis. That way I can just use the tiller for direction and the pedals to slow down. Once at the takeoff hold point, I switch back to the full-function default rudder preset. Nosewheel steering is great for getting out of tight parking spaces without pushback, as the wheel casters so well, I reckon.
That doesnāt happen to me. I have rudder assigned to one axis, and NWS assigned to another, and they donāt interfere at all. When I set a particular degree of turn on the NWS, it maintains that until I centre it again.
Hmmmm, Iāll need to check again then. Maybe I did stuff up the axes. Possibly I just copied the FBW setup and that doesnāt work for the Bae with the new nosewheel function Asobo added recentlyā¦
Just for clarity and in case it makes a difference, I use a hat switch for NWS. Every time I click the switch left or right it adjusts the rate of turn by a certain amount.
(Thereās also a NWS centre function which I have mapped to a separate button on my stick - it doesnāt seem to work well with the 146 but I just donāt use it in that case, I simply reverse the NWS manually until itās back to centre.)
Think the deadzone may indeed be the answer - quite possibly I pushed ever so slightly to one side when I only wanted to be ready with the toe brake. Iāll do a bit more testing. The axes look fine to me after checking again.
Yes, itās annoying (also itās often a navigraph revalidation required, not just re-login!). Also the Simbrief login EFB thing too, it retains my pilot ID BUT the checkbox in the options that says something like āuse or remember simbrief IDā which needs to be checked for some reason always gets unchecked every flight! Both issues are similar but annoying & I hope they are both fixed at some point.
Did it yesterday. Kinda failed to flare in time, decided to take my chances anyway and rolled over the end of the runway. It was the first time in years that happened to me and I loved the aircraft for it!
Testing out the new BAe 146 today and the entire flight was wonderful until the very end during an RNAV approach with autopilot.
The plane swerved left and right and couldnāt maintain the course. The vertical path indicator was moving the wrong direction and the G/S autopilot also did not work. Anyone else gotten this to work successfully?
I didnāt think this one could do it either. I could have sworn it wasnāt supposed to have that capability when I bought it. I thought it was something that might come in a future patch, maybe when they do a proper FMC.
But yeah, a tutorial on how to do with with this version would be useful if it is supposed to be possible.
RNAV (GPS) approaches using NAV (in RNAV mode) for lateral guidance and VS for vertical guidance already works, I have done it several times with no problems. Needs to be flown to LNAV minima, not LNAV/VNAV or LPV minima. No VNAV guidance, definitely no coupled VNAV, even more definitely no GP mode, and it does not support RNAV (RNP) or GLS approaches.
RNAV approaches were not even invented when the BAa 146 was designed, it had no FMC as built, and FMC retrofits as I understand were quite basic and mainly to allow enroute navigation. I donāt know if the real thing even had the required RNAV precision to fly an RNAV (GPS) approach or even RNAV terminal procedures but luckily our sim does not know thatā¦ The later Avro RJ variants were different in that regard.
Nothing special to it, can be flown just as in real life, just select the approach in the FMC, let the autopilot fly the lateral path in NAV mode or fly manually with the flight director, and use VS for vertical control like you would for a VOR or NDB approach. Obviously need an approach chart to know the altitudes, the FMC will not provide any vertical guidance.
I find it slightly awkward since the HSI distance readout only shows the distance to the next waypoint, not the name of the next waypoint. It requires frequent checking of the FMC flight plan page to know what waypoint it is currently tracking to and maintain situational awareness. Easy to miss a waypoint passage when the waypoints are only a couple miles apart.
For that reason I would only fly an RNAV (GPS) appraoch as a last resort if no ILS, VOR, or NDB approach is available. Easier to maintain situational awareness on such approaches without the next waypoint readout.
OK, seems that if I leave the rudder alone in terms of lateral movement the nosewheel does work as expected. Rather than muck around with the deadzone, Iāll just keep my feet off the pedals until it is time to brake. A great thing about this plane is that it doesnāt get away from you at ground idle and maintains a nice steady speed during taxi. So all good!
always gets unchecked every flight! Both issues are similar but annoying & I hope they are both fixed at some point.
