Pils

The button on the side of the throttles is the TO/GA button not the ATS disconnect button; you initiated a go-around. The light on the top of the fuselage being broken is a known issue and will be fixed in the next update. However, make sure you have HDR enabled for the Visual Effects setting.

That helps, thanks. But now we know that we need to know exactly what the flight plan looked like, as it sound like it crashed while determining the Lat/Lon of the intercept point.

Please provide details of exactly what was entered prior to the crash. Thanks.

100% sure the breaker at CB1-M2 is in? Maybe try cycling it out and on again.

Technically there isn’t a “checklist” for the go-around, there is a automated procedure performed by the virtual first officer. We put this in precisely because the G/A is a high workload phase, especially if attempted single pilot in the sim. The automation is there so you can concentrate on hand flying the initial stages of the G/A, which is the required procedure according to the AFM (if I recall correctly). The automation is active after the TO/GA button is pushed, and can be advanced using the same command as the actual checklists. We highly encourage its use! I believe after the procedure has been completed the next actuation of the command will bring up the Quick Return checklist and one can continue on normally from there. But I’m not 100% on that. Check out Foxtrot Alpha Aviation on YouTube, they might have one. But I’ve also passed the suggestion onto @Graeme_77.

You’ll need to provide more information. What do you see and what actions are you taking and what are the results, preferably with screenshots? Also you need to post the Log.txt from X-Plane.

Do you have a spare axis on the throttle instead? A lot of people use twist grip on their joystick if you have one.

The ones you’ve encountered thus far, yes please.

Use of ATS and A/P during G/A isn’t permitted in real world operation, but can be reengaged in the sim if desired. I don’t remember the exact sequence of the F/O’s automated G/A procedure, but at some point you’ll probably want to come out of T/O-rated thrust, which may be a good time to engage ATS and A/P.

What’s the command you’re using, exactly?

I think you’ll need to create a new airframe.

Can you please give some specific examples with screenshots, preferably of the mfd map as it’s larger? I suspect this is a known bug but want to confirm. Thanks.

Quite possibly!

As Cameron says above, the only update that’s potentially going to help is X-Plane 12, and that’s still theoretical. (Unless you’re talking specifically about the FBO van.)

Download issues will need to be handled by X-Aviation support <support@x-aviation.com>

These are from a bug in X-Plane that can’t be avoided, you can ignore them.

They’re basically used for creating Place-Bearing-Distance waypoints in your flight plan. Or for getting the GPS coordinate of a location (press down one of the knobs if I remember correctly) to create a custom data base waypoint in the FMS.

In the sim it’s primarily used as a staging location for the newest database to be activated as the primary, in-use database (“active data base”). Under the hood there’ll always be two databases available; one is the default nav data that comes with X-Plane (which changes when Laminar pushes new major versions of the simulator), the other is the content of your custom data directory, where third-party nav data is installed, e.g. from Navigraph. The CHK DATA BASE DATES message is showing (and the database date range text is in yellow) because your sim’s date is outside of the valid range for the nav data cycle that’s active. As you can see your sim is set to the 22nd of March (“DATE”).

You can’t. Only active is updatable to cycle between the two.

I’ll ask the developer but can you use commands instead? The raw datarefs are more for driving the animations.

One log doesn’t really identify the cause, the other says it was SAM that crashed.

It will, if you select “Track real-world date & time” from the Flight Configuration window.

It matches the date and time from the sim, in the current year from the system clock, as obtained via the simulated GNSS receivers (I assume).

Click on the Conditions header until you see Condition 1 & 2, then click Condition 1 or 2.