Starship

SimBrief has performance built-in. Even takeoff performance. Which I have checked is spot on!

Hello, I had the same on the TFDi MD-11. And I believe that if the aircraft is coded a certain way using MSFS's icing model and loading, you will notice the ice weight on your payload manager. On the MD-11 you will see the extra weight on the FMC's payload page as a higher gross weight than the sum of your airplane weight and fuel weight. This one I am not sure about. All I can think of is that maybe your intakes were clogged with and ice/or your inertial separators were closed. Leading to engines being chocked for air.

Odd Couple 2026 [image: e53157f9-35b0-49d6-adc3-e78ff561a0cc.png]

@SadBucket I think the option (and I'm a great believer in options!) to simply remove by tablet is great for those that maybe think they have a ground crew for doing those things. That actually brings up something I don't know: do biz jet pilots remove the covers and things? How deep a preflight do they do? I had a buddy who flew in east Africa for the Red Cross for years and he told me about the flying but never once mentioned doing a preflight. I drove school bus for 30 years and my stories never mention the 10 minutes doing the pretrip inspection that we all had to do every morning. @Black-Square I guess I'm missing something when setting the park brake - I'll try that ASAP. edit: Got it!! A small possible wrinkle would be having to be within a certain radius of a removable element; it would lend more credence to walking around doing the preflight. Why be able to reach 20' to remove a cover? Okay, we can't jump up on the wing (can we?!) to remove the intake covers so there has to be a compromise. Have a great day. Bob

That workaround seems to work for me. Thank you for the suggestion.

Yeah I have them both off to avoid random crashes. But it still happened. Did another flight today and all was good.

I think this is the well-known MSFS24 problem with turbulence settings in conjunction with terrain and real weather (wind changes of 30kts or more in less than a second, perhaps poorly simulated windshear-stuff or updrafts/downdrafts). There is also some discussion about this in the MSFS forums. I experienced this myself last week in Nuuk (BGGH, RWY22). For several hours (under real weather conditions), there was a repeatable effect where ANY aircraft would simply drop like a stone about 200 meters before touchdown because all lift was completely gone in a fraction of a second. This could only be fixed with turbulence set to medium or low. I suppose, because Starship's front wing stalls first, the aircraft goes hard nose down.

@Black-Square Thanks! I figured it was something along the lines of access to the api for the actual weather. Shame that Asobo/their weather provider dont have an api for that.

Amazing!! Thank you for sharing. You know these are my favorite stories, and I consider each one to be a testimonial. This is exactly why I put so much effort into my systems. No system stands alone, and no failure is a single point. As we've learned from watching Mayday, Seconds From Disaster, and alike, "Disasters don't just happen, they're a chain of critical events." Thank again for sharing, and thanks for enjoying Starship the way she was meant to be

@Black-Square Thanks again for the fast reply!

Thank you for clarifying that mention in the manual. I really didn't notice that detail!

@Black-Square I get issues from time to time with the native navdata and navigraph where some addon airports delete all the navigraph procedures. I talked to Matt from working title about it and he said it's a known issue and doesn't know if it can be fixed, but in the meantime most of my Canadian payware airports do not work with the starship or working title avionics because of this... So an external system where you can download the navdata from navigraph hub like with the TDS 750 would be nice... In the meantime, probably more work than it's worth.

FLC always commands nose to level first, before raising it to capture the selected IAS. This is a bug that's been there since v1.0

No problem. Thank you anyway!