Commuter aircraft departs exactly at void time. Unable contact ATC until 2 mins later.

Attributes
ACN	225625
Time
Date	199211
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : gtr
State Reference	MS
Altitude	msl bound lower : 264 msl bound upper : 2000
Environment
Flight Conditions	IMC
Light	Dawn
Aircraft 1
Controlling Facilities	tracon : ubs
Operator	common carrier : air carrier
Make Model Name	Light Transport
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 80 flight time total : 5900
ASRS Report	225625
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	inflight encounter : vfr in imc non adherence : clearance non adherence : far other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : unable
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We began our taxi from gtr airport at OX26 CST for our destination of nashville, tn. Upon taxi out we received our clearance for takeoff and a clearance void limit of OX31 CST. After completing all of our pretkof checks we departed the field at OX31 CST. During the climb we began monitoring the departure control frequencys of gtr airport as well as columbus departure. Our initial climb procedures and climb checklists were accomplished during the climb to 2000 ft our initial altitude assigned in our clearance. We called 'off' to gtr traffic and that we were departing pattern to the north. At OX33 CST and upon reaching 2000 ft we contacted columbus departure. It was then the columbus controller accused us of departing past our OX31 limit. We assured him we departed at OX31. He advised we should have our aircraft clocks checked. Our clearance was given to us as 'clearance void if not off by OX31 CST.' we were off by OX31 but were unable to contact departure until OX33 CST. How would approach controller at a different airport know when we departed the field?

Original NASA ASRS Text

Title: COMMUTER ACFT DEPARTS EXACTLY AT VOID TIME. UNABLE CONTACT ATC UNTIL 2 MINS LATER.

Narrative: WE BEGAN OUR TAXI FROM GTR ARPT AT OX26 CST FOR OUR DEST OF NASHVILLE, TN. UPON TAXI OUT WE RECEIVED OUR CLRNC FOR TKOF AND A CLRNC VOID LIMIT OF OX31 CST. AFTER COMPLETING ALL OF OUR PRETKOF CHKS WE DEPARTED THE FIELD AT OX31 CST. DURING THE CLB WE BEGAN MONITORING THE DEP CTL FREQS OF GTR ARPT AS WELL AS COLUMBUS DEP. OUR INITIAL CLB PROCS AND CLB CHKLISTS WERE ACCOMPLISHED DURING THE CLB TO 2000 FT OUR INITIAL ALT ASSIGNED IN OUR CLRNC. WE CALLED 'OFF' TO GTR TFC AND THAT WE WERE DEPARTING PATTERN TO THE N. AT OX33 CST AND UPON REACHING 2000 FT WE CONTACTED COLUMBUS DEP. IT WAS THEN THE COLUMBUS CTLR ACCUSED US OF DEPARTING PAST OUR OX31 LIMIT. WE ASSURED HIM WE DEPARTED AT OX31. HE ADVISED WE SHOULD HAVE OUR ACFT CLOCKS CHKED. OUR CLRNC WAS GIVEN TO US AS 'CLRNC VOID IF NOT OFF BY OX31 CST.' WE WERE OFF BY OX31 BUT WERE UNABLE TO CONTACT DEP UNTIL OX33 CST. HOW WOULD APCH CTLR AT A DIFFERENT ARPT KNOW WHEN WE DEPARTED THE FIELD?

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.