A B737-700 crew on the silcn 1 arrival was high approaching klide event though the FMC indicated the...

Narrative:

Approaching waypoint ssebb on the sjc silcn 1 arrival runway 30L transition at 280 knots on path; a quick check of the fix page showed us approximately 3000' high on the glidepath to runway and increasing as the aircraft slowed to 240 knots for the ssebb speed restriction. Just inside ssebb; at about 27 miles; I was about to call for the landing gear to help with the descent and was given a vector east by ATC to help with the descent. I asked approach if they had seen the same results with other aircraft on the silcn 1 and they replied yes. The obvious reason is that there are no hard altitudes to hit on the arrival to at least get the aircraft in the ballpark of a normal descent into sjc. At ssebb you are approximately 29 miles from the field having slowed to 240 knots and driving even higher. We submitted a report to reasses/fix the arrival and what the result is (potentially high on glide path). An obvious answer is to put a hard altitude in at klide for a more accurate path. We saw it coming and were ready to adjust before the vector from ATC. There were no deviations noted and we continued to land without incident. I have noticed other new arrivals with issues; such as the oak emzoh that if flown as written will have you faster than 200 knots for the sfo class B airspace. I input 210/ knots into waypoint myshn to comply. Seems like we need to take a harder look at some of the new arrivals and do some 'fine tuning'.change the altitude at klide to a hard 4000' versus at or above. I will input a hard altitude; in this case; at klide for a more accurate flight path. It just seems that these details need to be worked out before an arrival is published so that crews and ATC are not taken by surprise. Silcn arrival on path will drive you high for runways 30L/right.

Original NASA ASRS Text

Title: A B737-700 crew on the SILCN 1 arrival was high approaching KLIDE event though the FMC indicated the aircraft was on the VNAV path. NCT stated they have seen the same result with other aircraft.

Narrative: Approaching waypoint SSEBB on the SJC SILCN 1 Arrival Runway 30L transition at 280 knots on path; a quick check of the Fix page showed us approximately 3000' high on the glidepath to runway and increasing as the aircraft slowed to 240 knots for the SSEBB speed restriction. Just inside SSEBB; at about 27 miles; I was about to call for the landing gear to help with the descent and was given a vector east by ATC to help with the descent. I asked Approach if they had seen the same results with other aircraft on the SILCN 1 and they replied yes. The obvious reason is that there are no hard altitudes to hit on the arrival to at least get the aircraft in the ballpark of a normal descent into SJC. At SSEBB you are approximately 29 miles from the field having slowed to 240 knots and driving even higher. We submitted a report to reasses/fix the arrival and what the result is (potentially high on glide path). An obvious answer is to put a hard altitude in at KLIDE for a more accurate path. We saw it coming and were ready to adjust before the vector from ATC. There were no deviations noted and we continued to land without incident. I have noticed other new arrivals with issues; such as the OAK EMZOH that if flown as written will have you faster than 200 knots for the SFO Class B airspace. I input 210/ knots into waypoint MYSHN to comply. Seems like we need to take a harder look at some of the new arrivals and do some 'fine tuning'.Change the altitude at KLIDE to a hard 4000' versus at or above. I will input a hard altitude; in this case; at KLIDE for a more accurate flight path. It just seems that these details need to be worked out before an arrival is published so that Crews and ATC are not taken by surprise. SILCN Arrival on path will drive you high for Runways 30L/R.

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.

Attributes
ACN	1263301
Time
Date	201505
Local Time Of Day	0601-1200
Place
Locale Reference	SJC.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR SILCN 1
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain
Experience	Flight Crew Last 90 Days 183
Person 2
Function	First Officer
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

A B737-700 crew on the silcn 1 arrival was high approaching klide event though the FMC indicated the aircraft was on the VNAV path. Nct stated they have seen the same result with other aircraft.