Narrative:

I was departing kalispell, mt, fca, an uncontrolled airport. On the approach plate there was no clearance delivery frequency. Salt lake city approach frequency of 133.4 was listed on the plate. At many uncontrolled airports it is difficult to pick up clearance on the ground. It was a clear and unrestr visibility day with light traffic at the airport. I did not see the need to try to get my clearance before departure because of the conditions. After departing the pattern I contacted salt lake approach on 133.4 and told them that I had an IFR on file from fca and bli. The controller came back and said that I was cleared as filed climb to FL220. This is all that I wrote down on my pad. That is exactly what I was doing when I requested FL260. I was not sure on what he told me so I asked again if I was cleared FL260 or I should stay at FL220. This is when the problem was discovered. He thought that I was on the ground and I thought that I was cleared as filed. When he asked me what I was squawking I realized that it was still squawking 1200 VFR at FL220. I told him that I was already level FL220 and then he told me what my code was. I did have my transponder on. I did put in the correct code and I was soon handed off to another controller. What I believe really caused the problem is lack of communication. I thought that I was cleared as filed to climb to FL220 and I am sure that that is what I read back to the controller. I did not write down a code to squawk and I am sure I did not tell him a code. Part of this is my assuming he knows that I am airborne on such a beautiful day in the middle of nowhere. Part of this is the controller's fault assuming that I am on the ground. I am also very certain that I read back the clearance cleared as filed climb or climbing FL220. I am sure that he did not get a code back or verification from me on a hold for release, so I read back the clearance as I heard it and was not corrected. What can be done to correct the problem on my end is: to state if I am airborne or on the ground when requesting clearance. To make sure that I have a full clearance, and this is a trick that I have now learned. 'C' clearance, 'right' route, 'a' altitude, 'south' squawk, 'H' heading after departure. Make sure that I have them all. To correct the problem from the controller's side is: to ask if airborne or on the ground if not stated from the pilot. Make sure that the clearance that is read back matches the correct clearance.

Google
 

Original NASA ASRS Text

Title: CONFUSION ABOUT THE CLRNC LEADS TO ENTRY INTO CLASS A AIRSPACE WITHOUT CLRNC. ATC ASSUMED THE ACFT WAS STILL ON THE GND. THE PLT ASSUMED ATC KNEW HE WAS ALREADY AIRBORNE.

Narrative: I WAS DEPARTING KALISPELL, MT, FCA, AN UNCTLED ARPT. ON THE APCH PLATE THERE WAS NO CLRNC DELIVERY FREQ. SALT LAKE CITY APCH FREQ OF 133.4 WAS LISTED ON THE PLATE. AT MANY UNCTLED ARPTS IT IS DIFFICULT TO PICK UP CLRNC ON THE GND. IT WAS A CLR AND UNRESTR VISIBILITY DAY WITH LIGHT TFC AT THE ARPT. I DID NOT SEE THE NEED TO TRY TO GET MY CLRNC BEFORE DEP BECAUSE OF THE CONDITIONS. AFTER DEPARTING THE PATTERN I CONTACTED SALT LAKE APCH ON 133.4 AND TOLD THEM THAT I HAD AN IFR ON FILE FROM FCA AND BLI. THE CTLR CAME BACK AND SAID THAT I WAS CLRED AS FILED CLB TO FL220. THIS IS ALL THAT I WROTE DOWN ON MY PAD. THAT IS EXACTLY WHAT I WAS DOING WHEN I REQUESTED FL260. I WAS NOT SURE ON WHAT HE TOLD ME SO I ASKED AGAIN IF I WAS CLRED FL260 OR I SHOULD STAY AT FL220. THIS IS WHEN THE PROB WAS DISCOVERED. HE THOUGHT THAT I WAS ON THE GND AND I THOUGHT THAT I WAS CLRED AS FILED. WHEN HE ASKED ME WHAT I WAS SQUAWKING I REALIZED THAT IT WAS STILL SQUAWKING 1200 VFR AT FL220. I TOLD HIM THAT I WAS ALREADY LEVEL FL220 AND THEN HE TOLD ME WHAT MY CODE WAS. I DID HAVE MY XPONDER ON. I DID PUT IN THE CORRECT CODE AND I WAS SOON HANDED OFF TO ANOTHER CTLR. WHAT I BELIEVE REALLY CAUSED THE PROB IS LACK OF COM. I THOUGHT THAT I WAS CLRED AS FILED TO CLB TO FL220 AND I AM SURE THAT THAT IS WHAT I READ BACK TO THE CTLR. I DID NOT WRITE DOWN A CODE TO SQUAWK AND I AM SURE I DID NOT TELL HIM A CODE. PART OF THIS IS MY ASSUMING HE KNOWS THAT I AM AIRBORNE ON SUCH A BEAUTIFUL DAY IN THE MIDDLE OF NOWHERE. PART OF THIS IS THE CTLR'S FAULT ASSUMING THAT I AM ON THE GND. I AM ALSO VERY CERTAIN THAT I READ BACK THE CLRNC CLRED AS FILED CLB OR CLBING FL220. I AM SURE THAT HE DID NOT GET A CODE BACK OR VERIFICATION FROM ME ON A HOLD FOR RELEASE, SO I READ BACK THE CLRNC AS I HEARD IT AND WAS NOT CORRECTED. WHAT CAN BE DONE TO CORRECT THE PROB ON MY END IS: TO STATE IF I AM AIRBORNE OR ON THE GND WHEN REQUESTING CLRNC. TO MAKE SURE THAT I HAVE A FULL CLRNC, AND THIS IS A TRICK THAT I HAVE NOW LEARNED. 'C' CLRNC, 'R' RTE, 'A' ALT, 'S' SQUAWK, 'H' HEADING AFTER DEP. MAKE SURE THAT I HAVE THEM ALL. TO CORRECT THE PROB FROM THE CTLR'S SIDE IS: TO ASK IF AIRBORNE OR ON THE GND IF NOT STATED FROM THE PLT. MAKE SURE THAT THE CLRNC THAT IS READ BACK MATCHES THE CORRECT CLRNC.

Data retrieved from NASA's ASRS site as of July 2007 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.