Air carrier fails to notify numerous flcs of route change in 'as filed clearance' near phl.

Attributes
ACN	441786
Time
Date	199906
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : cyn.vor
State Reference	NY
Altitude	msl single value : 17000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny.artcc
Make Model Name	Medium Transport, High Wing, 2 Turboprop Eng
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	cruise : level
Route In Use	arrival star : bouno 3
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : multi engine pilot : instrument pilot : commercial
Experience	flight time last 90 days : 120 flight time total : 2800 flight time type : 120
ASRS Report	441786
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : clearance non adherence : company policies non adherence : published procedure other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : became reoriented flight crew : returned to original clearance none taken : detected after the fact
Consequence	faa : investigated other
Supplementary
Problem Areas	Flight Crew Human Performance Company Airspace Structure
Primary Problem	Company

Narrative:

We are filed from phl-hpn via the bound 3 arrival. Our clearance was received from phl clearance 'phl 6 as filed, maintain 5000 ft, departure 119.75, squawk XXXX.' we verified with clearance our first fix was 'drift intersection.' reaching cyn VOR, we turned to the cyn 063 degree radial, instead of following V312 (100 degree radial) drift intersection, V139, riced, riced 2, hpn, beginning the bound 3 arrival. The controller asked why we followed the 063 degree radial and stated this was the third time in a row that this occurred. He then requested our company phone number. We responded for him to stand by while we reinitialized the LNAV computer and verify its operation. We then turned to a heading of 110 degrees to intercept the 100 degree radial, and gave the controller the company phone number. He responded with a heading of 120 degrees to reintercept. During this time there was no TCASII alert given or TA by ATC. We believe that we were no more than 4 NM of the ctn VOR before turning back onto the radial. The company did not provide us with any additional warning of the route change prior to the flight.

Original NASA ASRS Text

Title: ACR FAILS TO NOTIFY NUMEROUS FLCS OF RTE CHANGE IN 'AS FILED CLRNC' NEAR PHL.

Narrative: WE ARE FILED FROM PHL-HPN VIA THE BOUND 3 ARR. OUR CLRNC WAS RECEIVED FROM PHL CLRNC 'PHL 6 AS FILED, MAINTAIN 5000 FT, DEP 119.75, SQUAWK XXXX.' WE VERIFIED WITH CLRNC OUR FIRST FIX WAS 'DRIFT INTXN.' REACHING CYN VOR, WE TURNED TO THE CYN 063 DEG RADIAL, INSTEAD OF FOLLOWING V312 (100 DEG RADIAL) DRIFT INTXN, V139, RICED, RICED 2, HPN, BEGINNING THE BOUND 3 ARR. THE CTLR ASKED WHY WE FOLLOWED THE 063 DEG RADIAL AND STATED THIS WAS THE THIRD TIME IN A ROW THAT THIS OCCURRED. HE THEN REQUESTED OUR COMPANY PHONE NUMBER. WE RESPONDED FOR HIM TO STAND BY WHILE WE REINITIALIZED THE LNAV COMPUTER AND VERIFY ITS OP. WE THEN TURNED TO A HDG OF 110 DEGS TO INTERCEPT THE 100 DEG RADIAL, AND GAVE THE CTLR THE COMPANY PHONE NUMBER. HE RESPONDED WITH A HDG OF 120 DEGS TO REINTERCEPT. DURING THIS TIME THERE WAS NO TCASII ALERT GIVEN OR TA BY ATC. WE BELIEVE THAT WE WERE NO MORE THAN 4 NM OF THE CTN VOR BEFORE TURNING BACK ONTO THE RADIAL. THE COMPANY DID NOT PROVIDE US WITH ANY ADDITIONAL WARNING OF THE RTE CHANGE PRIOR TO THE FLT.

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.