Non adherence to ATC clearance departure time.

Attributes
ACN	112641
Time
Date	198906
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : ocn
State Reference	CA
Altitude	msl bound lower : 900 msl bound upper : 3000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : san
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	climbout : takeoff climbout : intermediate altitude climbout : initial
Route In Use	departure other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : commercial pilot : instrument
Experience	flight time last 90 days : 150 flight time total : 1300 flight time type : 80
ASRS Report	112641
Person 2
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
Events
Anomaly	non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I called san diego radio on 122.1 and receiving over the oceanside VOR (ocn) (115.3), to pick up an IFR clearance from (ocn) oceanside airport to (sna) john wayne/orange county airport. As I copied the clearance, I heard and wrote down a departure window time of :30Z to :55Z. The reception of the clearance over the VOR was quite scratchy, but I copied and read back the clearance, however, I did not repeat the window times. The flight service technician did not query my copy of the window times but then gave me the altimeter setting. I responded with our thanks and advised him we would be departing momentarily. The specialist did not reply further. At approximately :32Z I announced my intentions over the CTAF, taxied into position on runway 24, and observed another aircraft holding short of runway 24, slightly further down the runway. This caused me to inwardly question my window times. Conditions at the airport were less than VFR, so the other aircraft was going to either be scud running or it was also departing IFR. Further, if the other aircraft were indeed IFR, it didn't make any sense why he was holding with his engine running because he would surely have to wait for at least 10 minutes after our departure. Holding in position, I opted to verify my window with flight service. I attempted to contact the facility 4 times, again transmitting on 122.1 and receiving over the oceanside (ocn) VOR. There was no response. I then departed, climbing out via the published IFR departure procedure for that airport, published on the airport diagram. I reported to san diego approach, where I was advised radar contact and a clearance to climb to 3000' as I was climbing through 400 MSL. After entering IMC conditions at approximately 800' MSL, I heard the airplane that I had seen on the ground at oceanside checking in with departure control out of 200'. The controller vectored both our aircraft away from each other. I was then told by the controller that my departure widow was from :50Z to :55Z and was then directed to call the facility upon landing over the telephone.

Original NASA ASRS Text

Title: NON ADHERENCE TO ATC CLRNC DEP TIME.

Narrative: I CALLED SAN DIEGO RADIO ON 122.1 AND RECEIVING OVER THE OCEANSIDE VOR (OCN) (115.3), TO PICK UP AN IFR CLRNC FROM (OCN) OCEANSIDE ARPT TO (SNA) JOHN WAYNE/ORANGE COUNTY ARPT. AS I COPIED THE CLRNC, I HEARD AND WROTE DOWN A DEP WINDOW TIME OF :30Z TO :55Z. THE RECEPTION OF THE CLRNC OVER THE VOR WAS QUITE SCRATCHY, BUT I COPIED AND READ BACK THE CLRNC, HOWEVER, I DID NOT REPEAT THE WINDOW TIMES. THE FLT SERVICE TECHNICIAN DID NOT QUERY MY COPY OF THE WINDOW TIMES BUT THEN GAVE ME THE ALTIMETER SETTING. I RESPONDED WITH OUR THANKS AND ADVISED HIM WE WOULD BE DEPARTING MOMENTARILY. THE SPECIALIST DID NOT REPLY FURTHER. AT APPROX :32Z I ANNOUNCED MY INTENTIONS OVER THE CTAF, TAXIED INTO POSITION ON RWY 24, AND OBSERVED ANOTHER ACFT HOLDING SHORT OF RWY 24, SLIGHTLY FURTHER DOWN THE RWY. THIS CAUSED ME TO INWARDLY QUESTION MY WINDOW TIMES. CONDITIONS AT THE ARPT WERE LESS THAN VFR, SO THE OTHER ACFT WAS GOING TO EITHER BE SCUD RUNNING OR IT WAS ALSO DEPARTING IFR. FURTHER, IF THE OTHER ACFT WERE INDEED IFR, IT DIDN'T MAKE ANY SENSE WHY HE WAS HOLDING WITH HIS ENGINE RUNNING BECAUSE HE WOULD SURELY HAVE TO WAIT FOR AT LEAST 10 MINUTES AFTER OUR DEP. HOLDING IN POSITION, I OPTED TO VERIFY MY WINDOW WITH FLT SERVICE. I ATTEMPTED TO CONTACT THE FAC 4 TIMES, AGAIN XMITTING ON 122.1 AND RECEIVING OVER THE OCEANSIDE (OCN) VOR. THERE WAS NO RESPONSE. I THEN DEPARTED, CLIMBING OUT VIA THE PUBLISHED IFR DEP PROC FOR THAT ARPT, PUBLISHED ON THE ARPT DIAGRAM. I REPORTED TO SAN DIEGO APCH, WHERE I WAS ADVISED RADAR CONTACT AND A CLRNC TO CLIMB TO 3000' AS I WAS CLIMBING THROUGH 400 MSL. AFTER ENTERING IMC CONDITIONS AT APPROX 800' MSL, I HEARD THE AIRPLANE THAT I HAD SEEN ON THE GND AT OCEANSIDE CHECKING IN WITH DEP CTL OUT OF 200'. THE CTLR VECTORED BOTH OUR ACFT AWAY FROM EACH OTHER. I WAS THEN TOLD BY THE CTLR THAT MY DEP WIDOW WAS FROM :50Z TO :55Z AND WAS THEN DIRECTED TO CALL THE FAC UPON LNDG OVER THE TELEPHONE.

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.