Piper arrow is slow to climb when unable to get confirmation of clearance.

Attributes
ACN	348670
Time
Date	199609
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : sbv airport : int
State Reference	VA
Altitude	msl bound lower : 7000 msl bound upper : 9000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc
Operator	general aviation : personal
Make Model Name	PA-28 Cherokee Arrow IV
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : commercial
Experience	flight time last 90 days : 25 flight time total : 1700 flight time type : 900
ASRS Report	348670
Person 2
Affiliation	Other
Function	observation : passenger
Qualification	pilot : instrument pilot : private
Experience	flight time last 90 days : 30 flight time total : 220 flight time type : 100
Events
Anomaly	altitude deviation : undershoot non adherence : published procedure non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : returned to intended course or assigned course other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

On IFR flight plan winston-salem, nc (int), to frederick, md. Had just leveled at 7000 ft, the altitude filed for. ZDC was busy with a lot of traffic and issued an instruction to 'climb to 9000 ft.' before the climb, it took about 45 seconds to get a word in on the frequency to request a confirmation that I filed for 7000 ft, not 9000 ft. At this point the aggravated controller 'lectured' me for about a min indicating I should climb first and request confirmations later. I immediately complied with the climb clearance while he was 'discussing' this with me. He stopped me at 8000 ft and a few mins later returned me to 7000 ft. He did not say 'immediately' climb or did not express any 'urgency' with the request. I thought he thought I filed for 9000 ft since his instruction came just after leveling at 7000 ft. If he had a traffic conflict with me, he did not indicate it to me. I will hereafter comply first, question the clearance second if necessary. I feel the controller should seek a confirmation of instructions, should express any urgency by saying 'climb immediately,' or briefly offering any explanation to the pilot.

Original NASA ASRS Text

Title: PIPER ARROW IS SLOW TO CLB WHEN UNABLE TO GET CONFIRMATION OF CLRNC.

Narrative: ON IFR FLT PLAN WINSTON-SALEM, NC (INT), TO FREDERICK, MD. HAD JUST LEVELED AT 7000 FT, THE ALT FILED FOR. ZDC WAS BUSY WITH A LOT OF TFC AND ISSUED AN INSTRUCTION TO 'CLB TO 9000 FT.' BEFORE THE CLB, IT TOOK ABOUT 45 SECONDS TO GET A WORD IN ON THE FREQ TO REQUEST A CONFIRMATION THAT I FILED FOR 7000 FT, NOT 9000 FT. AT THIS POINT THE AGGRAVATED CTLR 'LECTURED' ME FOR ABOUT A MIN INDICATING I SHOULD CLB FIRST AND REQUEST CONFIRMATIONS LATER. I IMMEDIATELY COMPLIED WITH THE CLB CLRNC WHILE HE WAS 'DISCUSSING' THIS WITH ME. HE STOPPED ME AT 8000 FT AND A FEW MINS LATER RETURNED ME TO 7000 FT. HE DID NOT SAY 'IMMEDIATELY' CLB OR DID NOT EXPRESS ANY 'URGENCY' WITH THE REQUEST. I THOUGHT HE THOUGHT I FILED FOR 9000 FT SINCE HIS INSTRUCTION CAME JUST AFTER LEVELING AT 7000 FT. IF HE HAD A TFC CONFLICT WITH ME, HE DID NOT INDICATE IT TO ME. I WILL HEREAFTER COMPLY FIRST, QUESTION THE CLRNC SECOND IF NECESSARY. I FEEL THE CTLR SHOULD SEEK A CONFIRMATION OF INSTRUCTIONS, SHOULD EXPRESS ANY URGENCY BY SAYING 'CLB IMMEDIATELY,' OR BRIEFLY OFFERING ANY EXPLANATION TO THE PLT.

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.