37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1502811 |
Time | |
Date | 201712 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cessna 310/T310C |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Flight Plan | VFR |
Component | |
Aircraft Component | VHF |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Total 940 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
Upon existing the runway at ZZZ I experienced a stuck mic on ground control frequency. I had no indications of issues in the prior to the flight. I was able to resolve the issue by recycling the avionics power and re-establishing communication with ground control. Since I had no prior indications that the equipment was having issues I considered one-time event. I contacted ground control for VFR clearance. I was given the VFR clearance and squawk code. No radio issues were present prior to or during taxi. I contacted tower and was given clearance to take off. The ceilings and visibility were unrestricted at time of departure. On the initial climb out I noticed that the garmin gtn's were indicating tx (transmit) and the ptt switch was not depressed. I tried to recycle the avionics but the problem still persisted. I squawked 7600 on my transponder to let ATC know I was aware of the problem. Since the nav/coms were still indicating they were transmitting; I figured the microphone was still hot; I stated my intentions were to fly straight out; level off at 1000; exit the charlie airspace; and remain clear of all airspace's since I was operating under VFR. I flew out to the east over the water still squawking 7600. Once clear of ZZZ charlie airspace; I was able to briefly re-establish communication with departure at which they told me to squawk VFR/1200 and radar services were terminated. I elected to pull the circuit breakers on both my nav/com's with hopes that I would not be effecting any of the other frequencies. I navigated via my garmin aera 796 portable which had current VFR charts on it to ensure I did not violate any airspace. I elected to change my destination to ZZZ2 from ZZZ1 since ZZZ2 was an uncontrolled field and two way communication was not required to land there. The rest of the flight to ZZZ2 was uneventful. I retrieved my airplane from ZZZ2 later that evening and flew it back to ZZZ1 when the tower had closed for the evening. The plane is currently at the avionics shop and will not fly until the issue is resolved. I am unsure what caused the equipment failure; and I am still waiting for the avionics shop to provide me with diagnosis.a few important lessons learned-always make sure I always have a backup/handheld radio in my flight bag.-do not assume anomalies with equipment are a one-time incident; plan accordingly.
Original NASA ASRS Text
Title: A Cessna C310 pilot reported that he experienced an intermittent stuck microphone.
Narrative: Upon existing the runway at ZZZ I experienced a stuck mic on ground control frequency. I had no indications of issues in the prior to the flight. I was able to resolve the issue by recycling the avionics power and re-establishing communication with ground control. Since I had no prior indications that the equipment was having issues I considered one-time event. I contacted ground control for VFR clearance. I was given the VFR clearance and squawk code. No radio issues were present prior to or during taxi. I contacted tower and was given clearance to take off. The ceilings and visibility were unrestricted at time of departure. On the initial climb out I noticed that the Garmin GTN's were indicating TX (transmit) and the PTT switch was not depressed. I tried to recycle the avionics but the problem still persisted. I squawked 7600 on my transponder to let ATC know I was aware of the problem. Since the nav/coms were still indicating they were transmitting; I figured the microphone was still hot; I stated my intentions were to fly straight out; level off at 1000; exit the charlie airspace; and remain clear of all airspace's since I was operating under VFR. I flew out to the east over the water still squawking 7600. Once clear of ZZZ charlie airspace; I was able to briefly re-establish communication with departure at which they told me to squawk VFR/1200 and radar services were terminated. I elected to pull the circuit breakers on both my nav/com's with hopes that I would not be effecting any of the other frequencies. I navigated via my Garmin Aera 796 portable which had current VFR charts on it to ensure I did not violate any airspace. I elected to change my destination to ZZZ2 from ZZZ1 since ZZZ2 was an uncontrolled field and two way communication was not required to land there. The rest of the flight to ZZZ2 was uneventful. I retrieved my airplane from ZZZ2 later that evening and flew it back to ZZZ1 when the tower had closed for the evening. The plane is currently at the avionics shop and will not fly until the issue is resolved. I am unsure what caused the equipment failure; and I am still waiting for the avionics shop to provide me with diagnosis.A few important lessons learned-Always make sure I always have a backup/handheld radio in my flight bag.-Do not assume anomalies with equipment are a one-time incident; plan accordingly.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.