Medium large transport flew the wrong route.

Attributes
ACN	93187
Time
Date	198808
Day	Fri
Local Time Of Day	0001 To 0600
Place
Locale Reference	atc facility : hbu
State Reference	CO
Altitude	msl bound lower : 33000 msl bound upper : 33000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other
Flight Phase	cruise other
Route In Use	enroute airway : j146 enroute airway : j128
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 215 flight time total : 7900 flight time type : 230
ASRS Report	93187
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I called clearance delivery in las for our clearance to ord. There was no flight plan in the computer. I called our company operations in las and asked them to call dispatch and request them to file another plan. Meanwhile our scheduled departure time had come and gone. Clearance delivery suggested that we call rno FSS and file the flight plan ourselves, which we did. The routing we filed was different than the one filed by the company. We filed J146 to pawnee city, the company filed J146 to blue mesa, then J128 dbq. When we finally received our clearance we received the standard 'cleared as filed' clearance, we assumed that the clearance was for the flight plan we filed, but apparently it was generated from the company filed plan. For obvious reasons at blue mesa VORTAC we proceeded out J146 as opposed to J128. At approximately 17 mi out of blue mesa on J146, ZDV called us and asked about our routing. After a short discussion about our routing, he amended our routing to J146 pawnee city, etc. I do not believe there was a conflict of traffic. Solution: when a potential exists for confusion on routings or altitudes, the crew should ask for a full route clearance. The controller working clearance delivery should also be aware of possible confusion when the normally filed flight plan is not in the computer and he requests the crew to file it.

Original NASA ASRS Text

Title: MLG FLEW THE WRONG ROUTE.

Narrative: I CALLED CLRNC DELIVERY IN LAS FOR OUR CLRNC TO ORD. THERE WAS NO FLT PLAN IN THE COMPUTER. I CALLED OUR COMPANY OPS IN LAS AND ASKED THEM TO CALL DISPATCH AND REQUEST THEM TO FILE ANOTHER PLAN. MEANWHILE OUR SCHEDULED DEP TIME HAD COME AND GONE. CLRNC DELIVERY SUGGESTED THAT WE CALL RNO FSS AND FILE THE FLT PLAN OURSELVES, WHICH WE DID. THE ROUTING WE FILED WAS DIFFERENT THAN THE ONE FILED BY THE COMPANY. WE FILED J146 TO PAWNEE CITY, THE COMPANY FILED J146 TO BLUE MESA, THEN J128 DBQ. WHEN WE FINALLY RECEIVED OUR CLRNC WE RECEIVED THE STANDARD 'CLRED AS FILED' CLRNC, WE ASSUMED THAT THE CLRNC WAS FOR THE FLT PLAN WE FILED, BUT APPARENTLY IT WAS GENERATED FROM THE COMPANY FILED PLAN. FOR OBVIOUS REASONS AT BLUE MESA VORTAC WE PROCEEDED OUT J146 AS OPPOSED TO J128. AT APPROX 17 MI OUT OF BLUE MESA ON J146, ZDV CALLED US AND ASKED ABOUT OUR ROUTING. AFTER A SHORT DISCUSSION ABOUT OUR ROUTING, HE AMENDED OUR ROUTING TO J146 PAWNEE CITY, ETC. I DO NOT BELIEVE THERE WAS A CONFLICT OF TFC. SOLUTION: WHEN A POTENTIAL EXISTS FOR CONFUSION ON ROUTINGS OR ALTS, THE CREW SHOULD ASK FOR A FULL ROUTE CLRNC. THE CTLR WORKING CLRNC DELIVERY SHOULD ALSO BE AWARE OF POSSIBLE CONFUSION WHEN THE NORMALLY FILED FLT PLAN IS NOT IN THE COMPUTER AND HE REQUESTS THE CREW TO FILE IT.

Data retrieved from NASA's ASRS site as of August 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.