Textron Beechcraft G58 Baron Stall Speed

Bug Reporting Hub Aircraft & Systems
, ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue: Since SU7 native Textron Beechcraft G58 Baron stall airspeed seems to be way too high at around 110 knots, making it almost uncontrollable immediately after take off and particularly so at final approach to landing. I understand this was an issue before and SU6 fixed it but SU7 seems to have broken it again.

Could affect other native, or all, aircraft and possibly related to the reported drag issues associated with SU7 although those seem to be more of a high speed on descent problem.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

Every time since SU7

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Take off at 90 - 100 knots. Flaps 1st stop.

  2. Try and maintain control at best angle or rate of climb 92 or 105 kn. You must race to over 110 kn quickly or wing will drop.

  3. Try to approach threshold at 95-100 kn, without stalling. Flaps 1st stop or full. Have to land at 110-120 kn which is far too fast.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it? No, none.

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use? RTX3080 10GB

[PC Only] What other relevant PC specs can you share? i9-10900K CPU @3.7GHz 64GB RAM

MEDIA

Please add a screenshot or video of the issue occurring.

2

Agreed, the stall warning is very pitch trigger happy, operating a speed way before its actual stalling speed. I play on PS5 with HOTAS 5 and it is very sensitive to pitch with control sensitivity set really low, the nose pitches up and down, oscillating, more than other similar types to a pitch input.

When starting an approach, it is off putting to have the stall warning constantly going, a banner pops up in free flight saying ‘approach speed too fast, set 75kts’ which is also not correct because stall speed is higher than that.

I tried several approach speed stalls, level flight, autopilot height hold and heading hold on, and reduced power gradually, with no oscillations due to the autopilot operating, stall warning started bleating at 98, actual stall occurred at 78kts clean, flaps up

Repeated with 15 flap, full flap, then gear down full flap, stall warning operated much higher than actual stall. Actual stall speeds seem logical. In fact with autopilot in, it was reluctant to stall with flaps down, I had to disengage the altitude hold to raise the nose sufficiently to get a stall.

I found it too difficult to do the excercise accurately with autopilot off due to the oscillations in pitch, causing stall warning to operate at 110 and over. The AOA seemed higher than expected at slow speed.

As the OP says, after T/O at speeds well over 120 kts, the stall warning operates with unexpected high AOA, but I think this is probably due to the rate of pitch oscillation. It seems wrong, but I find this Beechcraft to be difficult to control smoothly in pitch. It seems erratic on trim setting as well, set the trim to hold a speed, then shortly afterwards, it needs a retrim. Not a pleasant thing to play with.

3

My problem was actual stall and loss of control at what should have been normal approach speeds, and before any stall warning kicked in. However this seems much better after Service Update 7.1, though I haven’t tested it much since then. Fingers crossed that it’s been corrected.

Likewise my Baron is pretty sensitive on the controls but I leave sensitivities at default (limited brain power!). Sorry to hear about your too early stall warning. I’m on PC rather than PS5 so maybe the two systems create different anomalies, but don’t know enough to suggest anything. I never had any trouble with the Baron in 2020 and considered bringing that version across to 2024, until SU7.1, hopefully, seemed to solve my problem. Best of luck with yours.

4

I only started in August but I think the PS5 hasn’t got enough computer power for some of the requirements of MSFS. It’s ok when the autopilot is on, doing typical straight and level IFR stuff, but start on helicopters and GA where it’s manual flying and it gets unstable. About 50% of the missions I do in helicopters where it involves hoist or load or something requiring lots of small control inputs result in a game crash. But a couple of the basic MSFS 2024 aircraft suffer from odd behaviour, this Beechcraft is certainly one of them! I did what should be a straight forward mission, A-B, autopilot in, like a dream, watch the countryside go past, but landing at a small strip, total chaos, stall warning beeping all the time, out of trim no matter what I did. Got it on the ground eventually, restarted the mission a couple of times because of huge sink rate on short final with no noticeable wind, stall warning on for the entire approach, it’s very off putting, totally unrealistic behaviour. The game for me is beating the oddities of the game!