DRIVESHAFT FAILURE
gear fail = the shaft between the input and output end of that gear breaks, however so.
However, Nick's post indicates that the problem won't happen again since the shaft and gear were redesigned - therefore not much point in teaching it in the sim.
On the N1 governing by the DECU - with AC talking about matching N1 or Tq - I think that is confusing the ability to beep the engines up and down to match them in the way you prefer with what the DECU is designed to do (govern N1 and load share with the other engine)
Originally Posted by [email protected]
1. so it is a shaft failure or the bolts that hold the gear to the shaft and not the gear breaking up - that makes more sense.
2. However, Nick's post indicates that the problem won't happen again since the shaft and gear were redesigned - therefore not much point in teaching it in the sim.
3. On the N1 governing by the DECU - with AC talking about matching N1 or Tq - I think that is confusing the ability to beep the engines up and down to match them in the way you prefer with what the DECU is designed to do (govern N1 and load share with the other engine)
2. However, Nick's post indicates that the problem won't happen again since the shaft and gear were redesigned - therefore not much point in teaching it in the sim.
3. On the N1 governing by the DECU - with AC talking about matching N1 or Tq - I think that is confusing the ability to beep the engines up and down to match them in the way you prefer with what the DECU is designed to do (govern N1 and load share with the other engine)
2. As I mentioned earlier, we do not cover this malfunction in the simulator. It is discussed in class room training, more-so to get the trainees to think about and diagnose a set of circumstances which might not be covered in the RFM. Not all malfunctions are in the ECL.
3. There is no beep available to the pilot with DECU in automatic mode. The DECU gives you 107% N2 on both engines with N1 matched. That's it. The engine trim switch on the pilot collective - of which there is only one - only functions when the engine is in manual mode (i.e. using the MFCU controlling fuel flow, DECU controlled AFCU is disabled). It will beep up/down the engine/s in manual mode. Things get a bit tricky with the single eng trim switch and both engines in manual mode, particularly if there is a TQ split between the engines. This isn't usually practiced in the simulator, but it is easily manageable if you know what you're doing.
On the N1 governing by the DECU - with AC talking about matching N1 or Tq - I think that is confusing the ability to beep the engines up and down to match them in the way you prefer with what the DECU is designed to do (govern N1 and load share with the other engine)
212man - yes, my mistake, I wrote N1 when I should have put N2 - it comes from years of calling them Ng and Nf instead of N1 and N2 - doh!
Gulli - thanks, the Bell DECUs and Airbus DECUs clearly work in subtly different ways.
Since many aircraft have the facility to let you beep up Nr for Cat A, either automatically or via a switch/beep, I assumed the 76 was the same.
Gulli - thanks, the Bell DECUs and Airbus DECUs clearly work in subtly different ways.
Since many aircraft have the facility to let you beep up Nr for Cat A, either automatically or via a switch/beep, I assumed the 76 was the same.
And the other point. The DECU has no idea what the NR is...it doesn't even have an input for NR signal. The trigger for the DECU to govern N2 is when it senses the ECL in FLY position.
Not quite. After the engine is started, the DECU only controls N1 once the N2 exceeds 9%. Which is why, if you start the engine with the rotor brake on and then move the ECL from IDLE to FLY, the engine stays at idle.
And the other point. The DECU has no idea what the NR is...it doesn't even have an input for NR signal. The trigger for the DECU to govern N2 is when it senses the ECL in FLY position.
I was also talking in generalities about any governor, whether a FADEC, a DECU, an ECU or a hydro-pneumatic system using P3 air and bob weights. You start the engine and the N1 is governed then, as you increase the power the N2 increases and at a certain point it becomes the datum that is then governed.
The trigger for the DECU to govern N2 is when it senses the ECL in FLY position
(Note - I do know that in the S92 the Nf/N2 is referred to as Np, but was keeping it simple)
Last edited by 212man; 25th Feb 2018 at 14:39.
Terminology
I think we should all think carefully about..
N1/Ng
N2/NP
N3/Nr?
Goes to show standardisation is required..
Hated Torque matching 212 - 3B engine with TCU. 412/212 with ITT trim better but can lead you away... PTGs obviously don't match perfectly and one OHC unit against a almost timex unit can be interesting. PWAC removed field cleaning from MM so orifice clean no longer an option
Back to original question.
Most twins have overspeed protection of some sort. Singles driveshaft failure will be interesting...
Revert to the pilots...
N1/Ng
N2/NP
N3/Nr?
Goes to show standardisation is required..
Hated Torque matching 212 - 3B engine with TCU. 412/212 with ITT trim better but can lead you away... PTGs obviously don't match perfectly and one OHC unit against a almost timex unit can be interesting. PWAC removed field cleaning from MM so orifice clean no longer an option
Back to original question.
Most twins have overspeed protection of some sort. Singles driveshaft failure will be interesting...
Revert to the pilots...
But Ng = gas generator rpm
Nf = free power turbine rpm
and Nr = rotor rpm
That is both logical and easily understood
Nf = free power turbine rpm
and Nr = rotor rpm
That is both logical and easily understood
Nick's post indicates that the problem won't happen again since the shaft and gear were redesigned - therefore not much point in teaching it in the sim
There was a case of a 412 in Oz, airborne for a check flight after service, and the drive shaft from the combining gearbox let go.
Two serviceable engines having a little overspeed, rotor having somewhat of an underspeed, but the cool captain pulled off a good auto and all was well.
Two serviceable engines having a little overspeed, rotor having somewhat of an underspeed, but the cool captain pulled off a good auto and all was well.
The aircraft was damaged but they walked away...I think I read that the auto technique as described by the Captain was to develop the flare at the bottom until the tail stinger hit the ground, and then level off and land. And that's exactly what happened: the impact bent the tail boom but, as I said, they walked away.