Art

I've pushed the PFD 1 circuit breaker in and out several times again, no change. Then, related or not, Windows crashed. After rebooting I started X-Plane again and when I loaded the TBM, the PFD actually came on! It is working now, no idea why - maybe cycling the breaker did it (or the Windows crash fixed it ;-) I hope it stays that way.

I already have, no change. Thanks!

They are all in. Specifically also the one marked PFD 1.

Thanks, but yes. I have used "Fix all systems" and made sure the checkbox for the random failures is disabled.

After not flying it for quite a while I have started up my TBM again. Unfortunately the pilot side PFD remains blank (using the normal startup procedure. I also tried to use any switch I could think of). I made sure no failures are set. I've re-downloaded and re-installed the TBM. I am running X-Plane 11 updated to the latest version (no betas and not using the experimental flight model). I have created a new airframe. The problem remains. If I start up the engine anyway, the TRQ indication on the MFD and PFD 2 remains crossed out. The avionics seem to work normally in other airplanes and I have not encountered this problem before. What can it be? TBM900_Log.txt Log.txt

Yes. I only thought about the gear too close to the airport and because I (rightly) guessed that fuel was very low I did not consult the POH In this hurry. So I pumped, but not enough (the gear control lights were not working either). ...and that is what makes it fun and challenging to fly! I appreciate that! Yes, I should fly it a little less by intuition and pay attention to checklists and the POH a bit more. Thank you for your detailed reply, I will take off in your TBM soon again, it is currently my favorite plane!

I understand. But in this case this is not what happened, please see my post above. It was a newly created airframe.

Thanks. What happened though is I did those test flights, sometimes crashing the plane, but then I always created a new airframe. I just did not reload the TBM when doing so, should that be done? (I mean I created the airframe and started flying it, not selecting it anew via the X-plane Flight Configuration.) I had X-plane and the TBM loaded for more than a day, putting the computer into sleep mode in between (Win10). At one point I created a new airframe and with that I set out on this trip. At the end of this flight in which the instruments failed I had a crash landing due to the gear not coming down. Then the maintenance manager told me the aircraft was damaged beyond repair. I have extracted the part of the original TBM900_Log.txt that pertains only to this trip. As I'm not familiar with reading these log files I can't tell exactly what the boot sequence for a new airframe looks like. So I've included the last few lines pertaining to the previous, damaged airframe. The actual boot sequence for the new airframe seems to start around line 6 or 7. The excerpt starts with what is line 30354 in the original log file. My questions as to why the flight instruments and also the landing gear failed: Was it because something carried over from a previous, damaged airframe? Would it be saver to reload the TBM or even X-Plane when creating a new airframe? Was it pilot error? Is there any mistake I could make that could cause all instruments to suddenly fail (as well as the landing gear)? Is this an intended simulation of a malfunction that could happen on the real airplane? (I had not set any failures under X-Plane Flight Configuration.) Or is it not possible to know why these failures might have occurred? TBM900_Log_excerpt.txt

Thank you for responding so quickly! Yes, I was trying to check the maintenance manager. But I got something like "aircraft damaged beyond repair" under any of the sub-categories and it was not possible to see any details. Looking at the file I now see that I have gone through several airframes in this session. I was doing test flights trying to simulate a burn-out and restart the engine in flight (unsuccessfully), some resulting in emergency landings off airport and crashes. Also, for more realism and because I felt I had mastered flying the plane, I had turned all in-flight tips off on this trip...

Lately I've been flying the TBM quite a bit and appreciating how detailed the simulation is. So far any of the problems flying it were due to oversights or lack of preparation on my part. However yesterday something happened for which I have no explanation: I was taking a new airframe on a ferry flight across the North Atlantic. On the second leg from EGPF (Glasgow) to BGGH (Nuuk), after four and a half hours of an uneventful flight there was a single warning ping sound and all flight instruments went dark. I was over central Greenland at 30000 ft. I immediately turned on oxygen and got to a much lower flight level. It turned out the engine was still running (just from the sound and performance). With a lot of effort I was able to still fly the plane to Nuuk with the help of the AVITAB, having only the ESI and the Standby Compass as flight instruments. The autopilot was not available either, I was not able to get a clear sense of whether the electrical trims were working. I checked the fuses, they were all in and I flipped a lot of switches to see if the instruments would come back on - nothing! When finally approaching Nuuk I was surprised to hear AFIS come on - since the intercom panels were also dark I had no way to check or set other frequencies. On approach I did not do a fly-by (visual landing gear check) since I had no tower frequency, I was not sure if the gear was down and tried using the landing gear extension hand pump as well. (I did the emergency gear lowering procedure incorrectly, I now know, but before that the gear had not come down either.) I chose to land immediately, gear or no gear, since I assumed fuel might be low from not having been able to fly in a straight line and at lower altitude with unknown power settings. (I was right, on the ground it turned out there was hardly any fuel left.) It turned out the gear was not down and I did a belly landing with damage beyond repair to the airframe. I have no idea why this incident happened. I checked the battery after the crash, and it was in a normal loaded state. In the TBM900_Log.txt I see "Component Pilot's Primary Flight Display has failed suddenly due to an internal electrical fault" and a lot more similar lines. Unless I find the error the plane will not feel save for long trips any more. So I would appreciate any input. Thank you! Attached is the TBM900_Log.txt (The trouble seems to start at 2021-07-03 00:49:14) TBM900_Log.txt

Thanks again, Goran! After some trying I have my hardware issues resolved and the plane seems to be working fine. I saw that the TBM had its own hardware profile, either natively or I created it myself. Activating my current user profile fixed the problem. Sorry, my own mistake! (I had moved flight controls around since last using the TBM and had distributed functions differently. Saitek Pro Flight rudder pedals and yoke are also involved, as well as the Logitech Extreme 3D Pro joystick for some functions, particularily to replace the Saitek Throttle Quadrant, since it has a broken PS2 connection to the yoke.)

Thanks for the quick answer! Installing the latest NVDIA driver solved the problem. (Realized this issue after looking at X-Plane log.txt from the beginning...) But now there is another problem: On this plane my Logitech Extreme 3D Pro joystick doesn't work. It works with other planes and also worked after first installing this one. What might be the problem? Attached you find the X-Plane log.txt as it is now Log.txt

Hi, My HotStart TBM900 has been causing X-Plane 11 to crash to desktop upon loading for months now, after working fine initially. All other planes are working. A pity, since is's a great model! This is my system: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz 3.41 GHz - 64-bit, x64-based processor 32 GB RAM NVIDIA GeForce GTX 1070 (using a single monitor.) Windows 10 Home - Version 20H2 Windows Feature Experience Pack 120.2212.551.0 X-Plane 11 updated to latest version (11.53). I have tried running it without any plugins and I have removed and re-installed the plane (TBM_900_v1.1.13), nothing changed. Also I have considered this. So I removed all custom scenery for a test, no difference. I hope you can help, Thank you! _______________________________________________ Here are the last lines of my X-Plane Log.txt: =>removed, because Goran posted: "I'll need the complete log.txt file immediately after X-Plane crashes." A close look at X-Plane Log.txt revealed a problem with the NVDIA driver, apparently only affecting this plane. Installing the latest driver solved the problem. But now my joystick doesn't work for this plane. - See my post below.