Narrative:

I filed an IFR flight plan due to MVFR conditions. Pilots have been experiencing problems picking up airborne clearances in this area; from columbus approach below 3000 feet MSL. To be safe; I requested a void time clearance via cell phone. I was using a noise cancelling bluetooth headset to hear over the engine noise. After a query from clearance delivery; I advised I would need at least 5 minutes to complete the run up and would depart from runway 28. I stopped on taxiway alpha near the midfield to copy and read back the clearance. I was having trouble hearing the clearance delivery person. It was like he was moving around the room away from the phone. I turned the phone volume up all the way and was able to copy as filed; climb and maintain 3000; expect 4000 in 10; the transponder code and contact departure on 118.425. I read it back; heard 'read back correct'; but was not able to hear the void time. I was advised there was a jet inbound at a distance and direction that I don't remember. I said I would expedite my departure so I didn't ask for a repeat of the void time and began to taxi. I assumed I would have plenty of time to be off in 5 minutes or less; but did not consider the time to climb to an altitude where columbus would hear me. The first communications I heard on 118.425 was the jet being cleared for the approach into aoh. I thought that was strange since I hadn't been able to check in yet. The controller was very busy and I didn't get a chance to talk until about 2800 feet MSL; and reception is normally poor until higher. It seemed like about an extra minute. I wasn't concerned as I expected I had a clearance and they probably already saw my squawk on radar. Fortunately; I was clear of clouds and the ceiling better than expected. I called reporting 2800; climbing 3000; looking for higher. The controller advised my clearance was void minutes ago. I leveled at 3000 and made sure I could maintain VFR. I did not respond as I began to weigh my options. In a little bit he called me back; had me ident and cleared me to 4000. I did go IMC before reaching 4000. The remainder of the flight was without incident.5 minutes is enough time to complete the checklist and get airborne but not enough time to get to altitude. It tempts pilots to rush through the pre-takeoff checklist and make mistakes. I resisted that urge and did the best I could do safely. I wasn't watching the clock I was flying the airplane. Being able to communicate directly with the controller via VHF radio in the airplane is substantially better than trying to hear over engine noise and the distraction of operating a cell phone in the airplane. I have tried putting the phone under the ear cup of the headset and even invested in a blue tooth headset but it does not compare. I believe that undependable communications contributed to this problem and represents an unacceptable risk. Previously there was a link to indy center before that worked very well from the ground up. I think if columbus approach should had the same capability it would mitigate this risk before someone gets hurt. When it comes to clearances and dependable communications there should be no compromise.

Google
 

Original NASA ASRS Text

Title: GA pilot reported being airborne after the clearance void time; and attributed this deviation to undependable communication with Columbus TRACON below 3000 feet MSL.

Narrative: I filed an IFR flight plan due to MVFR conditions. Pilots have been experiencing problems picking up airborne clearances in this area; from Columbus approach below 3000 feet MSL. To be safe; I requested a void time clearance via cell phone. I was using a noise cancelling Bluetooth headset to hear over the engine noise. After a query from clearance delivery; I advised I would need at least 5 minutes to complete the run up and would depart from runway 28. I stopped on taxiway Alpha near the midfield to copy and read back the clearance. I was having trouble hearing the clearance delivery person. It was like he was moving around the room away from the phone. I turned the phone volume up all the way and was able to copy as filed; climb and maintain 3000; expect 4000 in 10; the transponder code and contact departure on 118.425. I read it back; heard 'read back correct'; but was not able to hear the void time. I was advised there was a jet inbound at a distance and direction that I don't remember. I said I would expedite my departure so I didn't ask for a repeat of the void time and began to taxi. I assumed I would have plenty of time to be off in 5 minutes or less; but did not consider the time to climb to an altitude where Columbus would hear me. The first communications I heard on 118.425 was the jet being cleared for the approach into AOH. I thought that was strange since I hadn't been able to check in yet. The controller was very busy and I didn't get a chance to talk until about 2800 feet MSL; and reception is normally poor until higher. It seemed like about an extra minute. I wasn't concerned as I expected I had a clearance and they probably already saw my squawk on radar. Fortunately; I was clear of clouds and the ceiling better than expected. I called reporting 2800; climbing 3000; looking for higher. The controller advised my clearance was void minutes ago. I leveled at 3000 and made sure I could maintain VFR. I did not respond as I began to weigh my options. In a little bit he called me back; had me ident and cleared me to 4000. I did go IMC before reaching 4000. The remainder of the flight was without incident.5 minutes is enough time to complete the checklist and get airborne but not enough time to get to altitude. It tempts pilots to rush through the pre-takeoff checklist and make mistakes. I resisted that urge and did the best I could do safely. I wasn't watching the clock I was flying the airplane. Being able to communicate directly with the controller via VHF radio in the airplane is substantially better than trying to hear over engine noise and the distraction of operating a cell phone in the airplane. I have tried putting the phone under the ear cup of the headset and even invested in a blue tooth headset but it does not compare. I believe that undependable communications contributed to this problem and represents an unacceptable risk. Previously there was a link to Indy center before that worked very well from the ground up. I think if Columbus approach should had the same capability it would mitigate this risk before someone gets hurt. When it comes to clearances and dependable communications there should be no compromise.

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.