Air carrier medium large transport track deviation.

Attributes
ACN	107920
Time
Date	198904
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : roc
State Reference	NY
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny tower : roc
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	cruise other
Route In Use	enroute airway : v93 enroute airway : v499
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 120 flight time total : 6500 flight time type : 2500
ASRS Report	107920
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 200 flight time total : 14000 flight time type : 2700
ASRS Report	108192
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	faa : investigated
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

Departed roc XA15 via runway heading, as filed, maintain 10000', expect FL210 in 10 mins. En route just south of lancaster ZNY asked us if we were navigating V93. We replied, 'no, V499 as filed.' he stated that we were supposed to be on V93 and cleared us direct bwi. We checked our filed routing as per our dispatch release and saw that the controller was wrong--we were filed V499. When ATC handed us off to bwi he made a smart remark that we would be hearing from him. The captain then stated that we had been cleared as filed and that was V499. ATC responded that we were supposed to be on V93 and that the FAA would be in touch with us. Upon landing we checked with our company and found that a mistake had been made and it was 2-FOLD. From XA00 to XC00 that flight was supposed to operate on V93 as ATC stated. Our company paperwork (dispatch release) was supposed to reflect that change and it did not. The company said this was due to a change over to a new computer system. The second mistake was made by ATC. Per our company rep, we were told that during those hours XA00-XC00, ATC was supposed to use a full route readout and not 'cleared as filed.' we did not receive a full readout of clearance and therefore flew the route as per our dispatch release. I feel the cause of this problem ultimately lies with our company and ATC. There is no excuse for our computer printing out erroneous routings and if ATC is required in certain instances to issue full route clrncs, there is no excuse for any variation in these procedures. Callback conversation with reporter acn 108192 revealed the following: contacted the reporter to obtain further information on his incident. He said that the 2 hour V93 routing is being applied at all upstate ny airports for departures going to the ny-dc airports. Said that ZNY was going to notify the upstate ny ATC facs to issue full route clrncs until the company computers are amended.

Original NASA ASRS Text

Title: ACR MLG TRACK DEVIATION.

Narrative: DEPARTED ROC XA15 VIA RWY HDG, AS FILED, MAINTAIN 10000', EXPECT FL210 IN 10 MINS. ENRTE JUST S OF LANCASTER ZNY ASKED US IF WE WERE NAVIGATING V93. WE REPLIED, 'NO, V499 AS FILED.' HE STATED THAT WE WERE SUPPOSED TO BE ON V93 AND CLRED US DIRECT BWI. WE CHKED OUR FILED ROUTING AS PER OUR DISPATCH RELEASE AND SAW THAT THE CTLR WAS WRONG--WE WERE FILED V499. WHEN ATC HANDED US OFF TO BWI HE MADE A SMART REMARK THAT WE WOULD BE HEARING FROM HIM. THE CAPT THEN STATED THAT WE HAD BEEN CLRED AS FILED AND THAT WAS V499. ATC RESPONDED THAT WE WERE SUPPOSED TO BE ON V93 AND THAT THE FAA WOULD BE IN TOUCH WITH US. UPON LNDG WE CHKED WITH OUR COMPANY AND FOUND THAT A MISTAKE HAD BEEN MADE AND IT WAS 2-FOLD. FROM XA00 TO XC00 THAT FLT WAS SUPPOSED TO OPERATE ON V93 AS ATC STATED. OUR COMPANY PAPERWORK (DISPATCH RELEASE) WAS SUPPOSED TO REFLECT THAT CHANGE AND IT DID NOT. THE COMPANY SAID THIS WAS DUE TO A CHANGE OVER TO A NEW COMPUTER SYS. THE SECOND MISTAKE WAS MADE BY ATC. PER OUR COMPANY REP, WE WERE TOLD THAT DURING THOSE HRS XA00-XC00, ATC WAS SUPPOSED TO USE A FULL ROUTE READOUT AND NOT 'CLRED AS FILED.' WE DID NOT RECEIVE A FULL READOUT OF CLRNC AND THEREFORE FLEW THE ROUTE AS PER OUR DISPATCH RELEASE. I FEEL THE CAUSE OF THIS PROB ULTIMATELY LIES WITH OUR COMPANY AND ATC. THERE IS NO EXCUSE FOR OUR COMPUTER PRINTING OUT ERRONEOUS ROUTINGS AND IF ATC IS REQUIRED IN CERTAIN INSTANCES TO ISSUE FULL ROUTE CLRNCS, THERE IS NO EXCUSE FOR ANY VARIATION IN THESE PROCS. CALLBACK CONVERSATION WITH RPTR ACN 108192 REVEALED THE FOLLOWING: CONTACTED THE RPTR TO OBTAIN FURTHER INFO ON HIS INCIDENT. HE SAID THAT THE 2 HR V93 ROUTING IS BEING APPLIED AT ALL UPSTATE NY ARPTS FOR DEPS GOING TO THE NY-DC ARPTS. SAID THAT ZNY WAS GOING TO NOTIFY THE UPSTATE NY ATC FACS TO ISSUE FULL ROUTE CLRNCS UNTIL THE COMPANY COMPUTERS ARE AMENDED.

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.