<< >> NASA ASRS Report 588548, July 2003

A PA31 single pilot reported that he received an IFR clearance and departed dvn without a void time which later caused a problem with mli.

Attributes
ACN	588548
Time
Date	200307
Day	Fri
Place
Locale Reference	airport : dvn.airport
State Reference	IA
Altitude	agl bound lower : 0 agl bound upper : 2000
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mli.tracon
Operator	general aviation : corporate
Make Model Name	PA-31T Cheyenne II
Operating Under FAR Part	Part 91
Flight Phase	ground : takeoff roll
Aircraft 2
Controlling Facilities	tracon : mli.tracon
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent : approach
Person 1
Affiliation	company : corporate
Function	flight crew : single pilot
Qualification	pilot : atp pilot : cfi pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 80 flight time total : 3300 flight time type : 600
ASRS Report	588548
Person 2
Function	flight crew : captain oversight : pic
Events
Anomaly	airspace violation : entry non adherence : published procedure non adherence : clearance non adherence : far
Independent Detector	other controllera
Resolutory Action	controller : issued advisory none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On the ground at dvn I called for an IFR clearance to miw. The WX was VFR with scattered to broken clouds at approximately 15000 ft with 10 mi visibility. Dvn has an rco so I opted to get the clearance on the ground. I received a 'cleared as filed' with altitudes, radio frequency and transponder code. I read the clearance back and the controller said 'readback correct' with the exception of an altitude change. I confirmed that and changed to advisory to depart. Using CTAF I departed and climbed through the scattered layer and upon calling quad cities departure was told by ATC that he was trying to call me to find out when I was going to be airborne. Apparently he had another aircraft on another approach to dun. He said it 'was never an issue but could have been 'hairy'.' I apologized and mentioned I did not receive a 'hold for release' clearance. There were no further communications. I believe if there was a question by ATC as to whether separation would be adequate that they should have made my clearance a 'hold for release'.

Related reports:

• A be-30 pilot reported that a high performance single engine...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A PA31 SINGLE PLT RPTED THAT HE RECEIVED AN IFR CLRNC AND DEPARTED DVN WITHOUT A VOID TIME WHICH LATER CAUSED A PROB WITH MLI.

Narrative: ON THE GND AT DVN I CALLED FOR AN IFR CLRNC TO MIW. THE WX WAS VFR WITH SCATTERED TO BROKEN CLOUDS AT APPROX 15000 FT WITH 10 MI VISIBILITY. DVN HAS AN RCO SO I OPTED TO GET THE CLRNC ON THE GND. I RECEIVED A 'CLRED AS FILED' WITH ALTS, RADIO FREQ AND XPONDER CODE. I READ THE CLRNC BACK AND THE CTLR SAID 'READBACK CORRECT' WITH THE EXCEPTION OF AN ALT CHANGE. I CONFIRMED THAT AND CHANGED TO ADVISORY TO DEPART. USING CTAF I DEPARTED AND CLBED THROUGH THE SCATTERED LAYER AND UPON CALLING QUAD CITIES DEP WAS TOLD BY ATC THAT HE WAS TRYING TO CALL ME TO FIND OUT WHEN I WAS GOING TO BE AIRBORNE. APPARENTLY HE HAD ANOTHER ACFT ON ANOTHER APCH TO DUN. HE SAID IT 'WAS NEVER AN ISSUE BUT COULD HAVE BEEN 'HAIRY'.' I APOLOGIZED AND MENTIONED I DID NOT RECEIVE A 'HOLD FOR RELEASE' CLRNC. THERE WERE NO FURTHER COMS. I BELIEVE IF THERE WAS A QUESTION BY ATC AS TO WHETHER SEPARATION WOULD BE ADEQUATE THAT THEY SHOULD HAVE MADE MY CLRNC A 'HOLD FOR RELEASE'.

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.