Track deviation results when commuter flight crew fails to check flight plan routing versus anticipa...

Attributes
ACN	461300
Time
Date	200001
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : flg.airport
State Reference	AZ
Altitude	msl single value : 13000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zab.artcc
Operator	common carrier : air carrier
Make Model Name	Beech 1900
Navigation In Use	other vortac
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial
Experience	flight time last 90 days : 290 flight time total : 970 flight time type : 710
ASRS Report	461300
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : instrument pilot : atp
Experience	flight time last 90 days : 56 flight time total : 4800 flight time type : 4500
ASRS Report	461680
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance Company
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departed flagstaff on a VFR day. Clearance given from tower (clearance delivery) was as filed. That used to be V321. The captain and I didn't check to see if there had been a new flight plan routing on our release. We intercepted flg VOR 172 degree radial for V321. This was incorrect. We were filed direct to drake, karlo 7 arrival to phx. We were both unaware of our usually standard routing not being our filed routing. It is both our faults for not checking routing on release. The company could have posted notices in appropriate stations stating that there were to be routing changes. It was ultimately our error, as the pilots. ZAB contacted us about 10 mi southeast of flg VOR. He asked us our desired routing and we told him V321, since that's what we were flying. He accommodated us and there were no traffic alerts or any trouble from the situation.

Original NASA ASRS Text

Title: TRACK DEV RESULTS WHEN COMMUTER FLC FAILS TO CHK FLT PLAN ROUTING VERSUS ANTICIPATED ROUTING.

Narrative: DEPARTED FLAGSTAFF ON A VFR DAY. CLRNC GIVEN FROM TWR (CLRNC DELIVERY) WAS AS FILED. THAT USED TO BE V321. THE CAPT AND I DIDN'T CHK TO SEE IF THERE HAD BEEN A NEW FLT PLAN ROUTING ON OUR RELEASE. WE INTERCEPTED FLG VOR 172 DEG RADIAL FOR V321. THIS WAS INCORRECT. WE WERE FILED DIRECT TO DRAKE, KARLO 7 ARR TO PHX. WE WERE BOTH UNAWARE OF OUR USUALLY STANDARD ROUTING NOT BEING OUR FILED ROUTING. IT IS BOTH OUR FAULTS FOR NOT CHKING ROUTING ON RELEASE. THE COMPANY COULD HAVE POSTED NOTICES IN APPROPRIATE STATIONS STATING THAT THERE WERE TO BE ROUTING CHANGES. IT WAS ULTIMATELY OUR ERROR, AS THE PLTS. ZAB CONTACTED US ABOUT 10 MI SE OF FLG VOR. HE ASKED US OUR DESIRED ROUTING AND WE TOLD HIM V321, SINCE THAT'S WHAT WE WERE FLYING. HE ACCOMMODATED US AND THERE WERE NO TFC ALERTS OR ANY TROUBLE FROM THE SIT.

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.

Track deviation results when commuter flight crew fails to check flight plan routing versus anticipated routing.