ebykowsky
Cleared for Takeoff
- Joined
- Dec 12, 2012
- Messages
- 1,405
- Display Name
Display name:
goalstop
TLDR: skip to paragraph 3
Had my first in-flight failure today on a just-for-fun XC to KAGS with my dad (fun for me, not as much for him ).--this was my first flight in a month, and my first flight over .5 hobbs in 2 months. A few minutes before getting to the airport, we get a call from the previous renter who just got back from KATL telling us to be careful about the electric system and that there's a very slow discharge from the battery as opposed to a steady charge--so, not wanting to mothball the flight, I decided to brave it and head out into the blue yonder, knowing that an electric failure isn't the end of the world (just ask a vintage Cub owner!)
Anyhow, before the flight, I shut off COM2, the GPS, and my NAV's and proceeded to KAGS--it ended up being a beautiful flight carving our way around clouds and viewing rain showers on the horizon in several directions. Interestingly, there was an A330 on the tarmac that got diverted on its way to KATL from Barcelona.
Then, about halfway back, after switching to KCAE approach, NAV1 flickers out, rapidly switching on and off... so, knowing what was going on, I switched the comms off, squawked 7600, and kept on flying the aircraft. Then, after a minute of squawking 7600, I shut off the avionics and master to save battery for the flaps. We circumnavigated the Charlie and dropped below it when we got close enough to the filed. I decided to only put in around 15deg. of flaps on final because I didn't want to be stuck with 30deg. if we had to go around and couldn't get them back up. Finally, we landed with a decent landing and taxied back and shut down... hope they get it fixed by tomorrow's flight!!!
All in all, the failure was a non-event, and I'm glad it happened so I could get that experience. Also, I would have never launched at night with knowledge of this problem; I knew it would be a more-or-less non-issue in the day.
Had my first in-flight failure today on a just-for-fun XC to KAGS with my dad (fun for me, not as much for him ).--this was my first flight in a month, and my first flight over .5 hobbs in 2 months. A few minutes before getting to the airport, we get a call from the previous renter who just got back from KATL telling us to be careful about the electric system and that there's a very slow discharge from the battery as opposed to a steady charge--so, not wanting to mothball the flight, I decided to brave it and head out into the blue yonder, knowing that an electric failure isn't the end of the world (just ask a vintage Cub owner!)
Anyhow, before the flight, I shut off COM2, the GPS, and my NAV's and proceeded to KAGS--it ended up being a beautiful flight carving our way around clouds and viewing rain showers on the horizon in several directions. Interestingly, there was an A330 on the tarmac that got diverted on its way to KATL from Barcelona.
Then, about halfway back, after switching to KCAE approach, NAV1 flickers out, rapidly switching on and off... so, knowing what was going on, I switched the comms off, squawked 7600, and kept on flying the aircraft. Then, after a minute of squawking 7600, I shut off the avionics and master to save battery for the flaps. We circumnavigated the Charlie and dropped below it when we got close enough to the filed. I decided to only put in around 15deg. of flaps on final because I didn't want to be stuck with 30deg. if we had to go around and couldn't get them back up. Finally, we landed with a decent landing and taxied back and shut down... hope they get it fixed by tomorrow's flight!!!
All in all, the failure was a non-event, and I'm glad it happened so I could get that experience. Also, I would have never launched at night with knowledge of this problem; I knew it would be a more-or-less non-issue in the day.