Narrative:

During a round trip from bos-isp-bos, we were told to make a flag stop in bdr after stopping in isp. When trying to pick up our clearance from isp tower, we were told that an IFR clearance could not be found on file. Isp tower put in a clearance for us. Departing bdr, we were told by bdr tower that once again, no clearance was on file. They told us they had a clearance for the previous flight which had canceled. Bdr operations told us that we could use that clearance. Bdr tower read the clearance as 'cleared to bos via bridgehaven 5 departure, madison, as filed' with 13000 ft as a final altitude which seemed to go with our paper work which showed us filed mad V1 hfd then dreem intersection, direct boston. Climbing over mad VOR on our departure, we turned to track V1 to hfd. Approximately 8 mi north of madison, new york asked us to verify our route and told us that we should be on victor 475 to orw with 9000 ft as our final. This mix-up may be due to the 2 flight plans being filed differently, however, they have always been the same in the past as they are computer generated 'canned' flight plans. Also, the fact that we were given 13000 ft as a final would keep us away from the V-475 route to orw, then V-16 woons to boston. These conflicts may have come to me sooner had it not been the 8TH leg of our day.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC OF AN LTT FLEW WRONG FL PLAN ROUTING DUE TO ANOTHER STOP PUT INTO THE NORMAL SCHEDULED FLT THAT WAS DIFFERENT FROM THAT OF THE STORED FLT PLAN.

Narrative: DURING A ROUND TRIP FROM BOS-ISP-BOS, WE WERE TOLD TO MAKE A FLAG STOP IN BDR AFTER STOPPING IN ISP. WHEN TRYING TO PICK UP OUR CLRNC FROM ISP TWR, WE WERE TOLD THAT AN IFR CLRNC COULD NOT BE FOUND ON FILE. ISP TWR PUT IN A CLRNC FOR US. DEPARTING BDR, WE WERE TOLD BY BDR TWR THAT ONCE AGAIN, NO CLRNC WAS ON FILE. THEY TOLD US THEY HAD A CLRNC FOR THE PREVIOUS FLT WHICH HAD CANCELED. BDR OPS TOLD US THAT WE COULD USE THAT CLRNC. BDR TWR READ THE CLRNC AS 'CLRED TO BOS VIA BRIDGEHAVEN 5 DEP, MADISON, AS FILED' WITH 13000 FT AS A FINAL ALT WHICH SEEMED TO GO WITH OUR PAPER WORK WHICH SHOWED US FILED MAD V1 HFD THEN DREEM INTXN, DIRECT BOSTON. CLBING OVER MAD VOR ON OUR DEP, WE TURNED TO TRACK V1 TO HFD. APPROX 8 MI N OF MADISON, NEW YORK ASKED US TO VERIFY OUR RTE AND TOLD US THAT WE SHOULD BE ON VICTOR 475 TO ORW WITH 9000 FT AS OUR FINAL. THIS MIX-UP MAY BE DUE TO THE 2 FLT PLANS BEING FILED DIFFERENTLY, HOWEVER, THEY HAVE ALWAYS BEEN THE SAME IN THE PAST AS THEY ARE COMPUTER GENERATED 'CANNED' FLT PLANS. ALSO, THE FACT THAT WE WERE GIVEN 13000 FT AS A FINAL WOULD KEEP US AWAY FROM THE V-475 RTE TO ORW, THEN V-16 WOONS TO BOSTON. THESE CONFLICTS MAY HAVE COME TO ME SOONER HAD IT NOT BEEN THE 8TH LEG OF OUR DAY.

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.