|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||airport : cma|
|Altitude||msl bound lower : 500|
msl bound upper : 500
|Controlling Facilities||tracon : ntd|
tower : bak
|Operator||general aviation : personal|
|Make Model Name||Small Aircraft, Low Wing, 1 Eng, Fixed Gear|
|Flight Phase||climbout : intermediate altitude|
climbout : takeoff
|Route In Use||enroute : on vectors|
|Function||flight crew : single pilot|
|Qualification||pilot : instrument|
pilot : commercial
|Experience||flight time last 90 days : 40|
flight time total : 535
flight time type : 480
|Affiliation||government : faa|
|Function||controller : departure|
|Qualification||controller : radar|
|Anomaly||non adherence : clearance|
other anomaly other
|Independent Detector||other controllera|
|Resolutory Action||controller : issued new clearance|
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||Pilot Deviation|
On an IFR flight plan (tower en route) PIC contacted designated clearance delivery for camarillo, ca, airport, and uncontrolled field. Controller read clearance, including instruction to contact magu approach after takeoff. I had never flown out of the cma (uncontrolled) airport before, and I thought it strange that I was given no void time for departure. I was under the impression that I was released for departure, and switched to CTAF and announced departure, and at 500', in VFR conditions, contacted mugu on 124.7. I was advised by approach that I was supposed to have contacted them for release prior to departure, and was instructed to maintain VFR. After being issued a vector to the northeast, I advised approach I would be unable to maintain VFR on such heading. I was then cleared to 5000' and shortly thereafter entered IMC conditions. Although technically I had not entered the IFR system or IFR WX prior to issuance of a clearance, the controller was clearly surprised by my departure. Contributing factors: the vast, vast majority of my IFR procedures experience has been at controled airfields where after readback of clearance an instruction to contact tower and advise ready for IFR release has always been issued. My IFR training included only 2 departures from uncontrolled fields, and each time a clearance was issued either from approach or FSS with a clearance void restriction. The magu clearance delivery controller was very gruff in issuing the clearance, and made no mention of the need to call another controller prior to takeoff, although I had some unresolved hesitations concerning the takeoff west/O issuance of a clearance void time. I believe I let the demeanor of the magu controller (who spoke so fast I thought I was hearing my first IFR clearance!) bully me in not communicating my doubts and seeking a resolution prior to proceeding. This hybrid situation of having a clearance delivery at an uncontrolled field was not the subject of any training nor a subject on the oral portion of my chkride. I've learned that if uncomfortable about the outcome of any procedure of flight, not to continue on until all doubts have been resolved.
Original NASA ASRS Text
Title: IFR DEP FROM UNCONTROLLED FIELD. DID NOT RECEIVE ACTUAL DEP RELEASE PRIOR TO TKOF.
Narrative: ON AN IFR FLT PLAN (TWR ENRTE) PIC CONTACTED DESIGNATED CLRNC DELIVERY FOR CAMARILLO, CA, ARPT, AND UNCTLED FIELD. CTLR READ CLRNC, INCLUDING INSTRUCTION TO CONTACT MAGU APCH AFTER TKOF. I HAD NEVER FLOWN OUT OF THE CMA (UNCTLED) ARPT BEFORE, AND I THOUGHT IT STRANGE THAT I WAS GIVEN NO VOID TIME FOR DEP. I WAS UNDER THE IMPRESSION THAT I WAS RELEASED FOR DEP, AND SWITCHED TO CTAF AND ANNOUNCED DEP, AND AT 500', IN VFR CONDITIONS, CONTACTED MUGU ON 124.7. I WAS ADVISED BY APCH THAT I WAS SUPPOSED TO HAVE CONTACTED THEM FOR RELEASE PRIOR TO DEP, AND WAS INSTRUCTED TO MAINTAIN VFR. AFTER BEING ISSUED A VECTOR TO THE NE, I ADVISED APCH I WOULD BE UNABLE TO MAINTAIN VFR ON SUCH HDG. I WAS THEN CLRED TO 5000' AND SHORTLY THEREAFTER ENTERED IMC CONDITIONS. ALTHOUGH TECHNICALLY I HAD NOT ENTERED THE IFR SYS OR IFR WX PRIOR TO ISSUANCE OF A CLRNC, THE CTLR WAS CLEARLY SURPRISED BY MY DEP. CONTRIBUTING FACTORS: THE VAST, VAST MAJORITY OF MY IFR PROCS EXPERIENCE HAS BEEN AT CTLED AIRFIELDS WHERE AFTER READBACK OF CLRNC AN INSTRUCTION TO CONTACT TWR AND ADVISE READY FOR IFR RELEASE HAS ALWAYS BEEN ISSUED. MY IFR TRNING INCLUDED ONLY 2 DEPS FROM UNCTLED FIELDS, AND EACH TIME A CLRNC WAS ISSUED EITHER FROM APCH OR FSS WITH A CLRNC VOID RESTRICTION. THE MAGU CLRNC DELIVERY CTLR WAS VERY GRUFF IN ISSUING THE CLRNC, AND MADE NO MENTION OF THE NEED TO CALL ANOTHER CTLR PRIOR TO TKOF, ALTHOUGH I HAD SOME UNRESOLVED HESITATIONS CONCERNING THE TKOF W/O ISSUANCE OF A CLRNC VOID TIME. I BELIEVE I LET THE DEMEANOR OF THE MAGU CTLR (WHO SPOKE SO FAST I THOUGHT I WAS HEARING MY FIRST IFR CLRNC!) BULLY ME IN NOT COMMUNICATING MY DOUBTS AND SEEKING A RESOLUTION PRIOR TO PROCEEDING. THIS HYBRID SITUATION OF HAVING A CLRNC DELIVERY AT AN UNCTLED FIELD WAS NOT THE SUBJECT OF ANY TRNING NOR A SUBJECT ON THE ORAL PORTION OF MY CHKRIDE. I'VE LEARNED THAT IF UNCOMFORTABLE ABOUT THE OUTCOME OF ANY PROC OF FLT, NOT TO CONTINUE ON UNTIL ALL DOUBTS HAVE BEEN RESOLVED.
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.