BAe 125 Series 800
Flight Crew Air Transport Pilot (ATP)
Human-Machine Interface
Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Human Factors
We were issued the RUUDY 4 RNAV departure out of Teterboro.  The  FMS was set up as well as the mode select panel and then briefed.  As part of the setup and brief VNAV was selected in order to capture the intermediate level off at 1500 to cross WENTZ intersection and then climb to 2000 ft.  We then discovered that the passengers were to be 2 hours late the APU was shut down to conserve fuel.  when we came back out to set up quickly the VNAV selector was missed.  0nce nearly reaching 1500 I recognized that VNAV was not selected and that the flight director was not going to depict a level off at 1500.  I quickly responded with a further throttle reduction and a manual level off.  Our indicated altitude reached 1600 with a rapid recovery to 1500.  The flight was then continued without further complication.  Hyper vigilance is necessary to assure proper setup of automation; especially when things are not happening as expected with passengers; weather; etc.
Suggestions.  Instead of using VNAV to climb simply put the first alititude asigned into the altitude alerter and once captured continue dialing in each new altitude as the departure requires. If passengers are going to be late better communication between broker and TMC so the pilots can prepare better for each departure. If electronics are shut down before a departure a full pre-brief should be conducted prior to engine start. If flying VNAV departures a verify VNAV armed could be added to the before take off checklist or taxi checks.
Hawker 850 Captain reports an overshoot during the RUUDY 4 RNAV departure from TEB.