RandallR

I did most of my RW flying in the 70's so even the idea of a home flight simulator didn't exist. It's also the reason I love simming so much - as I get to continue "flying" past my time of affordability and also safety due to my age. Also, I love that I get to practice more advanced techniques, learn about modern instrumentation (absolutely amazing what the systems of even smaller aircraft are capable of today). Now, when I went through training there was certainly no issue with over-dependence on the instruments (as I had no previous experience). Visual cues outside of the aircraft were used first followed by the "instrument scan". You can do a lot with the visual cues (cowling above and below the horizon for instance) but no - flying by "feel" only takes you so far (and can also be deadly). Unless I was flying under the hood, my main quick instrument checks were with the airspeed indicator and the turn and bank indicator (quick reference for coordination), and (of course) the altimeter.

Question to the OP - have you run Navigraph recently or Navigraph hub? They've made several updates over the last few weeks - make certain they're up-to-date. Also, there was a recent update to Simbrief itself a few days ago. When I ran Simbrief directly one day (not within FS) there was an update and I was forced to login with my Navigraph account. Since then, everything's been normal within the sim, though I haven't imported the FP directly from Simbrief into the g5000 for a while.

Love the aircraft and fly it often, though I haven't accessed Simbrief through the aircraft recently (that approach used to work just fine so I'm not sure how it's functioning now). I've been simply downloading the Simbrief plan into Navigraph, adding the anticipated approach there, then exporting that to FS2020. When I access that file in the FS2020 planner, then go to fly the flight plan is in place. If you (or others) continue to have a problem importing the Simbrief plan directly into the g5000, post what's happening and I'll give it a go this weekend.

Annoying is certainly correct. Now, if a future rendition of these systems, such as the g5000, had active TAWS options, being able to inhibit warnings under certain terrain conditions would be very helpful.

OK - I can verify that none of this works. The TAWS page in the FS2020 rendition of the g5000 is not operational. The work by WT is really wonderful on this unit and TAWS is certainly "running", considering the TAWS announce at start-up and the plethora of call-outs. However, the TAWS menu is greyed out on the MFD control and cannot be accessed.

Thanks! I'll check this out before my next flight with the Longitude.

When I looked through all of the options after the flight (yes, this is a TAWS system) - I couldn't find a way to just inhibit it. When I did a search, the common work-around appeared to be changing the minimum altitude for terrain warnings. If someone has located a quick way to inhibit the warning I'd love to hear the procedure.

I guess I'll adjust the altitude warning ranges in the MFD? Maybe set the bottom at 20'? I want terrain warnings to work normally when not flying in mountainous terrain, but this will mean changing this setting every time there are high-altitude approaches.

As a former pilot I appreciate the modern systems of warnings that aid pilots in many situations, and I certainly understand warnings for terrain, etc. The Longitude is one of my favorite aircraft and its systems are remarkable. However, I can certainly do without the continuous Terrain! Terrain! shout-outs and Pull Up! Pull Up! Pull Up! exclamations and warning horns when I'm exactly at the appropriate altitudes for my approach (Ecuadorian mountains). The approach is being properly read by the g5000 system and my altitudes are correct, so why all of the kerfuffle? The particular approach I was on today does place me occasionally within 2,000' of the surface in some sections, but that's exactly what it's supposed to do. Is the actual g5000 system this stupid or does it require the pilot to reset warning altitudes in real life when making this type of approach in order to not have their concentration constantly interrupted?

No update here...

In that case I would remove the Longitude entirely and close FS2020. Then, restart the sim and add the aircraft back in, basically reinstalling the aircraft.

Glad to hear it. The TBM would be the g3000 (g5000 in the Longitude) I would guess there is a Longitude livery or other add-on creating your issue.

I would start with an empty Community folder first. The only time I ever had any aircraft literally missing parts was with incompatible liveries or mods. Regardless, there should be no mods in the Community folder for the TBM, CJ4 or Longitude, as all updates from WT are now part of FS2020 and the TBM mods were nullified by MS/ASOBO updates quite a while ago.

The great mod work of Working Title on the CJ4 was incorporated into FS2020 - it is the default. It has also been reported that the FS2024 default version is excellent, so it appears to have been carried over.

For SimBrief, I still use this CJ4 SimBrief Profile from when WT was modding the aircraft in FS2020. It still works well for me (in FS2020). You may want to try it?