Narrative:

We were in cruise at FL350. ATC gave us a crossing restriction to cross 70 miles east of rinte at FL300. My first officer dialed FL300 into the asel; verified that VNAV was selected and then entered the full restriction into the FMS. I verified that it was put in correctly and he activated it. The FMS didn't reject it; say over max descent angle; or display 'check pd placement' like it normally would if the point was in an odd place. A couple minutes later ATC asked us about the restriction and if we had put 70 in for the distance. We had been getting ready for descent by looking at the SNKPT1 arrival; and I noticed then that we were only about 50 miles away from rinte and the plane hadn't descended or alerted or anything. It had only been minutes since they assigned the restriction and there's no way we could have covered over twenty miles in that time but were really confused and I inquired them before they swapped frequencies about it. You could tell a supervisor took over comms; and told us the restriction was supposed to be 'something around 35 miles or so.' not the 70 that was originally given to us. He said not to worry about it and that everything was fine; but I figured it would be better to play it safe and file this report.I thought that I had seen the restriction up on the mfd but I can't be sure especially after ATC asked us about the mileage. But we definitely entered it into the FMS and asel correctly. I just think that we were either inside of the restriction already; or just on the edge of it and there was no way to make it. So it seems as though the M in cami was missed; at least partly. We were distracted with preparing for the descent but in the future I can use this experience to remind myself and other crew to keep an eye out for close or possible past restrictions.

Related reports:

Google
 

Original NASA ASRS Text

Title: EMB170 flight crew is instructed to cross 70 NM east of RINTE on the SNKPT1 Arrival to IND at FL300 which is entered into the FMC. This crossing restriction is already behind the aircraft as ATC had meant to say 30 NM east at FL300. The crew is not aware of the problem until ATC questions the crew about the crossing restriction.

Narrative: We were in cruise at FL350. ATC gave us a crossing restriction to cross 70 miles east of RINTE at FL300. My FO dialed FL300 into the ASEL; verified that VNAV was selected and then entered the full restriction into the FMS. I verified that it was put in correctly and he activated it. The FMS didn't reject it; say over max descent angle; or display 'check PD Placement' like it normally would if the point was in an odd place. A couple minutes later ATC asked us about the restriction and if we had put 70 in for the distance. We had been getting ready for descent by looking at the SNKPT1 arrival; and I noticed then that we were only about 50 miles away from RINTE and the plane hadn't descended or alerted or anything. It had only been minutes since they assigned the restriction and there's no way we could have covered over twenty miles in that time but were really confused and I inquired them before they swapped frequencies about it. You could tell a supervisor took over comms; and told us the restriction was supposed to be 'something around 35 miles or so.' not the 70 that was originally given to us. He said not to worry about it and that everything was fine; but I figured it would be better to play it safe and file this report.I thought that I had seen the restriction up on the MFD but I can't be sure especially after ATC asked us about the mileage. But we definitely entered it into the FMS and ASEL correctly. I just think that we were either inside of the restriction already; or just on the edge of it and there was no way to make it. So it seems as though the M in CAMI was missed; at least partly. We were distracted with preparing for the descent but in the future I can use this experience to remind myself and other crew to keep an eye out for close or possible past restrictions.

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.