PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Rotorheads (https://www.pprune.org/rotorheads-23/)
-   -   DRIVESHAFT FAILURE (https://www.pprune.org/rotorheads/583598-driveshaft-failure.html)

gulliBell 24th February 2018 07:18


Originally Posted by John Eacott (Post 10063405)
I suspect that it hasn’t been pointed out to you because your interpretation is incorrect...

@megan 100% does know what he's talking about, he's just been misunderstood. If I may clarify his point. Within the S76 MGB, if the gear (that spins clockwise) between the main drive shaft gear (that spins anti-clockwise) and the gear (that spins anti-clockwise) that connects the #1 engine input gear to the TR drive shaft, should it fail, then the #1 engine will drive only the TR but not the main rotor. In that instance, should you misdiagnose the indications and shut down the #1 engine you will lose drive to the TR (the power from #2 engine only gets as far as the main drive shaft because of the failed gear). This has happened in an S76 before.

It's a scenario that gets discussed during recurrent training in the classroom, but I've never been asked to demonstrate it in the simulator. If the trainee is totally on-top of all the other malfunctions covered in the syllabus, and there is time available to look at other things, then sure, take a look at this one in the sim.

John Eacott 24th February 2018 07:30

gulli, you’re quite right and my interpretation of megan’s statement was of a No 1 engine failure. Not a No 1 drive failure.

RTFQ John!!

henra 24th February 2018 08:47


Originally Posted by megan (Post 10063369)

Thank you! Nothing beats a good schematic. Or: A picture is worth a thousand words.
With that schematic the possible failure mechanism and consequence becomes very clear!

gulliBell 24th February 2018 09:47


Originally Posted by henra (Post 10063514)
..With that schematic the possible failure mechanism and consequence becomes very clear!

What is also interesting, with this malfunction in S76 equipped with DECU, what behavior might you expect from the engines? The pilot response as per the ECL should be the same whether you have DECU or not, because this would be primarily indicated as a MGB failure (with secondary indications)...just don't get suckered into shutting down the #1 engine otherwise you'll give yourself a TR drive failure as well. As @megan correctly points out.

[email protected] 24th February 2018 12:26

Isn't that scenario a bit far-fetched? Surely if that shaft failed, the engine would very rapidly spin up due to the removal of the load and shut itself down?

I don't know what overspeed protection there is but if it has a DECU, it would surely shut the engine down.

Has that shaft ever failed? If not, then it is quite understandable that it isn't covered in annual sim training.

gulliBell 24th February 2018 12:56


Originally Posted by [email protected] (Post 10063698)
Isn't that scenario a bit far-fetched? ...

The scenario is not far-fetched because it has happened before. We aren't discussing a shaft failure, we drifted to discussing a particular gear failure inside the MGB. With this malfunction the #1 engine doesn't rapidly spin up, it is still governed at 107% N2 and under load driving the TR, but not the main rotor. The #2 engine is still driving the main rotor but not the TR. If you move the collective the TQ on both engines will respond accordingly, #2 engine because of the main rotor pitch change, and the #1 engine because of collective yaw coupling and the resulting TR pitch change. A pedal input will result in a change in TQ on #1 engine but not #2 engine. When DECU are involved which talk to each other to maintain constant N1 on both engines, when there are vastly different loads placed on each engine due to the MGB gear failure, then the discussion gets interesting. But, as I mentioned before, not normally practiced in the simulator unless the trainees are a whiz at everything else. However it is discussed in the class during systems review, particularly if the trainees are sleepy.

albatross 24th February 2018 13:23

One thing I always wondered is why on the Bell 212 tripletach the Rotor RPM is a small, short needle and the eng RPM are 2 big long needles? Isn't Rotor RPM the most important?

gulliBell 24th February 2018 13:49

Reason being, there are two N2 needles and one NR needle. If the big needle was NR, there wouldn't be enough length in the 2 shorter N2 needles so the "1" and "2" flags on the respective needles didn't overlap.

[email protected] 24th February 2018 15:17

Gullibell - I still don't see it - if that gear fails (not sure what you mean by gear failure - does it disintegrate or just stop spinning?) the gear that links it to the TR drive must surely also fail/stop spinning since it is attached to the same shaft (as far as I can see in the diagram).

And, if the gear fails and the load from the MRGB is suddenly removed leaving only the load of the TR on the No1 engine (especially in the cruise with relatively low TR thrust) there must be a Tq split until the N1 governor for No 1 engine catches up and backs off the fuel.

albatross 24th February 2018 16:21


Originally Posted by gulliBell (Post 10063763)
Reason being, there are two N2 needles and one NR needle. If the big needle was NR, there wouldn't be enough length in the 2 shorter N2 needles so the "1" and "2" flags on the respective needles didn't overlap.

Well if all three are lined up it doesn't matter and if you have a non- engagement or drive shaft failure the eng needle number will appear. But perhaps I am grinding the coffee a little fine ...I just think that Rotor RPM is the most important indication in the cockpit.
I was always taught...caution light, strange noise, disturbance in the force...check Rotor RPM and control that before you do or say anything else.

gulliBell 24th February 2018 17:18


Originally Posted by [email protected] (Post 10063831)
Gullibell - I still don't see it...

gear fail = the shaft between the input and output end of that gear breaks, however so. The input part of that gear still turns freely thus continues to transmit power from #1 engine output to the TR drive gear.

yes, of course there will be a TQ split between the engines if one engine is driving the main rotor and the other is driving the TR. There will be a point in the collective range of travel where the TQ on each engine will be matched.

gulliBell 24th February 2018 17:32


Originally Posted by albatross (Post 10063889)
Well if all three are lined up it doesn't matter...

But it does matter. If N1 was the short pointer there is not enough length on that radius for the "1" and "2" flags not to overlap. Just draw it on a piece of paper and it should be clear why. Also, just because the NR pointer is shorter than the N2 pointers on the indicator doesn't assign it any lesser priority.

RVDT 24th February 2018 17:47

Lets roll back a bit here:

Nick Lappos 2nd Nov 2001, 18:09


The procedure is based on an actual failure that occurred about 15 years ago, where the input gear attachment bolts lost torque and the separation that you describe actually occurred.
The gear was redesigned, and no repeat failure occurred. The flight crew noted the problem as noise and rumbling, a momentary upspeed of #1 engine, a swing to the left (extra tail thrust)
and then back to normal, with very low #1 torque and high #2 torque.
After a bit of discussion, the crew left well enough alone, and flew home without shutting down #1 (what a good pair of guys! If it works, leave it alone!).

When they landed, they noted that the failure, in that the tail rotor was not connected to the main rotor.
We id'd the problem and fixed it asap, of course, and no repeat has occurred. We inspect all boxes on overhaul for signs of lost torque on that gear to see if any recurrence is creeping back,
and everything is fine now.

For Nr Fairy
The above is not like a more common failure that NR fairy notes, where the engine shaft going to the transmission can fail, and N2/Np can go up while torque goes down. In that case, you have an
engine power loss, but a healthy rotor drive train otherwise. That can be confusing because the engine rpm on the triple tach goes up, but the rotor goes down. The rotor is your closest friend,
so it is wise to make it happy first, of course. Crews can get confused when those needles, always stuck together before, start to disagree.

Also, I am surprised that any A's are flogging around with disconnected electric overspeed systems. They were a pain in the early days (1979) but should be healthy now. The normal governor
will catch these failures we describe, I think, so it is not essential to the failures on this thread, but the electric overspeed is helpful for internal engine failures where the power section can unbutton
from the compressor, the internal engine overspeed can get very high and engine rupture is possible.
There are other clues to Nr - noise and vibration - pretty obvious but unless you have experienced it before it may be a little bit of a surprise as to what the strange noise is.

We used to do touchdown autos in the old days with the RRPM obscured for the student - surprising how close you can keep it to correct as you are attuned to the noise and vibration.


When DECU are involved which talk to each other to maintain constant N1 on both engines, when there are vastly different loads placed on each engine due to the MGB gear failure, then the discussion gets interesting.
I think you might mean NG or N2.

gulliBell 24th February 2018 18:19


Originally Posted by RVDT (Post 10063971)
..I think you might mean NG or N2.

No. The DECU talk to each other to match N1, unless TQ limit on one engine is reached before the other then the DECU will stop matching N1.

RVDT 24th February 2018 18:31


No. The DECU talk to each other to match N1, unless TQ limit on one engine is reached before the other then the DECU will stop matching N1.
So if you have a stronger (better performing) N1 or Ng than the other you must have Q splits all the time?

gulliBell 24th February 2018 23:06


Originally Posted by RVDT (Post 10064004)
So if you have a stronger (better performing) N1 or Ng than the other you must have Q splits all the time?

Correct. The DECU match N1 for load sharing. RFM Part 2 Section 1 pg 1-10 refers, together with all the other intricacies of the DECU. And just to extend on that concept, the pilot has no control over TQ matching with the engines in automatic mode. So even if the pilot wanted to, he can't match/trim the TQ output of each engine. The DECU will only allow N1 matching until TQ limits are reached. If one engine has a better TQ margin than the other, the DECU will hold it at the TQ limit and then N1 will split until the weaker engine reaches its TQ limit. The DECU gets pretty busy at that point with soft limiting logic, and eventually blow-away logic, if you keep demanding more power. When you back off from a TQ limit the DECU reverts back to N1 matching for load sharing. It's the way the system is designed.

Unlike helicopters like B212 or B412, which have a TQ split limitation, there is no such limitation in a S76 fitted with DECU. As long as the engines make power assurance, flying with DECU matched N1 and a TQ split due to engines having different margins is no big deal.

Ascend Charlie 25th February 2018 03:24

gulliBell, the 76B allowed the pilot to match either N1 or Tq. I usually matched Tq to make the dial line up in a pleasing and eye-catching manner.

megan 25th February 2018 05:27

76B, who for AC, in what role, and how did it compare with regard to the rest? Have lot of time in the A and C.

gulliBell 25th February 2018 07:08


Originally Posted by Ascend Charlie (Post 10064269)
gulliBell, the 76B allowed the pilot to match either N1 or Tq..

Sure. I was particularly referring to DECU in S76C++...C+ also, sort of.

gulliBell 25th February 2018 07:17


Originally Posted by megan (Post 10064298)
...Have lot of time in the A and C.

Big jump between A/C and C++, I think you'd like it. I'm old fashioned, I like the 212.

[email protected] 25th February 2018 09:31


gear fail = the shaft between the input and output end of that gear breaks, however so.
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.

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)

Ascend Charlie 25th February 2018 09:31

The B in the 76B stood for BALLS, which it had plenty of with the PT-6 and FADEC.

gulliBell 25th February 2018 11:42


Originally Posted by [email protected] (Post 10064474)
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)

1. I think that gear is 2 separate pieces that are bolted together. As NL pointed out the failure mode in the example cited was bolts coming loose. Gears in helicopter gear boxes can certainly fail and make metal for other reasons. I know, not long after when we got C model there was an AD about the possibility of loose bolts within the MGB. Sikorsky sent a maintenance team to open all the gear boxes in the new helicopters and check the torques on the bolts. They had some pretty impressive test gear with them. It is very rare event to see inside a S76 MGB.

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.

212man 25th February 2018 11:53


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)
DECUs, and any governing system, only govern N1/Ng when the engine(s) are at idle. With the Nr in the normal operating range they govern N2/Nf. Matching N1 is something different.

212man 25th February 2018 11:54


Originally Posted by Ascend Charlie (Post 10064475)
The B in the 76B stood for BALLS, which it had plenty of with the PT-6 and FADEC.

Pretty sure it doesn’t have FADEC.

[email protected] 25th February 2018 12:09

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!:ok:

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.

gulliBell 25th February 2018 12:28


Originally Posted by 212man (Post 10064634)
DECUs, and any governing system, only govern N1/Ng when the engine(s) are at idle. With the Nr in the normal operating range they govern N2/Nf.

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.

212man 25th February 2018 14:17


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.
So you start with the rotor brake on and the engine sits there happily at idle N1 - what do you suggest is controlling that value?


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 didn't suggest it did sense Nr, but if you don't have Nr you won't have N2 and in normal conditions they are matched.

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
Are you positive about that? In the S92 when you advance the throttles from IDLE to FLY the N2/Nr will rise and then reach the normal value of 105% at which point pushing the throttles forward further has no effect. This happens a couple of inches before reaching the FLY detent and clearly indicates that the FADEC has taken over N2 control. There also some flight checks that require the throttle to be retarded out of the FLY gate, but the N2 is still governed. It was the same in the 76A+ with its steam driven system.

(Note - I do know that in the S92 the Nf/N2 is referred to as Np, but was keeping it simple)

Salusa 25th February 2018 14:56

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...

[email protected] 25th February 2018 18:03

But Ng = gas generator rpm
Nf = free power turbine rpm
and Nr = rotor rpm

That is both logical and easily understood:ok:

megan 25th February 2018 23:45


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
Sometimes the dog of fate lifts its leg and urinates on the pillar of science. Never believe in the word never, as in, it can't happen. The only MGB problem in this regard I ever had was the rotor brake quill on a 212 snapping in half for some unknown to me reason. Bevel gear dropped and bounced around in the MGB and the brake disc left lying on the cabin roof. Any part can fail for any number of reasons, heat treating, tooling marks, corrosion, inclusions being a few. I'm sure some one once said a MGB can't fail and release the main rotor. We know better now, and still await the initiating cause.

Ascend Charlie 26th February 2018 02:03

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.

gulliBell 26th February 2018 10:06


Originally Posted by Ascend Charlie (Post 10065224)
..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.


All times are GMT. The time now is 19:21.


Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.