Altitude deviation altitude overshot in descent.

Attributes
ACN	296308
Time
Date	199502
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : mlf
State Reference	UT
Altitude	msl bound lower : 35000 msl bound upper : 37000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zlc
Operator	general aviation : corporate
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 91
Navigation In Use	Other Other
Flight Phase	descent other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 12700 flight time type : 2200
ASRS Report	296308
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	flight crew : returned to intended course or assigned course flight crew : became reoriented other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

The flight was anticipating an immediate and rapid descent considering our altitude and distance from our destination (approximately 60 NM east at FL390). When center finally cleared us to a lower altitude, the PNF received the call and set the altitude preselect and notified me. I had not monitored the original call. We started a rapid descent (3000 FPM) from FL390 toward FL270. However, passing FL360 we were notified we were cleared to only FL370. The PNF felt certain he heard FL270, not FL370, and had set the preselect accordingly. We leveled by FL350 and climbed to FL370. The confusion on radios between 2's and 3's is long standing. The PNF also remembers repeating 'FL270' when replying to the center's descent clearance. I suggest that altitude clrncs be issued in the standard format, ie, 'FL370,' however, the response should be differently expressed, ie, 'descending/climbing to 37.' this way, 20 and 30 are less confusing on the radio than 2 and 3. This is the way we usually respond, and feel the controller missed our response.

Original NASA ASRS Text

Title: ALTDEV ALT OVERSHOT IN DSCNT.

Narrative: THE FLT WAS ANTICIPATING AN IMMEDIATE AND RAPID DSCNT CONSIDERING OUR ALT AND DISTANCE FROM OUR DEST (APPROX 60 NM E AT FL390). WHEN CTR FINALLY CLRED US TO A LOWER ALT, THE PNF RECEIVED THE CALL AND SET THE ALT PRESELECT AND NOTIFIED ME. I HAD NOT MONITORED THE ORIGINAL CALL. WE STARTED A RAPID DSCNT (3000 FPM) FROM FL390 TOWARD FL270. HOWEVER, PASSING FL360 WE WERE NOTIFIED WE WERE CLRED TO ONLY FL370. THE PNF FELT CERTAIN HE HEARD FL270, NOT FL370, AND HAD SET THE PRESELECT ACCORDINGLY. WE LEVELED BY FL350 AND CLBED TO FL370. THE CONFUSION ON RADIOS BTWN 2'S AND 3'S IS LONG STANDING. THE PNF ALSO REMEMBERS REPEATING 'FL270' WHEN REPLYING TO THE CTR'S DSCNT CLRNC. I SUGGEST THAT ALT CLRNCS BE ISSUED IN THE STANDARD FORMAT, IE, 'FL370,' HOWEVER, THE RESPONSE SHOULD BE DIFFERENTLY EXPRESSED, IE, 'DSNDING/CLBING TO 37.' THIS WAY, 20 AND 30 ARE LESS CONFUSING ON THE RADIO THAN 2 AND 3. THIS IS THE WAY WE USUALLY RESPOND, AND FEEL THE CTLR MISSED OUR RESPONSE.

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.