I'm too lazy to care. Some would call that bad form. Me? I call it technique. You go a little faster, a little slower, just take the average. It'll work out.
What do you call it passing a fix that says AT 280kts while the plane is doing 260?
I usually don't care how people fly and as FO of course I'm not raising alarm bells for things outside of safety of flight. But crossing a fix 20 knots below published restricted airspeed, IMO, is bad form.
The most common error, apart from going into V/S to 'smooth out' a climb/descent is being in V/S and constantly tweaking the setting as ALT* engages at a moment you didn't expect.
Personally, if I was an instructor (which I'm not), I'd probably just cover up the MCP and teach my students to reach for the correct control and then set the autopilot while watching the FMA. The MCP is what you want, the FMA is what you're getting.
That's a gotcha. One shouldn't be tweaking it near ALT* , the time to do that is before and then leave it and let it capture.
Another fine example of when using open descent or managed descent will leave you high is on the Williamsport3 arrival into EWR. Cross SLT at FL310. Typically scenario is we're on a transcon at FL370 and tailwinds of 50-100 knots at that point. If you put SLT at 310 in the box, and set 310 on the FCP, it almost always puts the TOD arrow at exactly 18-19 miles, which is literally a 3 to 1 rule. It doesn't work if you try to start down at the arrow with tailwinds being what they are (strong). The Vdev ball goes low quickly and the power is of course slow to come off. Soon it hits idle, and it's diving down at top of the 20 knot scale in order to chase the ball. It finally ALT* at a fairly high point and starts to level the nose/reduce descent rate. With managed descent and even open descent, Starting down at the TOd arrow which is 18-19 miles away from SLT, I've seen guys cross it at FL314-318. Again, probably not a big deal to ATC considering the plane is leveling and their radar sweep isn't fast enough and they'll probably not notice. You are after all leveling at Fl310. Case like this personally I dial in VS down about 26-28 miles out instead of 18-19, and a rate of about 2200-2500 fpm works great. Ends up crossing SLT at level altitude.
The other technique/finese thing is resetting the vertical dev after crossing a much higher altitude restriction. So same arrival, level at FL310, the Vdev ball continues to go down for HAYED at FL180. But you still have quite some room before you really have to start down. If you don't reset it (re-input crossing altitude at later fix, or swap flaps full to flaps 3 and back to full on Perf page), the Vertical dev doesn't recalculate itself. Managed descent at this point will initially start a dive down until the ball comes in, them it starts to shallow it down to ~500/600fpm. Again, not that big a deal. But it's a finesse thing IMO and just better form/more efficient. If you come down 50 miles sooner because the Vdev wasn't reset, then not that big a deal. If I was CA I wouldn't bug the FO about it. But if I'm flying the leg, I'll do stuff like the above. No CA has complained yet
