I had a flight on the weekend where I also had fuel shortage. I didn’t use SimBrief, but based on distance and the range shown in MSFS, I should have had plenty of fuel with 50% load with plenty of fuel to spare after landing. I was still testing out the SF50 and wanted to try a nice, high altitude flight, so I picked this particular familiar route.
I was travelling in an east southeast direction. I’ve done this flight many times in various planes, and always had a tail / crosswind normally, and typically nowhere near this strong. Not this time. I ended up with a 125kt headwind most of the flight, slowing me drastically and increasing fuel requirement for the flight significantly. I started getting low fuel warnings about 20 mins before arrival. When I landed, I had 6 gallons left in each tank. If this would have been IRL, I can guarantee the pucker factor would have been strong enough that my hemorrhoids would have been tickling my tonsils.
So yes, there are many factors that can affect fuel endurance, and wind is definitely a HUGE one to take into effect. And SimBrief will take that into consideration when doing its calculations.
I sent an AFM compliant Little Nav Map performance file that Albar (Alex) validated before uploading to the LNM Performance Page. It includes an NBAA reserve calculated - not just a divert number, but actual finesse stuff like time in hold, etc. So the real max range of the jet by NBAA numbers is closer to 1,099NM and just a shade under 3:40:00 endurance with no wind.
There’s a conversation about LRC in the Discord Support Channel if anyone wants to peruse it. One of our owner/operators provided an N table for distance missions.
Totally depends on what your weight is, what your speed is and what altitude you are trying to reach. If you are at max weight, don’t imagine you’re going to be able to reach 31,000 feet easily. BTW, cruise altitude for the SF50 is 25,000 feet.
I probably did something wrong. It was my first time using AT.
I had set the FLC speed at Vx and altitude to 15,500 on the ground. I think I turned on AP around 1000 feet and then hit the AT FMS.
That’s about where I noticed I was leveling off as I was approaching cruise speed. I was still climbing but at 150-200 fpm. FLC was somewhere around current cruise speed.
When I tried to adjust the FLC back to Vx the FLC speed automatically reset back. It was in a limited high speed range.
Once I turned the AT off I was able to dial in Vx.
Yeah, I need to spend some time coming up with a solid sequence of events after takeoff. I.e. TOGA first to get it at 5 degrees climb and LVL wings, HDG or NAV as appropriate, FLC maybe to 165 KIAS and then turn on A/T, or A/T first, etc.
Would love to hear other’s thoughts on what works best for them.
Personally I think the MSFS gust model is extremely aggressive - it isn’t representative of the real world
Edit - this is a good pilots discussion on some of the issues.
My own view from what I’ve experienced so far is that large variations have been enabled at too high a frequency and up to higher FLs than you’d expect. I also think that I’d expect something like that from a model that hasn’t been statistically optimised or tuned. I’m sure it could be improved but we’ll have to wait or put up - I guess it’s possible (devs would know) to tune aircraft sensitivity but in my view that would then cause problems with a retuned gust or turbulence model…
So what I do is after 400’ (the latest patch will enforce this), Autopilot is available. I hit AP which should put you in ROL PIT with YD already on after 200’. If I’m not already on path, enable NAV to start tracking the flight path. I manage the throttle manually at this point to stay under 250kts or whatever that leg might require.
Once I’m stabilized laterally, enable AT and visually verify it selected AT FMS (status light on the throttle console). It should set SPEED and start to accelerate to 250 kts. I usually have dialed in initial step altitude when I got clearance on the ground. Then I hit FLC and it automatically switches to CLIMB and 165.
I don’t remember where I read it, but I think they are aware of the excessive gusts in the sim at the moment. It will be addressed. Sry, can’t provide a source.
Developers are not allowed to give support on this forum per the forum rules (unless that has changed with the reorg, I’m going to assume it hasn’t). I don’t know why, maybe to protect those developers who don’t like to support their products.
I’ve probably already gushed about this plane too much on this thread and elsewhere, but I’ve put another five hours or so on it and it’s really perfect for the way I use the sim (sightseeing mostly, an hour or so per flight).
It’s fast enough to cover ground (1 hour flight gives me more than a 400-500 km radius), but slow enough to sightsee and hand fly comfortably. If I’m flying along and I see someone in multiplayer I want to chase around, I can easily go down to their speed no matter what they’re flying (almost). And when I’m hand flying the handling is predictable and sweet. Sounds are great, too.
The visibility is top notch.
Modern avionics allow me to have as much or as little workload as I want in any given situation. The auto throttle is a stand out feature, for someone who has flown exclusively GA planes in the sim. An added bonus: The map will tell me what cities I’m flying over so I don’t have to keep checking google maps on my phone and guessing (I’m on XBOX). The avionics also allow for easy and relaxing night flying which is only helped by the great exterior and interior lighting. Pressurization means I can play pretend airliner without having to study a huge manual.
It’s all the goodness of GA flying plus many of the benefits of a jet wrapped in an easy to use and satisfying package. What a deal for $25.
Because when vendors and customers disagree (and many times vehemently) we end up having to step in, and then one or both sides get penalized. That’s unnecessary work for a volunteer Staff. Additionally, there are legal and regulatory impacts to allowing vendors who are not MS employees to conduct business on MS property and systems. One is practical, the other operational. Both good reasons not to conduct Tech Support here.