engine-failure-again-lost-left-engine-this-time
-
As a first step, we would recommend double-checking that there aren't any control assignments being triggered unintentionally when you're reducing engine power. I personally haven't used the TCA Throttle Quadrant with the F28 but I seem to recall there may be some button/control assignments assigned to the detents by default? If so, one of those could be triggering something in the F28.
To test this, it may be worth creating a brand new controller profile for the TCA Throttle Quadrant and then clearing all the control assignments except the THROTTLE AXIS assignments. If the engine doesn't cut out then, then we can narrow it down to being a control assignment conflict.
Mark - Just Flight
-
@rbringh Check that you dont accidentally click the engine fire handles right below the AP Mode Selector. Its very easy to conveniently fail the left engine because of a wrong click during turbulences or view changes... Happened to me several times.
-
@dominicjaermann The two times it has happened out of about forty flights the only action being done was easing back on throttles. No mouse clicks, key presses or view changes. Strange, still checking this out.
-
@rbringh said in engine-failure-again-lost-left-engine-this-time:
@mark If it was a binding I would expect it to happen every flight. It has happened only two times out of about 40 flights. Different engine each time. I'm still checking things out.
Just in case: Its not the bindings you made, its the bindings which come default with some hardware.
So its a good advice to check ALL devices you've connected.
Its easy to miss one -
Me too.
Lost LH engine (1) for no explicable reason, assuming inadvertently pressed fire handle, but not sure.
Restart not possible, plenty of fuel, and even tried CTRL-E (don't laugh, I was desperate!).
However, that seemed only to put the engine fuel valves ON without ability to shut them off, and engine starters kept cycling on their own (obviously not doing CTRL-E again!).
It's a shame because it was an online flight that I'd flown twice before, and that new shiny aircraft feeling didn't last long...
Thoughts? -
We have been trying to replicate this internally to no avail so far.
For those that have the issue, would it be possible to provide a little more detail on when the issue occurred? I.e. at what altitude/speed, and if the issue occurred when chopping the throttles back to idle or if it occurred when slowly reducing the throttles to idle?
Also, if you suspect the engine fire guards have been opened you can reset the fuel shut-off valves by pressing the respective "RESET" buttons on either side of the glare shield. The indicators should always show OPEN during normal operations.
Mark - Just Flight
-
I have made over 25 flights in the plane and had the issue 3 times. It happened again to me yesterday. I was at cruise altitude FL270. KEYW to KDAB with a VOR flight plan. I was using the GNS530 on this flight. About 30 minutes into the 60 minute flight right engine shut off. No prior warnings just low oil pressure light on, believe it was hydraulics. Engine restarted fine. No controls or keys, buttons etc. were being used. In fact I was just using my Android tablet at the time.
I had two other events, one on descent involving left engine, another in cruise involving right engine.
Throttles are Thrustmaster TCA Airbus. Yoke is Turtle Beach Velocity One. I also use a Logitech throttle but it is configured as Landing Gear, Flaps and Speed Brake.
I use the same hardware configuration for all the planes I fly. Primarily the ATR, FSS Embraer 170/175, PMDG 737-700, Nextgen Embraer P-110 and a few other turbo props.
I had this issue with the 170/175 but that was resolved by the developers.
-
Had another left engine shutdown a few minutes ago. This time I was not able to restart. Absolutely nothing going on prior to the event. Dev's I know this is not a systemic problem as only one or two have had this issue, but sure would like to know what is causing it. GNS530 was on at the time.
-
@rbringh
I am not following this thread closely, soDid you rule out, sthg in your community folder is conflicting ->>
Rename Community to CommunityX
Create a new Community folder.
Copy ONLY the "justflight-aircraft-f28" folder over, no livery, no nothing else.
Fly a couple of times. (I know, its default MS airports only ... )Are you using MSFS control assignments only, or tools like SPAD / FSUIPC / AAO ?
Sthg is acting up on your install - 100% !
I am flying this aircraft since release day, not a single hickup. VOR2VOR / GPS 530.....with 370 GB of Scenery / Tools / Aircraft installed.
Recheck your hardware bindings AGAIN, yours and the MSFS default bindings !!!!
Check also "ASSISTANCE OPTIONS" - "FAILURE ..." - "ENGINE STRESS" to OFF
for the next x flights.
(Mine is set to ON, but just to be sure ! )Good luck !
