mike1864 wrote: ↑Tue Feb 10, 2026 11:44 am
Prior to my second breakdown, the break was happily coming and going for several minutes, proving that this scenario - matching the OP's symptoms -
does happen. Mine displayed several seconds of contact, then several seconds of open circuit; ie not related to the engine's rpm.
An intermittent connection's previous stabilising for a thousand miles seems unlikely (and very lucky). But it's the only diagnosis that fits my events.
Vibration, heat and the springiness/position of the wire all obviously play a part in such intermittent discontinuities. But here there's also arcing; this junction is carrying the same traffic as the contact breakers, but without the benefit of a spark suppression device. So a partial "remedial" weld is possible, albeit temporary, due to contamination with wire enamel, flux and cooling oil.
But we'll never know! Even a forensic, microscopic examination of the joint would have been scuppered as soon as the top was lifted off.
Hence my suggesting a hefty wallop to any suspect coil; and in several different planes. I reckon that such an extreme impact - outside the range of engine vibrations - is likely to permanently dislodge a dodgy contact, rather than repair it. And it wouldn't trouble a good joint.
But we all agree to carry a spare. And even if it's brand new, one of my branch members (yet another engineer!) sensibly recommends testing it in situ before putting in the boot.
Ahhh, some more details...
It's the 2 year gap that I find incredible, but perhaps you didn't do many miles in that time.
From your earlier comments, we've both clearly experience weird faults in the past, which influence our thinking.
The one lesson to take away from this discussion is that the old adage around these parts, of
It's never the Coil
is well and truly disproven, especially with anything produced in the last 40 years or so.
I've got quite a few strange and wonderful tales...
Like the aircraft which during start, would shut down the Auxiliary Power Unit (APU) if the Pilot contacted Air Traffic on the 'Local' frequency.
The Pilots lived with it for a while, just delaying contacting the Tower until after engine start.
But eventually we got to look at it.
We'd recently been given a new bit of test equipment which allowed us to monitor the APU Control Unit and it's various sensors on the APU, Temperature, Speed, amongst others.
Using this new bit of kit, we learned that the APU Control Unit was detecting an over-speed (or over-temp, I forget which) when the call to the Tower was made.
Cutting a long and tedious story short, we found that the Radio guys had replaced this aircraft's upper VHF Aerial and it's cable some months before.
In fitting the new cable, they had not routed it exactly how the old one was fitted and had cable tied it, only for about 9" or so, right next to the cable loom carrying the APU wiring. The electromagnetic interference radiated by the aerial cable was inducing a signal into the APU sensor wiring which made the Control Unit think there was an APU fault.
Got the Radio guys to do their job properly, and follow the designated clipping points and snag fixed.
The problem had only arisen when the Tower had changed some of it's local radio frequencies; something which was done periodically just to make the Soviets do some work when eavesdropping. This was in the '70s before secure radios became standard.
