Narrative:

Received clearance from columbus -- as filed, expect FL190 in 5 mins, FL210 in 10 mins, departure 135.6. Clearance obtained from columbus by the first officer. We departed on runway 36 at gtr. Before takeoff, I asked if we were cleared 'runway heading' or 'as filed.' first officer responded 'runway heading.' we announced our departure on 122.8. At 400 ft AGL, I switched to 135.6 and checked in with columbus departure. We continued to 2000 ft MSL on runway heading. At this point, a different controller asked us if we were cleared 'runway heading' or 'as filed.' I stated 'runway heading.' we were corrected and told to turn right to 100 degrees. We complied. We were then cleared 'as filed.' the 'as filed' clearance was direct to rome VOR. This would have incorporated a right turn after takeoff. The controller informed me that proceeding on runway heading could cause a problem with the columbus military air base's airspace. We did not have a traffic conflict or TCASII advisory. The terminology 'as filed' doesn't indicate an immediate turn as was wanted by columbus departure. They did not ask us to turn when we checked on at 400 ft AGL. There needs to be a better way for columbus to clear aircraft at gtr, for this not to occur again. Clearance needs to specify the need for the immediate turn in order to secure aircraft spacing. Callback conversation with reporter revealed the following information: reporter stated his first officer mistakenly interpreted 'as filed' departure clearance by cbm as 'runway heading.' reporter however advised company chief pilot of the situation. Corrections to the company SOP have been completed. Company personnel clarified departure procedures with cbm milfac prior to implementing SOP changes.

Related reports:

Google
 

Original NASA ASRS Text

Title: CL65 FLC CONCERNED WITH GTR DEP ROUTING WHEN CHALLENGED BY CBM MILFAC.

Narrative: RECEIVED CLRNC FROM COLUMBUS -- AS FILED, EXPECT FL190 IN 5 MINS, FL210 IN 10 MINS, DEP 135.6. CLRNC OBTAINED FROM COLUMBUS BY THE FO. WE DEPARTED ON RWY 36 AT GTR. BEFORE TKOF, I ASKED IF WE WERE CLRED 'RWY HDG' OR 'AS FILED.' FO RESPONDED 'RWY HDG.' WE ANNOUNCED OUR DEP ON 122.8. AT 400 FT AGL, I SWITCHED TO 135.6 AND CHKED IN WITH COLUMBUS DEP. WE CONTINUED TO 2000 FT MSL ON RWY HDG. AT THIS POINT, A DIFFERENT CTLR ASKED US IF WE WERE CLRED 'RWY HDG' OR 'AS FILED.' I STATED 'RWY HDG.' WE WERE CORRECTED AND TOLD TO TURN R TO 100 DEGS. WE COMPLIED. WE WERE THEN CLRED 'AS FILED.' THE 'AS FILED' CLRNC WAS DIRECT TO ROME VOR. THIS WOULD HAVE INCORPORATED A R TURN AFTER TKOF. THE CTLR INFORMED ME THAT PROCEEDING ON RWY HDG COULD CAUSE A PROB WITH THE COLUMBUS MIL AIR BASE'S AIRSPACE. WE DID NOT HAVE A TFC CONFLICT OR TCASII ADVISORY. THE TERMINOLOGY 'AS FILED' DOESN'T INDICATE AN IMMEDIATE TURN AS WAS WANTED BY COLUMBUS DEP. THEY DID NOT ASK US TO TURN WHEN WE CHKED ON AT 400 FT AGL. THERE NEEDS TO BE A BETTER WAY FOR COLUMBUS TO CLR ACFT AT GTR, FOR THIS NOT TO OCCUR AGAIN. CLRNC NEEDS TO SPECIFY THE NEED FOR THE IMMEDIATE TURN IN ORDER TO SECURE ACFT SPACING. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED HIS FO MISTAKENLY INTERPED 'AS FILED' DEP CLRNC BY CBM AS 'RWY HDG.' RPTR HOWEVER ADVISED COMPANY CHIEF PLT OF THE SIT. CORRECTIONS TO THE COMPANY SOP HAVE BEEN COMPLETED. COMPANY PERSONNEL CLARIFIED DEP PROCS WITH CBM MILFAC PRIOR TO IMPLEMENTING SOP CHANGES.

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.