A B757 captain reported that; despite properly programming and verifying the FMS; the aircraft was u...

Attributes
ACN	1066800
Time
Date	201302
Local Time Of Day	0601-1200
Place
Locale Reference	ZDV.ARTCC
State Reference	CO
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR BOSSS1
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 275 Flight Crew Total 35000 Flight Crew Type 12000
Events
Anomaly	Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy

Narrative:

We had two RNAV STAR changes inbound to den; all of which were checked by both pilots and a jumpseat rider and cross checked with the efb and commercially provided paper aero charts. All speeds were checked; we were in LNAV and VNAV; on path; on speed and the pdi showed on profile. Then; approaching quail; still in VNAV and LNAV; we could not make the crossing speed and altitude restrictions at quail even with speed brakes fully extended. We did not make the profile altitudes while the LNAV and VNAV showed on the pdi and I am baffled as to why. We informed ATC and were given a descend and maintain clearance; a vector turn and a speed at our discretion. We were then cleared for a visual approach to R35L and landed normally. I called approach control and the supervisor said he had no problem with our flight and that there has been a flood of issues with aircraft not making the profiles on these new arrivals one minute we were on the path and; in an instant; we were very high on the profile! We are baffled. After 29 years with 12 plus on this fleet; this was the first problem I have had with this issue.

Original NASA ASRS Text

Title: A B757 Captain reported that; despite properly programming and verifying the FMS; the aircraft was unable to comply with the altitude and airspeed restrictions at QUAIL intersection descending into DEN. When he contacted Approach Control after landing the Supervisor advised it was no problem because the deviation was one of many occurring following implementation of the new OPD RNAV STARs at DEN.

Narrative: We had two RNAV STAR changes inbound to DEN; all of which were checked by both pilots and a jumpseat rider and cross checked with the EFB and commercially provided paper aero charts. All speeds were checked; we were in LNAV and VNAV; on path; on speed and the PDI showed on profile. Then; approaching QUAIL; still in VNAV and LNAV; we could not make the crossing speed and altitude restrictions at QUAIL even with speed brakes fully extended. We did not make the profile altitudes while the LNAV and VNAV showed on the PDI and I am baffled as to why. We informed ATC and were given a descend and maintain clearance; a vector turn and a speed at our discretion. We were then cleared for a visual approach to R35L and landed normally. I called Approach Control and the SUPERVISOR said he had NO PROBLEM with our flight and that there has been a flood of issues with aircraft not making the profiles on these new arrivals One minute we were on the path and; in an instant; we were very high on the profile! WE ARE BAFFLED. After 29 years with 12 plus on this fleet; this was the first problem I have had with this issue.

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