A B737-300 captain reported his aircraft had difficulty tracking the sfo sstik RNAV route after take...

Narrative:

Two days in a row; flying two different -300 aircraft; we were unable to fly or determine where we were supposed to be while flying the same sstik RNAV departure out of sfo. The aircraft did not appear to fly the proper arc to the first point and missed the turn after the first point on both occasions. Luckily ATC intervened and gave us vectors without our asking. They must know there is a problem with this combination (-00 and/or sstik departure). Additionally; with VNAV selected on both occasions; the aircraft failed to fly the indicated VNAV speed above 10;000 feet. After holding 250 knots to 10;000 feet; the aircraft would lower its nose and accelerate past the VNAV indicated climb speed requiring pilot intervention prior to the clacker. We were so surprised the first time that we took extra care checking the route the second time to make sure we had not created the situation. The results were identical.we should not be flying -300 aircraft in the new aircraft airspace. Its' inability to fly some RNAV departures combined with the lack of moving map produces stressful and additive conditions that puts pilots in the red. This distraction will lead to subsequent issues (flap overspends; missed crossing restrictions; etc.) and dangerous situations caused by the lack of capability of the avionics.

Original NASA ASRS Text

Title: A B737-300 Captain reported his aircraft had difficulty tracking the SFO SSTIK RNAV route after takeoff and properly flying the VNAV path above 10;000 Feet.

Narrative: Two days in a row; flying two different -300 aircraft; we were unable to fly or determine where we were supposed to be while flying the same SSTIK RNAV Departure out of SFO. The aircraft did not appear to fly the proper arc to the first point and missed the turn after the first point on both occasions. Luckily ATC intervened and gave us vectors without our asking. They must know there is a problem with this combination (-00 and/or SSTIK Departure). Additionally; with VNAV selected on both occasions; the aircraft failed to fly the indicated VNAV speed above 10;000 feet. After holding 250 knots to 10;000 feet; the aircraft would lower its nose and accelerate past the VNAV indicated climb speed requiring Pilot intervention prior to the clacker. We were so surprised the first time that we took extra care checking the route the second time to make sure we had not created the situation. The results were identical.We should not be flying -300 aircraft in the new aircraft airspace. Its' inability to fly some RNAV departures combined with the lack of moving map produces stressful and additive conditions that puts Pilots in the RED. This distraction will lead to subsequent issues (flap overspends; missed crossing restrictions; etc.) and dangerous situations caused by the lack of capability of the avionics.

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	1256848
Time
Date	201504
Local Time Of Day	0601-1200
Place
Locale Reference	NCT.TRACON
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Component
Aircraft Component	Autoflight System
Person 1
Function	Captain
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Speed All Types Deviation - Track / Heading All Types

A B737-300 captain reported his aircraft had difficulty tracking the sfo sstik RNAV route after takeoff and properly flying the VNAV path above 10;000 feet.