2010-05 · NASA ASRS report 889665
A GLF-5 flight crew failed to comply with the 1500 MSL crossing restriction at WENTZ while flying the RUUDY 2 RNAV SID from TEB.
We were assigned; and briefed; the RUUDY2 RNAV departure; including 1500' crossing limit at WENTZ. The crossing altitudes were confirmed in FMS; 1500' was set on Altitude Preselect; and LNAV was selected on Display Controller. During initial climb; passing 500'; I called 1000' to go; and noted that an unexpected left turn was started. I called the deviation; and noted that the pilot flying's navigation source was 'Green Nav' [VOR] instead of the needed 'Blue Nav' (FMS); and it was commanding a left turn. I advised the problem; and the pilot flying requested that I switch his navigation to FMS.I leaned across pedestal to select the correct navigation source on pilot flying's glare shield; and looked back at panel to see us going through 1500' as we approached WENTZ; leveling at 2000' (the altitude limit after passing WENTZ). I called the altitude deviation; and reported altitude to Departure Control; who was justifiably unhappy. Immediately after confirming that we had overshot the altitude; the controller advised that we were now clear of the Newark arrival path; and cleared us for further climb.I believe that the primary contributing factor to the overshoot was the distraction caused by the improperly selected NAV source on pilot flying's side; which was compounded by loss of the monitoring support of the pilot not flying (me) while my attention was focused on correcting the navigation source selection. Although we discussed that this would be an LNAV departure; and LNAV was selected on the Display Controller; FMS was apparently not selected on the pilot flying's side. Note - the default; 'power-up' setting for navigation source on the GLF5 is automatically FMS. Had this been an originating flight; this would not have been a factor; as the source would have already been FMS. As we had used 'Green Nav' during our TEB arrival; however; it remained selected on pilot flying side for departure. If I could replay this departure; upon noting that there was a guidance error on pilot flying's side; I would have just assumed control of the aircraft until the pilot flying was able to correct his setup; insuring that we remained on profile. This also reinforces that we must not only set our own source; but check the other side.
...after setting up the FMS and guidance panel for the departure; and set to long range nav; we waited for takeoff for 20 mins. I was distracted resetting guidance to LNAV and I flew through 1500 to 2000 and leveled off near WENTZ.Also if LNAV goes off; or needs reselecting; get the right seat pilot to set it as I fly the airplane to the correct heading and altitude.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.