Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Fying RC with Baron and autopilot is wrong

Featured Replies

This may have nothing to do with RC, but I can't think what else!

I am flying the default Baron in UK (northern Scotland) - at the start of a round the world trip.

I am setting the standard pressure when RC clears me to flight level 50, 1013mb (29.92 inches).

But then the autopilot levels the plane at 4520 on the altimeter, when I obviously have the a/p set at 5000!

Naturally RC complains am not at altitude, so I have to add on 500 to the a/p to achieve FL50!

 

The other day I was flying at 4000 and then the a/p was levelling the aircraft at 3960. But then I hadn't realised I should have been at standard pressure setting.

I was still around the given airfield pressure.

 

As you can see I am wondering if RC is someway involved as it is requiring me to fly at 5000 on standard pressure.

But I didn't imagine that the a/p should consider anything other than the altimeter.

So why does it think the plane is at 5000 when the alt is showing  something else?

 

Thanks

Nigel

 

First, you are not using the FS "B" key to set altimeter pressure, are you? That is hard coded for a transition altitude of 18,000 feet valid only for FAA jurisdictional territories.

 

RC's transition altitude dabase has 3,000 feet for Inverness Airport, EGPE, in northern Scotland so it is not a marginal error.

 

When your altimeter is at standard pressure, you climb until it reads 5,000 feet for FL50. The AP should be set at that.

 

I have not used the Baron that much.

 

I also don't use shift-Z in the flight levels but either way it will show altitude with surface pressure  reference below 18,000 feet. I do not think shift-Z shows flight level altitudes anyway.

 

The Baron in F9 uses the default KING AP. Make sure the FD and AP buttons next to the instraument air gauge are enabled and the ALT button on the AP.

 

RC see the aircraft altitude via FSUIPC so make sure the full and interim versions are current from:

http://forum.simflight.com/topic/66139-updated-modules/

 

FS does not use FSUIPC regarding the default Baron so that that should not be involved in your problem.

 

Run a test flight with the Baron with just FS running and nothing else that might be interfering.

  • Author

Ronzie,

 

Thanks for your reply.

I was a bit confused by it as you mention things and then discount them as not applicable.

 

No, I am not using the B key as that would set the pressure to that given by FC ATC (RC ATC generally gives a different pressure)

I haven't used shift Z either

I will check my version of FSUIPC (I have the free version) I only installed it a couple of days ago so it should be OK. Thanks for the link.

But you say you don't think that is involved anyway.

 

I will try a simple FSX flight with the Baron - to see if the problem occurs with that.

 

Nigel

P.S. I am looking for a good GA aircraft to buy to use on my RTW trip. The Baron is OK, but I would like a fully functional model.

I have the A2A C172, but that's not got the range I need. The Flight One Super King Air looks great, but is bit large for my purposes.

  • Moderator

 

 


I am flying the default Baron in UK (northern Scotland) - at the start of a round the world trip.

I am setting the standard pressure when RC clears me to flight level 50, 1013mb (29.92 inches).

 

So far so good.

 

But then the autopilot levels the plane at 4520 on the altimeter, when I obviously have the a/p set at 5000!

Naturally RC complains am not at altitude, so I have to add on 500 to the a/p to achieve FL50!

That is definitely an aircraft issue and not RC.

 

The other day I was flying at 4000 and then the a/p was levelling the aircraft at 3960. But then I hadn't realised I should have been at standard pressure setting.

I was still around the given airfield pressure.

 

if you were at 4000ft then you should have been at QNH. But if you meant FL40 then yes, your altimeter should have been at 1013. Need more info about that segment of your flight. Were you instructed to descend to 4000 feet or FL40? Flight details would help here.

 

As you can see I am wondering if RC is someway involved as it is requiring me to fly at 5000 on standard pressure.

It all depends on your flight plan and what the transition altitude is for each airport. That's why I need plan details. TA is different for many UK airports but is generally 5000 or 6000ft.

 

But I didn't imagine that the a/p should consider anything other than the altimeter. So why does it think the plane is at 5000 when the alt is showing something else?

A/Ps don't know about FLs or feet. They just enact on what you dial in as I'm sure you know. Dunno. More info as requested will help.

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

  • Author

Ray,

 

Thanks. I was flying the leg EGPO - EKVG Stornoway to Vagar (Faroe Islands) actually at 5000ft

I was cleared up to "Flight Level 50" and so I assumed the pressure setting should be 1013 (and RC was quiet about any deviations so I assume I was right)

But as I say this was only after having to mess with the a/p to get it to climb the aircraft to 5000.

I am going to fly the beginning of the route again without RC just to see what happens if I set the pressure differently.

I can't imagine this is a problem with FSX - it has to be something I am misunderstanding

 

Nigel

  • Author

OK I have flown the beginning of that same route.

 

I think the problem is in the G1000

After I take off and climb to 5000 using the autopilot. If I adjust the pressure setting on the G1000 nothing changes except the altitude indication - the aircraft doesn't climb or descend and the autopilot doesn't change. Just the altitude on the G1000 rises or falls.

If I adjust the pressure on the standby altimeter the aircraft does climb or descend and the altitude changes on the stand by as well as the G1000, but the baro doesn't follow.

 

So it looks like the baro setting on the G1000 isn't doing anything - unless I have got something completely wrong here!

 

As a side issue

When I change the pressure setting on the standby, whilst the aircraft climbs or descends presumably by the autopilot, the autopilot doesn't show any fps (only if I turn the Alt button off and then on)!

 

I flew this in the Baron and the Mooney (with G1000) with the same results.

 

Nigel

It sounds like the AP needs refreshing to activate your altimeter change by turning off the AP and turning it on again or better just the ALT button.

 

Now, once you get a change to or from FL if you are already climbing or descending, is the pressure immediately recognized? It is safe to enter the new pressure once you receive the ATC command to the new altitude. In fact, as far as RC goes, unless you are very close to a checkpoint, we recommend you do not ack an altitude change until the aircraft starts its climb or descent due to RC's impatient controllers.

 

For what it is worth, on the the B737/738 Smiths FMC, if you are not in a climb or descent mode, you have to activate an alt change button for it to be recognized. Does the G1000 have anything similar?

  • Author

No there is nothing that I can see on the G1000 for that.

As I say it seems that the altimeter display on the G1000 is not the one the that a/p reads it seems it only read the stand-by altimeter.

I flew another leg in my RTW trip and just set the pressure on the standby altimeter and that seemed to work.

But it's annoying that the G1000 display infront of me is not working.

 

I am surprised that this hasn't been flagged up before

 

Thanks

Nigel

I grabbed the POM for a 2008 manual covering the Baron 50/G50.:

 

http://static.garmincdn.com/pumac/G1000:BeechcraftBaron58_G58_PilotsGuide_0508.13Non-WAASor0857.05WAAS_.pdf

 

"ALT UNIT Displays softkeys for setting the altimeter and BARO settings to metric units
METERS When enabled, displays altimeter in meters
IN Press to display the BARO setting as inches of mercury
HPA Press to display the BARO setting as hectopacals
STD BARO Sets barometric pressure to 29.92 in Hg (1013 hPa if metric units are selected)"

 

If you set the STD BARO on, does the AP act accordingly?

 

See indexed pages 19 and 20.

 

Is there a switch that selects which altimeter to use for the AP? The real Garmin has several fault paths for backup.

 

Does the default G1000 (is there one?) have these? Is this an add-on G1000? Is it a WAAS capable unit with VNAV?

 

I'd ask on the FSX forum for greater exposure.

  • Author

Ronzie,

 

Thanks for that and the further link.

I don't think the G1000, as modelled in the Baron (and other default a/c), has that amount of functionality.

There is no Std Baro soft key showing.

I will try this on the FSX forum, as you say it is not related to RC anymore.

 

Thanks

Nigel

  • 2 weeks later...
  • Author

Just as a postscript to this thread.

I bought and switched over to the RealAir Duke and everything is wonderful.

The plane flies very nicely and all the controls, so far as I know, are doing everything they should!

It is a joy to fly, but I'm still learning.

 

Nigel

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.