Sun Nov 27, 2016 5:04 pm
#1500648
Having only recently got the aircraft back from its annual, and only having done a few short flights squeezed in around work, I decided yesterday to do a dusk trip from Cambridge to Gloucester and back as the weather had turned out OK.
The way out was uneventful (and indeed I can recommend the burgers at the Aviator - very nice!). The journey back had started fine, other than a bit of concern about some traffic that crossed ahead of me, as it's always difficult to judge distances at night (kept a careful watch on it - I presume as it proceeded to orbit around a town at what appeared to be fairly low level that it was a police helicopter or similar in the end).
That was until all of a sudden the low voltage light came on - look at the load meter (which shows load on the alternator) and indeed it's showing 0. First thought is don't panic, remember priority #1 is fly the aircraft, so I turned the autopilot off (don't want it doing anything erratic if the voltage drops) and ensured I was stable on heading and altitude etc.
Next thought is perhaps it's a temporary issue - switch off the avionics, and the master, wait 10 seconds (reading the flight manual later I gather I should probably have waited a minute) and turn back on - still getting low voltage light and no load shown.
Check circuit breakers, all in.
So, assess the situation - navigation is not a big problem (current heading will take me straight to Cambridge, and I had SD running on an iPad etc), so concerns are lighting and communication. I decided therefore to run:
- COM2 (COM1 is a GNS430 so the screen likely means higher draw)
- Nav lights
- Very minimal instrument lighting
Also get handheld transceiver out the bag, and ensure it works and is tuned to the Cambridge frequency so it's ready if needed if the situation gets worse.
I'd not been talking to anybody at this point - I'm about 5 minutes from range of Cambridge so I waited to talk straight to them. I decided not to declare a PAN PAN (though probably should have done in retrospect), but did inform them I'd had an alternator failure, and while I had a handheld onboard there was a risk of communications failure.
Next issue was I realised I couldn't see any town lights any more - a solid cloud layer had appeared beneath me - without my avionics this would make an instrument approach 'interesting' to say the least. As such I decided (based on the weather forecast I'd seen beforehand) to descend to MSA and see if that pops me through it, which fortunately it (just) did.
As I closed in on Cambridge it occurred to me that I might have an issue lowering the gear, as the hydraulic pump is electrically powered, so I quickly reminded myself on the emergency procedure in case that was needed.
At 5 miles I lowered the gear (which fortunately came down fine and gave me 3 greens), reported to Cambridge who cleared me to land at that stage. I decided against using landing lights, as I'd rather do the landing without them than have them fail at a critical moment, and as it was the landing was fine.
After parking up I checked for any obvious problems (e.g. belt snapped or anything like that), but nothing clear - will have to get the engineers to take a look on Monday (though Murphy's law says it'll all work fine)...
Thinking it through afterwards, learning points are:
- I should probably have got the checklist out rather than doing everything from memory
- It wouldn't have hurt to declare a PAN PAN, not really sure why I didn't
- In this case handheld was in my flight bag on the passenger seat, if it had been on the back seat that would have been more complicated - should probably put it in the seat pocket beforehand
The way out was uneventful (and indeed I can recommend the burgers at the Aviator - very nice!). The journey back had started fine, other than a bit of concern about some traffic that crossed ahead of me, as it's always difficult to judge distances at night (kept a careful watch on it - I presume as it proceeded to orbit around a town at what appeared to be fairly low level that it was a police helicopter or similar in the end).
That was until all of a sudden the low voltage light came on - look at the load meter (which shows load on the alternator) and indeed it's showing 0. First thought is don't panic, remember priority #1 is fly the aircraft, so I turned the autopilot off (don't want it doing anything erratic if the voltage drops) and ensured I was stable on heading and altitude etc.
Next thought is perhaps it's a temporary issue - switch off the avionics, and the master, wait 10 seconds (reading the flight manual later I gather I should probably have waited a minute) and turn back on - still getting low voltage light and no load shown.
Check circuit breakers, all in.
So, assess the situation - navigation is not a big problem (current heading will take me straight to Cambridge, and I had SD running on an iPad etc), so concerns are lighting and communication. I decided therefore to run:
- COM2 (COM1 is a GNS430 so the screen likely means higher draw)
- Nav lights
- Very minimal instrument lighting
Also get handheld transceiver out the bag, and ensure it works and is tuned to the Cambridge frequency so it's ready if needed if the situation gets worse.
I'd not been talking to anybody at this point - I'm about 5 minutes from range of Cambridge so I waited to talk straight to them. I decided not to declare a PAN PAN (though probably should have done in retrospect), but did inform them I'd had an alternator failure, and while I had a handheld onboard there was a risk of communications failure.
Next issue was I realised I couldn't see any town lights any more - a solid cloud layer had appeared beneath me - without my avionics this would make an instrument approach 'interesting' to say the least. As such I decided (based on the weather forecast I'd seen beforehand) to descend to MSA and see if that pops me through it, which fortunately it (just) did.
As I closed in on Cambridge it occurred to me that I might have an issue lowering the gear, as the hydraulic pump is electrically powered, so I quickly reminded myself on the emergency procedure in case that was needed.
At 5 miles I lowered the gear (which fortunately came down fine and gave me 3 greens), reported to Cambridge who cleared me to land at that stage. I decided against using landing lights, as I'd rather do the landing without them than have them fail at a critical moment, and as it was the landing was fine.
After parking up I checked for any obvious problems (e.g. belt snapped or anything like that), but nothing clear - will have to get the engineers to take a look on Monday (though Murphy's law says it'll all work fine)...
Thinking it through afterwards, learning points are:
- I should probably have got the checklist out rather than doing everything from memory
- It wouldn't have hurt to declare a PAN PAN, not really sure why I didn't
- In this case handheld was in my flight bag on the passenger seat, if it had been on the back seat that would have been more complicated - should probably put it in the seat pocket beforehand