A B767-300 cargo flight is reported by ZID in accord with the filed flight plan from dispatcher who ...

Attributes
ACN	537516
Time
Date	200202
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : pxv.vortac
State Reference	IN
Altitude	msl single value : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude
Route In Use	enroute airway : v4.airway
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : cfi pilot : atp pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 100 flight time total : 12000 flight time type : 900
ASRS Report	537516
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : company policies non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory
Consequence	faa : reviewed incident with flight crew other
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Company
Primary Problem	Company
Air Traffic Incident	Pilot Deviation

Narrative:

Climbing out en route, ATC cleared us to vih, which was not on our route of flight as indicated on our flight release. We were then asked what we showed to be our route of flight, and it differed with the route filed with ATC via ACARS. We asked our dispatcher why this was so, and were told previous dispatcher had changed the routing and filed the change with ATC. We were not informed of the change. Note: this happened during, or around, the time of a shift change in the dispatch office according to our present (new) dispatcher. We received our clearance via pre departure clearance on ACARS. Our ACARS pre departure clearance ATC clearance was: V4 pxn, then as filed on page 1 along with the departure procedure, departure frequency and altitude to maintain. Unfortunately, we are not (and I should stress, I am not) in the habit of cycling through all the ACARS pages for each message, pre departure clearance, etc. The extra, or other, pages often contain no information at all, as was the case this day on page 3 of pre departure clearance which contains only the line 'end of clearance' which was obvious on page 2 (previous page). In summary: 1) we had a communication breakdown between the captain and dispatcher, who share joint dispatch responsibility. The dispatcher changed our filed route with ATC and did not inform us. I am filing a company report to investigate how this happened. 2) we had a chance to 'catch' the discrepancy by viewing all the pre departure clearance pages in our ACARS, but failed to do so. I should note that many of the airports we fly into do not have pre departure clearance capability, so we would have had no way of knowing there was a different route filed. Plan of corrective actions: 1) always xchk flight release ATC route with all pages of ACARS pre departure clearance. 2) post on our union safety board for all crews to be aware of this type incident and suggested prevention.

Original NASA ASRS Text

Title: A B767-300 CARGO FLT IS RPTED BY ZID IN ACCORD WITH THE FILED FLT PLAN FROM DISPATCHER WHO HAD NOT ADVISED THE CAPT OF THE NEW FLT PLAN DEP LOU, KY.

Narrative: CLBING OUT ENRTE, ATC CLRED US TO VIH, WHICH WAS NOT ON OUR RTE OF FLT AS INDICATED ON OUR FLT RELEASE. WE WERE THEN ASKED WHAT WE SHOWED TO BE OUR RTE OF FLT, AND IT DIFFERED WITH THE RTE FILED WITH ATC VIA ACARS. WE ASKED OUR DISPATCHER WHY THIS WAS SO, AND WERE TOLD PREVIOUS DISPATCHER HAD CHANGED THE ROUTING AND FILED THE CHANGE WITH ATC. WE WERE NOT INFORMED OF THE CHANGE. NOTE: THIS HAPPENED DURING, OR AROUND, THE TIME OF A SHIFT CHANGE IN THE DISPATCH OFFICE ACCORDING TO OUR PRESENT (NEW) DISPATCHER. WE RECEIVED OUR CLRNC VIA PDC ON ACARS. OUR ACARS PDC ATC CLRNC WAS: V4 PXN, THEN AS FILED ON PAGE 1 ALONG WITH THE DEP PROC, DEP FREQ AND ALT TO MAINTAIN. UNFORTUNATELY, WE ARE NOT (AND I SHOULD STRESS, I AM NOT) IN THE HABIT OF CYCLING THROUGH ALL THE ACARS PAGES FOR EACH MESSAGE, PDC, ETC. THE EXTRA, OR OTHER, PAGES OFTEN CONTAIN NO INFO AT ALL, AS WAS THE CASE THIS DAY ON PAGE 3 OF PDC WHICH CONTAINS ONLY THE LINE 'END OF CLRNC' WHICH WAS OBVIOUS ON PAGE 2 (PREVIOUS PAGE). IN SUMMARY: 1) WE HAD A COM BREAKDOWN BTWN THE CAPT AND DISPATCHER, WHO SHARE JOINT DISPATCH RESPONSIBILITY. THE DISPATCHER CHANGED OUR FILED RTE WITH ATC AND DID NOT INFORM US. I AM FILING A COMPANY RPT TO INVESTIGATE HOW THIS HAPPENED. 2) WE HAD A CHANCE TO 'CATCH' THE DISCREPANCY BY VIEWING ALL THE PDC PAGES IN OUR ACARS, BUT FAILED TO DO SO. I SHOULD NOTE THAT MANY OF THE ARPTS WE FLY INTO DO NOT HAVE PDC CAPABILITY, SO WE WOULD HAVE HAD NO WAY OF KNOWING THERE WAS A DIFFERENT RTE FILED. PLAN OF CORRECTIVE ACTIONS: 1) ALWAYS XCHK FLT RELEASE ATC RTE WITH ALL PAGES OF ACARS PDC. 2) POST ON OUR UNION SAFETY BOARD FOR ALL CREWS TO BE AWARE OF THIS TYPE INCIDENT AND SUGGESTED PREVENTION.

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.

A B767-300 cargo flight is reported by ZID in accord with the filed flight plan from dispatcher who had not advised the captain of the new flight plan departure lou, ky.