Narrative:

During the initial descent into phl, ATC advised us that we could expect to cross the terri intersection on the dupont 4 arrival at 10000 ft and 250 KTS. This was an expect only advisory -- we were to maintain our present altitude of 15000 ft. I read back the advisory as an 'expect' only clearance. The captain was the PF for this leg. After reading back the expect clearance, I advised the captain that I would stop monitoring communication #1 radio (in use for ATC communication) so that I could make a farewell announcement to our passenger. He acknowledged me, and I proceeded to make the announcement. When I returned to communication #1 radio (reselected #1 radio), my attention was caught by the unwinding altimeter. I asked the captain if ATC had cleared us to descend to 10000 ft. He said yes. Shortly thereafter, ATC advised us that we had not been given a descent clearance and he restated that it had been an 'expect to cross' only. I asked the captain again if we had indeed been cleared to descend during the time I had been talking to the passenger. His reply was 'I thought we were.' the controller also stated that our altitude deviation did not create any conflicts. Our airline has an altitude awareness program that has worked very well. It has been adopted by several other airlines. It does not, however, address 'expect to cross' clrncs. It is used to verify altitude selection in the altitude window of our MCP of the apfds. I will suggest to our safety department that it be extended to include that both pilots verbalize the 'expect to cross' clrncs as such. The main cause for our altitude deviation was my assumption that the captain understood the clearance simply because he was also listening to the radio xmissions.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B767 CREW, ARRIVING PHL, MISUNDERSTOOD AN 'EXPECT TO CROSS' CLRNC AS BEING A CLRNC TO CROSS, STARTING DSCNT PREMATURELY.

Narrative: DURING THE INITIAL DSCNT INTO PHL, ATC ADVISED US THAT WE COULD EXPECT TO CROSS THE TERRI INTXN ON THE DUPONT 4 ARR AT 10000 FT AND 250 KTS. THIS WAS AN EXPECT ONLY ADVISORY -- WE WERE TO MAINTAIN OUR PRESENT ALT OF 15000 FT. I READ BACK THE ADVISORY AS AN 'EXPECT' ONLY CLRNC. THE CAPT WAS THE PF FOR THIS LEG. AFTER READING BACK THE EXPECT CLRNC, I ADVISED THE CAPT THAT I WOULD STOP MONITORING COM #1 RADIO (IN USE FOR ATC COM) SO THAT I COULD MAKE A FAREWELL ANNOUNCEMENT TO OUR PAX. HE ACKNOWLEDGED ME, AND I PROCEEDED TO MAKE THE ANNOUNCEMENT. WHEN I RETURNED TO COM #1 RADIO (RESELECTED #1 RADIO), MY ATTN WAS CAUGHT BY THE UNWINDING ALTIMETER. I ASKED THE CAPT IF ATC HAD CLRED US TO DSND TO 10000 FT. HE SAID YES. SHORTLY THEREAFTER, ATC ADVISED US THAT WE HAD NOT BEEN GIVEN A DSCNT CLRNC AND HE RESTATED THAT IT HAD BEEN AN 'EXPECT TO CROSS' ONLY. I ASKED THE CAPT AGAIN IF WE HAD INDEED BEEN CLRED TO DSND DURING THE TIME I HAD BEEN TALKING TO THE PAX. HIS REPLY WAS 'I THOUGHT WE WERE.' THE CTLR ALSO STATED THAT OUR ALTDEV DID NOT CREATE ANY CONFLICTS. OUR AIRLINE HAS AN ALT AWARENESS PROGRAM THAT HAS WORKED VERY WELL. IT HAS BEEN ADOPTED BY SEVERAL OTHER AIRLINES. IT DOES NOT, HOWEVER, ADDRESS 'EXPECT TO CROSS' CLRNCS. IT IS USED TO VERIFY ALT SELECTION IN THE ALT WINDOW OF OUR MCP OF THE APFDS. I WILL SUGGEST TO OUR SAFETY DEPT THAT IT BE EXTENDED TO INCLUDE THAT BOTH PLTS VERBALIZE THE 'EXPECT TO CROSS' CLRNCS AS SUCH. THE MAIN CAUSE FOR OUR ALTDEV WAS MY ASSUMPTION THAT THE CAPT UNDERSTOOD THE CLRNC SIMPLY BECAUSE HE WAS ALSO LISTENING TO THE RADIO XMISSIONS.

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.