Reporter accepts clearance that erroneously utilizes a VOR that is notamed OTS from pqi.

Attributes
ACN	439910
Time
Date	199906
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bos.airport
State Reference	MA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Operating Under FAR Part	Part 135
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : atp
Experience	flight time last 90 days : 210 flight time total : 3300 flight time type : 1690
ASRS Report	439910
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : multi engine
Events
Anomaly	non adherence : published procedure non adherence : far
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : became reoriented flight crew : returned to intended or assigned course none taken : detected after the fact
Supplementary
Problem Areas	Navigational Facility ATC Human Performance Airspace Structure Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Our filed route was pqi.J55.ene...with J55 predicated on the use of pqi VOR. Our ATC clearance was pqi.J55.ene...received by ZBW. This is a canned route for us and ZBW normally gives us this clearance (final destination bos). The problem is the pqi VOR is OTS and has been for over 2 weeks. I missed the clearance above until after we received it and was taking off. Being VFR for the entire trip and knowing that our usual request for a vector direct to ene would be honored, I continued the flight on schedule. I was also thoroughly familiar with the alternate clearance we've been using. If a no communication situation were to arise, I know no additional threat would be an issue because of the crew's familiarity with the region, the day's perfect WX, and ATC's expectations for the flight. This won't happen again.

Original NASA ASRS Text

Title: RPTR ACCEPTS CLRNC THAT ERRONEOUSLY UTILIZES A VOR THAT IS NOTAMED OTS FROM PQI.

Narrative: OUR FILED RTE WAS PQI.J55.ENE...WITH J55 PREDICATED ON THE USE OF PQI VOR. OUR ATC CLRNC WAS PQI.J55.ENE...RECEIVED BY ZBW. THIS IS A CANNED RTE FOR US AND ZBW NORMALLY GIVES US THIS CLRNC (FINAL DEST BOS). THE PROB IS THE PQI VOR IS OTS AND HAS BEEN FOR OVER 2 WKS. I MISSED THE CLRNC ABOVE UNTIL AFTER WE RECEIVED IT AND WAS TAKING OFF. BEING VFR FOR THE ENTIRE TRIP AND KNOWING THAT OUR USUAL REQUEST FOR A VECTOR DIRECT TO ENE WOULD BE HONORED, I CONTINUED THE FLT ON SCHEDULE. I WAS ALSO THOROUGHLY FAMILIAR WITH THE ALTERNATE CLRNC WE'VE BEEN USING. IF A NO COM SIT WERE TO ARISE, I KNOW NO ADDITIONAL THREAT WOULD BE AN ISSUE BECAUSE OF THE CREW'S FAMILIARITY WITH THE REGION, THE DAY'S PERFECT WX, AND ATC'S EXPECTATIONS FOR THE FLT. THIS WON'T HAPPEN AGAIN.

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.