The tower was closed and FSS was busy. C172 pilot made every attempt to get a clearance void time. When he finally contacted ATC, he was told to hold for release. When asked when he would be ready he said in 6 mins. In 6 mins he took off without release and without further contact with ATC.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	358400
Time
Date	199701
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : mod
State Reference	CA
Altitude	agl bound lower : 0 agl bound upper : 1000
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : sck
Operator	general aviation : instructional
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	climbout : intermediate altitude climbout : takeoff ground : holding
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : commercial
Experience	flight time last 90 days : 200 flight time total : 450 flight time type : 100
ASRS Report	358400
Person 2
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
Events
Anomaly	inflight encounter : vfr in imc non adherence : far non adherence : clearance other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Under IFR flight plan from mod to rhv, home base, FSS told me to contact sck approach on the ground because I requested a clearance void time. Mod tower was closed and I was supposed to take off at XX30 friday. I contacted, on ground. Rancho FSS was too busy to issue me a clearance void time, sck approach on 120.95 to receive my IFR clearance. After my IFR clearance was received, the controller told me to 'hold for release' with no efc time and ask when I will take off. I effectively read back 'hold for release' and told him that I will take off in 6 mins. I did my runup and elected to take off once the 6 mins passed, and forgot about the 'hold for release.' I recontacted the sck approach once airborne and I understood the surprise of the controller. Then, I apologized and he told me to call the following day the sck manager of the approach. I think that my fatigue and the fact that I didn't have my dinner is part of why I did that. The WX in mod was IFR and it was nighttime.

Original NASA ASRS Text

Title: THE TWR WAS CLOSED AND FSS WAS BUSY. C172 PLT MADE EVERY ATTEMPT TO GET A CLRNC VOID TIME. WHEN HE FINALLY CONTACTED ATC, HE WAS TOLD TO HOLD FOR RELEASE. WHEN ASKED WHEN HE WOULD BE READY HE SAID IN 6 MINS. IN 6 MINS HE TOOK OFF WITHOUT RELEASE AND WITHOUT FURTHER CONTACT WITH ATC.

Narrative: UNDER IFR FLT PLAN FROM MOD TO RHV, HOME BASE, FSS TOLD ME TO CONTACT SCK APCH ON THE GND BECAUSE I REQUESTED A CLRNC VOID TIME. MOD TWR WAS CLOSED AND I WAS SUPPOSED TO TAKE OFF AT XX30 FRIDAY. I CONTACTED, ON GND. RANCHO FSS WAS TOO BUSY TO ISSUE ME A CLRNC VOID TIME, SCK APCH ON 120.95 TO RECEIVE MY IFR CLRNC. AFTER MY IFR CLRNC WAS RECEIVED, THE CTLR TOLD ME TO 'HOLD FOR RELEASE' WITH NO EFC TIME AND ASK WHEN I WILL TAKE OFF. I EFFECTIVELY READ BACK 'HOLD FOR RELEASE' AND TOLD HIM THAT I WILL TAKE OFF IN 6 MINS. I DID MY RUNUP AND ELECTED TO TAKE OFF ONCE THE 6 MINS PASSED, AND FORGOT ABOUT THE 'HOLD FOR RELEASE.' I RECONTACTED THE SCK APCH ONCE AIRBORNE AND I UNDERSTOOD THE SURPRISE OF THE CTLR. THEN, I APOLOGIZED AND HE TOLD ME TO CALL THE FOLLOWING DAY THE SCK MGR OF THE APCH. I THINK THAT MY FATIGUE AND THE FACT THAT I DIDN'T HAVE MY DINNER IS PART OF WHY I DID THAT. THE WX IN MOD WAS IFR AND IT WAS NIGHTTIME.

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.