Narrative:

I was acting as the pilot monitoring and giving IOE during the event flight. We had begun our arrival into rdu on the MALNR1 arrival and had briefed the arrival; completed the descent checklist and were in reasonably good shape. We had been given an initial descent and started down when there were multiple frequency changes and finally a clearance to descend 'pilots discretion to fl 240'. The pilot flying (our IOE candidate on day three of IOE; third leg) set 240 and I had verified this.then another frequency change and the new section (ZDC low in the vicinity of sdz working clt and rdu arrivals) gave us clearance to cross sdz at fl 230. The IOE/PF set 230 in the FMC and forgot (not the first time on this trip) to reset the MCP. Crew factors - long day; running behind; I'm worn out from teaching; he's thinking the aircraft will automatically descend (since his past aircraft did) and I missed verifying the altitude. This is a mistake I totally made and assume responsibility for; since the [verification] chain was broken with me not verifying the altitude; I looked up pointed and saw what I wanted to see; not what was there. We passed our top of descent and I noticed (thankfully) on the des page that we were high and trending higher; asked the PF to descend and he was confused. I then asked him again to start down; which he did; and we missed the crossing by 300-400 feet high. Oh yeah; another frequency change (I think our fourth on the arrival.)if at all possible; could the ATC procedures department check with ZDC and ZJX and ask if there is any chance that we can receive a descent clearance on the arrival and not have to contact four different controllers with different clearances? Maybe that's too much as I know we leave jax high airspace for jax low airspace to wash low airspace in a busy arrival corridor. Not placing any blame on anyone but me as the controllers didn't miss my crossing altitude; I did.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 Check Captain as pilot monitoring; reported missing a crossing restriction during descent when the flying Captain forgot to reset the MCP altitude.

Narrative: I was acting as the Pilot Monitoring and giving IOE during the event flight. We had begun our arrival into RDU on the MALNR1 Arrival and had briefed the arrival; completed the Descent Checklist and were in reasonably good shape. We had been given an initial descent and started down when there were multiple frequency changes and finally a clearance to descend 'Pilots Discretion to FL 240'. The Pilot Flying (our IOE candidate on day three of IOE; third leg) set 240 and I had verified this.Then another frequency change and the new section (ZDC low in the vicinity of SDZ working CLT and RDU arrivals) gave us clearance to cross SDZ at FL 230. The IOE/PF set 230 in the FMC and forgot (not the first time on this trip) to reset the MCP. Crew factors - long day; running behind; I'm worn out from teaching; he's thinking the aircraft will automatically descend (since his past aircraft did) and I missed verifying the altitude. This is a mistake I totally made and assume responsibility for; since the [verification] chain was broken with me not verifying the altitude; I looked up pointed and saw what I wanted to see; not what was there. We passed our Top of Descent and I noticed (thankfully) on the DES page that we were high and trending higher; asked the PF to descend and he was confused. I then asked him again to start down; which he did; and we missed the crossing by 300-400 feet high. Oh yeah; another frequency change (I think our fourth on the arrival.)If at all possible; could the ATC procedures department check with ZDC and ZJX and ask if there is any chance that we can receive a descent clearance on the arrival and not have to contact four different Controllers with different clearances? Maybe that's too much as I know we leave JAX high airspace for JAX low airspace to Wash low airspace in a busy arrival corridor. Not placing any blame on anyone but me as the Controllers didn't miss my crossing altitude; I did.

Data retrieved from NASA's ASRS site 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.