I am an active trainer in an ATO. For our X-Plane 11 students we use the Beechcraft Baron BE58 Ultimate as our multi-engine training aircraft. One problem we have is the practise of Engine Failure.

At present, when using 'yourcontrols', we appear to only be able to fail an engine when the pilot controlling does so deliberately themselves: in other words, the instructor pilot is unable to fail an engine when the student is doing the flying. This takes away the element of surprise, an essential part of this aspect of multi-engine training.

Does anyon have any solutions?

rr

Not a direct answer but you could check:

Engine Fail Plugin - X-Plane Developers and Plugins - X-Plane.Org Forum

Features of FSFlyingSchool 2022 for X-Plane

as well as Austin's own suggestion 🙂

Complete tutorial on ControlPad for X-Plane - YouTube

Edited October 19, 20223 yr by jcomm

Yes,thanks for the pointers. Sadly, they are mostly about what was going on 14 years ago! Nothing much seems to have happened since.

I have been trying the XPlane 11 Instructor Operating System, just on my own computer. It works for many failures (but NOT for Engine Failure #). Engine Fire does work in spectacuar fashion - glad I was on the ground. RMI compass heading, VSI and ADI (AH to us old guys) also work well.

                                   Good news is that Engine Seize # works!

So, if you need to fail an engine, DON'T use Engine Failure - use Engine Seize # (and, confusingly, it comes under PROP!)

ne small step for man, ................

Now to see if it works across SmartCopilot???????

Edited October 19, 20223 yr by roadrabbit149
elucidation

58 minutes ago, roadrabbit149 said:

 

I have been trying the XPlane 11 Instructor Operating System, just on my own computer. It works for many failures (but NOT for Engine Failure #). Engine Fire does work in spectacuar fashion - glad I was on the ground. RMI compass heading, VSI and ADI (AH to us old guys) also work well.

                                   Good news is that Engine Seize # works!

So, if you need to fail an engine, DON'T use Engine Failure - use Engine Seize # (and, confusingly, it comes under PROP!)

Although, engine seize would mean (I think) that the aicraft could keep flying with the prop stopped, even if the prop is not feathered. (That's something to try in XP's Baron).

So, an alternative to "Engine failure", would be to fail the fuel pumps or the magnetos (I just tried it in the XP C172, and they indeed cause the engine to fail as it should be, but the prop is not seized).

Or, something more elaborate and treacherous, setting up a loss of oil pressure instead. In that case the engine failure would not be immediate, and a good student  could even catch it and act before the engine fails. 

 

Excellent advice - many thanks.

Your comment re stopping using Engine Seize raises the point: is it the prop that has seized (no feathering available),or has the engine itself seized (crankshaft)? In this latter case feathering may still be available as, I believe, it relies on 'stored' pressure to work.

I shall continue to experiment with the various failures. Another anomaly for me is that I can fail <Pitot Tube Sensor 2>, but not <Pitot Tube Sensor 1>.

rr

Edited October 19, 20223 yr by roadrabbit149

6 hours ago, roadrabbit149 said:

I am an active trainer in an ATO. For our X-Plane 11 students we use the Beechcraft Baron BE58 Ultimate as our multi-engine training aircraft. One problem we have is the practise of Engine Failure.

At present, when using 'yourcontrols', we appear to only be able to fail an engine when the pilot controlling does so deliberately themselves: in other words, the instructor pilot is unable to fail an engine when the student is doing the flying. This takes away the element of surprise, an essential part of this aspect of multi-engine training.

Does anyon have any solutions?

rr

Can you use the XPlane iPad remote app to fail an engine without interrupting the simulation?  I haven't tried it, but I that was feature of that app.

thanks,

Rich Boll

1 hour ago, roadrabbit149 said:

Your comment re stopping using Engine Seize raises the point: is it the prop that has seized (no feathering available),or has the engine itself seized (crankshaft)? In this latter case feathering may still be available as, I believe, it relies on 'stored' pressure to work.

In XP, "engine seize" seizes the crankshaft, not the driveshaft. In fact, if you both seize the engine and fail the driveshaft, the prop will still be able to windmill, being it now free from the seized engine crankshaft.

Anyway, i suggested not using the "engine seize" option because in that case, whether prop is feathered or not, would probably have little aerodynamic consequences, since the prop stops windmilling right away without the need to feather it. So, if the student is practicing engine failures and forgets to feather the prop, he'll get away with it.

On the other hand, if you fail the engine in a way that the prop keeps windmilling when not feathered, the aircraft will eventually crash in XP (as in RL) if the student does not feather the prop.

Edited October 19, 20223 yr by Murmur

This is my problem, trying to use three different base systems (P3Dv5, XPlane 11 and MSFS) for our students. You miss out on something really, really obvious!

I have only just found the IOS (Instructor Operating Station)!!!

I shouldn't be allowed out on my own   🙄🙄🙄