Narrative:

I was acting as second in command (pilot not flying) on an IFR flight that departed teb. We received a clearance to our destination via the RUUDY2 RNAV SID. The FMS had been programmed by the pilot in command and confirmed by me to include all elements and requirements of the SID as published. The pilot in command's departure briefing included required minimum climb gradients; departure route description; applicable SID notes; along with standard departure briefing items and noise abatement requirements of runway 24.after takeoff from runway 24 at teb and complying with all SID restrictions; we were given vectors and a climb to 6000ft MSL by new york TRACON and further cleared to intercept the col 350 degree radial to col. The SID as published and depicted by the FMS does not show or make reference to the 350 radial. The pilot in command and I both discussed the quickest most efficient way to implement the modification to our flight plan; and reprogrammed the FMS at a critical time while in VMC.the need to reconfigure for a new routing and maintain vigilance while in VMC caused a distraction. This distraction resulted in neither pilot recognizing the initial power reduction would not prevent the aircraft from accelerating to 330 KIAS. Immediately upon seeing our speed; the pilot in command made a reduction in power and extended the speed brakes. As we were slowing; the controller asked our speed and issued a new heading and cleared us to col. At no time were we informed of a conflict with other traffic nor was any noted with our TCAS.in a high density environment further complicated during VMC; minimizing the load placed on pilots and controllers is a goal that SID and STAR designs should embrace. Had the col 350 degree radial been depicted as part of the RNAV SID and consequently part of the FMS database; the crew would not have been distracted at a critical time.

Google
 

Original NASA ASRS Text

Title: Distracted by the need to program a clearance which is not part of the RUUDY 2 RNAV SID to which they'd been assigned; the Flight Crew of a Falcon jet allowed the jet to accelerate to 330K while below 10;000 MSL.

Narrative: I was acting as Second In Command (Pilot Not Flying) on an IFR flight that departed TEB. We received a clearance to our destination via the RUUDY2 RNAV SID. The FMS had been programmed by the Pilot In Command and confirmed by me to include all elements and requirements of the SID as published. The Pilot In Command's departure briefing included required minimum climb gradients; departure route description; applicable SID notes; along with standard departure briefing items and noise abatement requirements of Runway 24.After takeoff from Runway 24 at TEB and complying with all SID restrictions; we were given vectors and a climb to 6000ft MSL by New York TRACON and further cleared to intercept the COL 350 degree radial to COL. The SID as published and depicted by the FMS does not show or make reference to the 350 Radial. The Pilot In Command and I both discussed the quickest most efficient way to implement the modification to our flight plan; and reprogrammed the FMS at a critical time while in VMC.The need to reconfigure for a new routing and maintain vigilance while in VMC caused a distraction. This distraction resulted in neither pilot recognizing the initial power reduction would not prevent the aircraft from accelerating to 330 KIAS. Immediately upon seeing our speed; the Pilot In Command made a reduction in power and extended the speed brakes. As we were slowing; the Controller asked our speed and issued a new heading and cleared us to COL. At no time were we informed of a conflict with other traffic nor was any noted with our TCAS.In a high density environment further complicated during VMC; minimizing the load placed on pilots and controllers is a goal that SID and STAR designs should embrace. Had the COL 350 degree radial been depicted as part of the RNAV SID and consequently part of the FMS database; the crew would not have been distracted at a critical time.

Data retrieved from NASA's ASRS site as of April 2012 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.