F100 - ATS and Landing behaviour
-
Had a vAPP of 121kn today and I didn't manage to perform a stable approach.
Aircraft accelerated to 160kn and even higher as you can see on this screenshot (wasn't able to record a video quickly enough):
@OELVA Second this. I had erratic speed changes up to 160kts, all the way from 121kts which was selected.
-
I would like to chip in here with my modest observation - this might be an issue occurring only on MSFS 2024, imho.
I flew F100 in MSFS 2024, LOWW-EPKK, the turbulence settings set to low and nearly no wind, the plane climbed in profile mode, was unable to follow FMS selected IAS. Oscillations were always +/- 20 kts. The throttle was stable in climb thrust, but the plane was unable to follow the FD properly and was overshooting the selected speed until a cruise altitude was reached.
I flew F100 in MSFS 2020, the same route, the same conditions, the plane kept the speed in profile climb without any issues (tiny variations due to the wind, absolutely normal).
I also flew F70, only in MSFS2020 on LOWW-LZKZ-LOWW, different cruise altitudes and speeds, always flown accurately. Did not fly F70 in MSFS2024.
The ATS is sometimes slightly sluggish, but as Mark says, that is to be expected, and I did not find the ATS behaviour in MSFS 2020 particularly problematic (would say that 737s by a famous developer have a similarly sluggish auto throttle).
Could it be the difference between simulators?
@MichailusB
Can anyone else who uses MSFS 2020 confirm this? I use MSFS 2024 and the plane can't maintain speed on climb ( even on descent in LVL change mode it oscillates a lot ). If this is a case of only in MSFS 2024 issue then it needs to be investigated. -
Hi all!
I had huge problems flying the f100/f70 in real weather. Approach speeds fluctuating wildly and incontrollable aircraft. But, I found a solution in the internet which seems to work on my pc. It’s a windows problem (!). The OS clock synchronization, didn’t work well (but check also DNS and IPv6). It caused MSFS2024 to mess up winds, particularly during last 500 feet AGL of the approach.
The link is here:
https://forums.flightsimulator.com/t/extreme-crosswinds-and-wind-swings-close-to-the-ground-on-final/728054Many thanks to paulofranca89!
-
Do these issues still persist?
According to the change log for v1.2 the trim issue should be sorted out.
However, I cannot find anything regarding the ATS-hunting issues.These reports regarding the ATS-inaccuracies prevent me from purchasing the F70/100.
Best regards
-
In the few flights I did with V1.2, I haven't paid attention specifically to the out-of-trim state when disconnecting the A/P on the ILS, but I haven't had the impression that it still exists.
Aircraft feels in trim when you disconnect the AP.
ATS is still an issue for me.On my last flight so far, I've selected IAS250 and LVLCH in descend. From what I've read on the manual, throttles should go back to idle and the aircraft maintains 250 IAS just by vertical speed just like your average Boeing or Airbus. What happened was the aircraft going into a >4000ft/m steep descend while being at 270IAS and further accelerating by down pitch, while, for my understanding, the aircraft should have pitched up to reduce speed until the set 250 IAS in FLCH mode is reached and not going even faster by pitching down.
On reddit, someone told me that's a normal behaviour in a TOGA condition... I've even provided a screenshot showing the aircraft in CLB and IASE modes. -
Thank you.
Does this apply to MSFS 2020, MSFS 2024 or both of them?
-
Hi all!
I had huge problems flying the f100/f70 in real weather. Approach speeds fluctuating wildly and incontrollable aircraft. But, I found a solution in the internet which seems to work on my pc. It’s a windows problem (!). The OS clock synchronization, didn’t work well (but check also DNS and IPv6). It caused MSFS2024 to mess up winds, particularly during last 500 feet AGL of the approach.
The link is here:
https://forums.flightsimulator.com/t/extreme-crosswinds-and-wind-swings-close-to-the-ground-on-final/728054Many thanks to paulofranca89!
@venemair I experienced a combination of the poor ATS response, but more notably the crosswind issue just before landing using historic weather (Active Sky) on approach to 28L at EIDW. On first attempt I went around as was certainly not a stable approach. On 2nd attempt exactly the same issue, but carried on to land (not pretty) as was out of time for the evening!
Because I was using ActiveSky for the weather injection I don't think this can be the system clock issue, but might be a corrupt weather file? As regards the ATS, I had this disengaged for the final approach, but find I keep fighting it as it turns itself on to protect speed. TBF, I think I was in the amber, but how do you tell the computer that it's within parameters for the approach? The correct flap setting was set with an approach speed of 141Kts which I was maintaining, so not really sure what I'm getting wrong if anything...
I have done some good landings in the Fokker 100 (in fact some my best), but it does seem very inconsistent.
-
@Gisbourne just tried in real wx to land in a F100 at EIDW 28R, winds 020/20. ATS on until touchdown. Vapp (fmc) + 5 due to xwind. At 500’ I noticed ground effect and turbulence, but nothing too bad. Auto pilot off at 400’ needed some trim up but the result: a normal, reasonably soft landing. ATS did it fine. I do not have AS. Also did good landings today at EGGD and LFMN with xwind in CB. All with ATS on until touchdown, but a/p off. Turbulence realistic, real wx. I know how frustrating is can be. My confidence is slowly coming back regarding the fokkers of justflight.
