Operation deviation.

Attributes
ACN	288987
Time
Date	199411
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : myr
State Reference	SC
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : myr tower : myr artcc : zob
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	climbout : initial
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 16000 flight time type : 2500
ASRS Report	288987
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

We requested the IFR clearance from myr ground control. We were given the following 'cleared as filed, maintain runway heading, climb and maintain 2000 ft, expect 12000 ft 10 mins after takeoff, departure on 119.2 squawk 2733.' I read the clearance back, I then checked our filed routing. It was myr, fay, rdu. After takeoff we were cleared 'on course' (10000 ft) and started toward fay VOR. The controller questioned our routing saying he had us going over ilm VOR. He stated that regardless of what was filed the 'computer' would only give the ilm- blade 3 routing. We advised the ATC controller of the clearance we had received. The 'as filed clearance' can lead to errors in this type of situation. ATC should be required to give a fix after the as filed clearance. If myr ATC is aware of the 'computer' problem, they should exercise care in issuing 'as filed clrncs.'

Original NASA ASRS Text

Title: OP DEV.

Narrative: WE REQUESTED THE IFR CLRNC FROM MYR GND CTL. WE WERE GIVEN THE FOLLOWING 'CLRED AS FILED, MAINTAIN RWY HDG, CLB AND MAINTAIN 2000 FT, EXPECT 12000 FT 10 MINS AFTER TKOF, DEP ON 119.2 SQUAWK 2733.' I READ THE CLRNC BACK, I THEN CHKED OUR FILED RTING. IT WAS MYR, FAY, RDU. AFTER TKOF WE WERE CLRED 'ON COURSE' (10000 FT) AND STARTED TOWARD FAY VOR. THE CTLR QUESTIONED OUR RTING SAYING HE HAD US GOING OVER ILM VOR. HE STATED THAT REGARDLESS OF WHAT WAS FILED THE 'COMPUTER' WOULD ONLY GIVE THE ILM- BLADE 3 RTING. WE ADVISED THE ATC CTLR OF THE CLRNC WE HAD RECEIVED. THE 'AS FILED CLRNC' CAN LEAD TO ERRORS IN THIS TYPE OF SIT. ATC SHOULD BE REQUIRED TO GIVE A FIX AFTER THE AS FILED CLRNC. IF MYR ATC IS AWARE OF THE 'COMPUTER' PROB, THEY SHOULD EXERCISE CARE IN ISSUING 'AS FILED CLRNCS.'

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.