Narrative:

We were filed to fly the jfrye 1 RNAV arrival beginning at hydes into dal. We got repeated 'steep descent after jtroe' or 'masty' messages at various times after the zero fuel weight was entered in the FMC and in-flight. Prior to TOD; we uploaded ACARS winds into the FMC and those winds were pretty much as advertised; from five o'clock from 57 to 40 knots throughout most of the arrival. Mental math confirmed we would have problems flying the arrival as published at several points on our way down. The problem became the most problematic right after passing jtroe. The first officer (first officer) had done a fine job at getting the airplane back in VNAV pth prior to jtroe and airspeed was right on. As soon as we passed jtroe; we went from right on path to over 1;200 feet high at which point the FMC reverted to VNAV speed again. The only way we could have made the 10;000 feet restriction at gregs would have been if we had been 30 to 40 knots above the published 250 speed there. We were discussing the need to get ATC relief when regional approach told us to descend to 5;000 feet so that eliminated the threat. Regardless of 737 variant; it appears the descent gradient for this arrival is too steep with even relatively benign tailwinds. Please test this arrival in the simulator. If it is 'un-flyable' then we should revert to the gregs arrival where the descent gradient is less constraining. The altitude constraints at both jtroe and masty appear too high. We are placing our pilots at unnecessary risk if this arrival has problems of the magnitude we saw last night.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 Captain reports being unable to maintain the descent path on the JFRYE1 RNAV arrival to DAL with a 40 knot tailwind. ATC provides relief without being prompted.

Narrative: We were filed to fly the JFRYE 1 RNAV Arrival beginning at HYDES into DAL. We got repeated 'steep descent after JTROE' or 'MASTY' messages at various times after the zero fuel weight was entered in the FMC and in-flight. Prior to TOD; we uploaded ACARS winds into the FMC and those winds were pretty much as advertised; from five o'clock from 57 to 40 knots throughout most of the arrival. Mental math confirmed we would have problems flying the arrival as published at several points on our way down. The problem became the most problematic right after passing JTROE. The First Officer (FO) had done a fine job at getting the airplane back in VNAV PTH prior to JTROE and airspeed was right on. As soon as we passed JTROE; we went from right on path to over 1;200 feet high at which point the FMC reverted to VNAV SPD again. The only way we could have made the 10;000 feet restriction at GREGS would have been if we had been 30 to 40 knots above the published 250 speed there. We were discussing the need to get ATC relief when regional approach told us to descend to 5;000 feet so that eliminated the threat. Regardless of 737 variant; it appears the descent gradient for this arrival is too steep with even relatively benign tailwinds. Please test this arrival in the simulator. If it is 'un-flyable' then we should revert to the GREGS Arrival where the descent gradient is less constraining. The altitude constraints at both JTROE and MASTY appear too high. We are placing our Pilots at unnecessary risk if this arrival has problems of the magnitude we saw last night.

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.