Narrative:

Filed VFR flight plan with grand junction, co, before departure to bellingham, wa. Called malad, identification, on 122.1 and asked to change to IFR. Malad took information and instructed me to contact slc center at 50 mi fix 130 degree right for IFR. Flight proceeded normally. After landing I became concerned that my VFR flight plan might not have been cancelled and called FSS in bli. I was informed that it had not and was almost up to the point where search would have started. Both pilot and FSS personnel should be clear about whether or not a flight plan is cancelled when another is filed or changed to IFR. This could have caused some problems if I had not become uneasy about it. This seems much more likely to occur when the flight plan is changed in flight.

Related reports:

Google
 

Original NASA ASRS Text

Title: HIGH TIME PLT FILES VFR AND THEN REFILES IFR AFTER AIRBORNE BUT FORGETS TO CANCEL VFR FLT PLAN AFTER ARRIVING AT DESTINATION.

Narrative: FILED VFR FLT PLAN WITH GRAND JUNCTION, CO, BEFORE DEP TO BELLINGHAM, WA. CALLED MALAD, ID, ON 122.1 AND ASKED TO CHANGE TO IFR. MALAD TOOK INFO AND INSTRUCTED ME TO CONTACT SLC CTR AT 50 MI FIX 130 DEG R FOR IFR. FLT PROCEEDED NORMALLY. AFTER LNDG I BECAME CONCERNED THAT MY VFR FLT PLAN MIGHT NOT HAVE BEEN CANCELLED AND CALLED FSS IN BLI. I WAS INFORMED THAT IT HAD NOT AND WAS ALMOST UP TO THE POINT WHERE SEARCH WOULD HAVE STARTED. BOTH PLT AND FSS PERSONNEL SHOULD BE CLR ABOUT WHETHER OR NOT A FLT PLAN IS CANCELLED WHEN ANOTHER IS FILED OR CHANGED TO IFR. THIS COULD HAVE CAUSED SOME PROBS IF I HAD NOT BECOME UNEASY ABOUT IT. THIS SEEMS MUCH MORE LIKELY TO OCCUR WHEN THE FLT PLAN IS CHANGED IN FLT.

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.