Narrative:

The problem arose from a series of errors in communication. We were under the assumption we had properly obtained an IFR to VFR clearance from ukiah FSS, to depart mendocino county airport for the VOR at mendocino, and cancel in VFR conditions. The only cloud layer was 600 ft thick and we were on top in seconds. When we called oakland center to cancel IFR, they had no clearance to cancel. There had been a mistake. Before engine start I specifically asked if we had a clearance IFR to VFR. My student said yes, to the mendocino VOR at 5000 ft. We had no void time. This should have alerted me. My student filed the proper flight plan, but later stated he never actually heard a clearance. His mistake. The specialist at ukiah FSS was abrupt with my student, who asked 3 times to make sure we had our clearance, and was told you're fine, have a nice day. This was his mistake. The specialist should have made clear how to obtain the clearance at mendocino, as they are the ones familiar with the exact procedure there. The airport has no approachs or departure procedures so you cannot verify your instructions against anything. In retrospect, I shall never depart IFR unless I hear and personally verify all ATC communications and clrncs. The only corrective action was a call I had to make to the supervisor at oakland center. The lesson from all this is that strict rules of communication must be followed by all parties. The error occurred because all links of the chain broke. There was no incident, no intentional violation of any far, nor involvement of any other aircraft, nor hazard to safety, we all just made mistakes.

Related reports:

Google
 

Original NASA ASRS Text

Title: IMC IN VFR FLT WHEN INSTRUCTOR PLT DISCOVERS THAT THEIR IFR FLT PLAN WAS NEVER ACTIVATED WITH ATC, THROUGH THE FSS AS REQUIRED.

Narrative: THE PROBLEM AROSE FROM A SERIES OF ERRORS IN COM. WE WERE UNDER THE ASSUMPTION WE HAD PROPERLY OBTAINED AN IFR TO VFR CLRNC FROM UKIAH FSS, TO DEPART MENDOCINO COUNTY ARPT FOR THE VOR AT MENDOCINO, AND CANCEL IN VFR CONDITIONS. THE ONLY CLOUD LAYER WAS 600 FT THICK AND WE WERE ON TOP IN SECONDS. WHEN WE CALLED OAKLAND CENTER TO CANCEL IFR, THEY HAD NO CLRNC TO CANCEL. THERE HAD BEEN A MISTAKE. BEFORE ENG START I SPECIFICALLY ASKED IF WE HAD A CLRNC IFR TO VFR. MY STUDENT SAID YES, TO THE MENDOCINO VOR AT 5000 FT. WE HAD NO VOID TIME. THIS SHOULD HAVE ALERTED ME. MY STUDENT FILED THE PROPER FLT PLAN, BUT LATER STATED HE NEVER ACTUALLY HEARD A CLRNC. HIS MISTAKE. THE SPECIALIST AT UKIAH FSS WAS ABRUPT WITH MY STUDENT, WHO ASKED 3 TIMES TO MAKE SURE WE HAD OUR CLRNC, AND WAS TOLD YOU'RE FINE, HAVE A NICE DAY. THIS WAS HIS MISTAKE. THE SPECIALIST SHOULD HAVE MADE CLR HOW TO OBTAIN THE CLRNC AT MENDOCINO, AS THEY ARE THE ONES FAMILIAR WITH THE EXACT PROC THERE. THE ARPT HAS NO APCHS OR DEP PROCS SO YOU CANNOT VERIFY YOUR INSTRUCTIONS AGAINST ANYTHING. IN RETROSPECT, I SHALL NEVER DEPART IFR UNLESS I HEAR AND PERSONALLY VERIFY ALL ATC COMS AND CLRNCS. THE ONLY CORRECTIVE ACTION WAS A CALL I HAD TO MAKE TO THE SUPVR AT OAKLAND CENTER. THE LESSON FROM ALL THIS IS THAT STRICT RULES OF COM MUST BE FOLLOWED BY ALL PARTIES. THE ERROR OCCURRED BECAUSE ALL LINKS OF THE CHAIN BROKE. THERE WAS NO INCIDENT, NO INTENTIONAL VIOLATION OF ANY FAR, NOR INVOLVEMENT OF ANY OTHER ACFT, NOR HAZARD TO SAFETY, WE ALL JUST MADE MISTAKES.

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.