Narrative:

Chain of events: our part 121 flight was scheduled to depart morgantown municipal airport (mgw) for clarksburg/benedum airport (ckb). We would then pick up passenger at ckb, and continue on to parkersburg wood county wilson airport (pkb). Earlier that day, our flight had been delayed 1 hour for maintenance, so we arrived at mgw 1 hour behind schedule. After arriving in mgw, I checked the passenger loads for the next legs to ckb and pkb, and the computer showed zero passenger. I discussed with dispatch the possibility of canceling the stop in ckb and going direct to pkb, so that we could hand off the aircraft to the next crew a little bit closer to schedule. Dispatch agreed, and said they would send over a release direct from mgw to pkb. I received the release and we departed mgw for pkb. After a quick climb to cruise on a westerly heading for VOR at parkersburg (jpu VOR), ATC asked us what our heading was for ckb VOR. We told the controller we were tracking direct to jpu. He then asked us if we were cleared as filed, and we responded 'affirmative.' I then looked at the flight plan on the release and realized our company filed our flight route to overfly ckb VOR before proceeding on to jpu VOR. Ckb VOR was about 16 mi south of our departure point. I then immediately requested 'present position direct parkersburg' and apologized to the controller for misunderstanding the clearance. ATC granted us our request for direct pkb. Human performance considerations: 1) failing to verify flight route on release due to the compelling feeling to 'rush and catch up to the schedule.' 2) first officer's lack of experience and assertiveness. The first officer had been on line for about 1 month and was new. She did not question our routing when I briefed the departure route. 3) fatigue. This was our 38TH leg, 30TH flight hour, and 63RD duty hour in 5 days of flying, including one reduced rest.

Related reports:

Google
 

Original NASA ASRS Text

Title: B190 CREW HAD TRACK DEV.

Narrative: CHAIN OF EVENTS: OUR PART 121 FLT WAS SCHEDULED TO DEPART MORGANTOWN MUNICIPAL ARPT (MGW) FOR CLARKSBURG/BENEDUM ARPT (CKB). WE WOULD THEN PICK UP PAX AT CKB, AND CONTINUE ON TO PARKERSBURG WOOD COUNTY WILSON ARPT (PKB). EARLIER THAT DAY, OUR FLT HAD BEEN DELAYED 1 HR FOR MAINT, SO WE ARRIVED AT MGW 1 HR BEHIND SCHEDULE. AFTER ARRIVING IN MGW, I CHKED THE PAX LOADS FOR THE NEXT LEGS TO CKB AND PKB, AND THE COMPUTER SHOWED ZERO PAX. I DISCUSSED WITH DISPATCH THE POSSIBILITY OF CANCELING THE STOP IN CKB AND GOING DIRECT TO PKB, SO THAT WE COULD HAND OFF THE ACFT TO THE NEXT CREW A LITTLE BIT CLOSER TO SCHEDULE. DISPATCH AGREED, AND SAID THEY WOULD SEND OVER A RELEASE DIRECT FROM MGW TO PKB. I RECEIVED THE RELEASE AND WE DEPARTED MGW FOR PKB. AFTER A QUICK CLB TO CRUISE ON A WESTERLY HDG FOR VOR AT PARKERSBURG (JPU VOR), ATC ASKED US WHAT OUR HDG WAS FOR CKB VOR. WE TOLD THE CTLR WE WERE TRACKING DIRECT TO JPU. HE THEN ASKED US IF WE WERE CLRED AS FILED, AND WE RESPONDED 'AFFIRMATIVE.' I THEN LOOKED AT THE FLT PLAN ON THE RELEASE AND REALIZED OUR COMPANY FILED OUR FLT RTE TO OVERFLY CKB VOR BEFORE PROCEEDING ON TO JPU VOR. CKB VOR WAS ABOUT 16 MI S OF OUR DEP POINT. I THEN IMMEDIATELY REQUESTED 'PRESENT POS DIRECT PARKERSBURG' AND APOLOGIZED TO THE CTLR FOR MISUNDERSTANDING THE CLRNC. ATC GRANTED US OUR REQUEST FOR DIRECT PKB. HUMAN PERFORMANCE CONSIDERATIONS: 1) FAILING TO VERIFY FLT RTE ON RELEASE DUE TO THE COMPELLING FEELING TO 'RUSH AND CATCH UP TO THE SCHEDULE.' 2) FO'S LACK OF EXPERIENCE AND ASSERTIVENESS. THE FO HAD BEEN ON LINE FOR ABOUT 1 MONTH AND WAS NEW. SHE DID NOT QUESTION OUR ROUTING WHEN I BRIEFED THE DEP RTE. 3) FATIGUE. THIS WAS OUR 38TH LEG, 30TH FLT HR, AND 63RD DUTY HR IN 5 DAYS OF FLYING, INCLUDING ONE REDUCED REST.

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.