Top of Descent and 0 for missed approach altitude issues

[dornier]

Hi,

I accomplished a flight from KELP to KABQ.  FMC flight plan was LATVE2.CME.LZZRD3, PILLA transition.  The cruise altitude was FL300 and once I crossed CME vor, I placed 10000 into the MCP altitude window.  I was on path and everything looked great until I crossed MKYON intersection.  Upon crossing MKYON, the path fully deflected high and it showed that I was off by 15000' (high on the path).  It was obvious early on that the predicted T/D was not accurate.  As a matter of fact, I've noticed on several flights that the T/D is passed the airport.  

I don't know if this part of the prediction problem, but I've noticed that when I pull up an approach, there tends to be 0 (zeros) for the missed approach altitudes.  I think I've also seen zeros on some arrivals, but I need to check on that again.

Hope this helps,

George

[crisk73]

Since the new 1.0.7 I'm seeing zeroes for some altitudes also in SID and STAR calculations and when it happens VNAV is not available before such waypoints. I use to delete zeroes or add some alt restrictions in place of them to make the vertical profile be calculated and VNAV then becomes available. Maybe this issue has to do with the new VNAV modifications introduced with 1.0.7.