Narrative:

I recieved a clearance to 9000 ft and read back 9000 ft. At approximately 12000 ft I requested that we be allowed to 'keep the descent going.' (for we always cross bpt at 6000 ft) and it was gong to require a rapid rate of descent later if started at 9000 ft. The controller then told us 'crossing at 8000 ft.' I understood that I was to keep my descent going and cross bpt at 8000 ft. Subsequently I continued down to the 8000 that I felt I was cleared to. ATC informed me of traffic 12 O'clock which we were looking for when they asked me to verify my altitude as 9000 ft. I said 'no I am out of 8.4 for 8 and visually checked that the altitude alerter was set for 8000 ft. It was set on 8000. ATC informed me that I was only cleared to 9000 ft. So I expedited back to 9000 ft to solve the traffic conflict. I asked the controller if further action was necessary and took the lack of response to mean yes. I phoned center and spoke with supervisor about the event. He informed me that a review of the tape had taken place and it was logged as 'pilot error.' I now feel that the 'crossing at 8000' he acknowledged was meant to warn us of 'traffic crossing at 8000' not the clearance to cross (bpt) at 8000 as we had heard and complied with. In his attempt to inform us of traffic the controller inadvertently nearly brought us together. Supplemental information from acn 184746. ATC responds, 'negative, crossing traffic at 8000 ft. Lower when clear.' I question the new altitude; '8000 ft?' company policy dictates that the PNF is to handle radio communications. Captain discounted my question about the accuracy of the clearance.

Google
 

Original NASA ASRS Text

Title: LTSS ACCOUNT CAPT CONTINUES DSCNT WHEN TFC ADVISORY HAD BEEN GIVEN.

Narrative: I RECIEVED A CLRNC TO 9000 FT AND READ BACK 9000 FT. AT APPROX 12000 FT I REQUESTED THAT WE BE ALLOWED TO 'KEEP THE DSCNT GOING.' (FOR WE ALWAYS CROSS BPT AT 6000 FT) AND IT WAS GONG TO REQUIRE A RAPID RATE OF DSCNT LATER IF STARTED AT 9000 FT. THE CTLR THEN TOLD US 'XING AT 8000 FT.' I UNDERSTOOD THAT I WAS TO KEEP MY DSCNT GOING AND CROSS BPT AT 8000 FT. SUBSEQUENTLY I CONTINUED DOWN TO THE 8000 THAT I FELT I WAS CLRED TO. ATC INFORMED ME OF TFC 12 O'CLOCK WHICH WE WERE LOOKING FOR WHEN THEY ASKED ME TO VERIFY MY ALT AS 9000 FT. I SAID 'NO I AM OUT OF 8.4 FOR 8 AND VISUALLY CHKED THAT THE ALT ALERTER WAS SET FOR 8000 FT. IT WAS SET ON 8000. ATC INFORMED ME THAT I WAS ONLY CLRED TO 9000 FT. SO I EXPEDITED BACK TO 9000 FT TO SOLVE THE TFC CONFLICT. I ASKED THE CTLR IF FURTHER ACTION WAS NECESSARY AND TOOK THE LACK OF RESPONSE TO MEAN YES. I PHONED CENTER AND SPOKE WITH SUPVR ABOUT THE EVENT. HE INFORMED ME THAT A REVIEW OF THE TAPE HAD TAKEN PLACE AND IT WAS LOGGED AS 'PLT ERROR.' I NOW FEEL THAT THE 'XING AT 8000' HE ACKNOWLEDGED WAS MEANT TO WARN US OF 'TFC XING AT 8000' NOT THE CLRNC TO CROSS (BPT) AT 8000 AS WE HAD HEARD AND COMPLIED WITH. IN HIS ATTEMPT TO INFORM US OF TFC THE CTLR INADVERTENTLY NEARLY BROUGHT US TOGETHER. SUPPLEMENTAL INFO FROM ACN 184746. ATC RESPONDS, 'NEGATIVE, XING TFC AT 8000 FT. LOWER WHEN CLR.' I QUESTION THE NEW ALT; '8000 FT?' COMPANY POLICY DICTATES THAT THE PNF IS TO HANDLE RADIO COMS. CAPT DISCOUNTED MY QUESTION ABOUT THE ACCURACY OF THE CLRNC.

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.