Narrative:

During departure from teb with clearance for the ruudy 2 RNAV departure; white intersection; as filed; and after complying with initial altitude restrictions of departure procedure; was cleared to 4;000 and asked if familiar with elvae intersection. Then was cleared to intercept col 350 radial to col with no further instruction after intercept. While trying to set up for the new instructions and climb an overshoot of the assigned altitude occurred by approximately 400 ft and followed by controller inquiry of altitude. He informed us of approaching traffic 2;000 ft above; we confirmed leveling at 4;000 ft. This clearance deviation from issued clearance occurs on a regular basis for southbound departures for the white transition. Departure control issues these changes which are not part of the ruudy 2 RNAV departure but appear to be referenced on the liberty departure for ewr. When questioning further clearance instructions we are told to fly the departure procedure. This is confusing since clearance issued is a conflict with controller instructions. These last minute changes require heads down and multiple actions to try and set up for the non-standard departure that was already set up in the FMS as part of the original clearance. This creates unneeded cockpit distraction. It appears that the controllers are unfamiliar with the ruudy 2 RNAV departure. When questioning controllers we are told to fly procedure assigned; when their instructions are contrary to published procedure. These actions are very distracting to the cockpit while trying operate in a high workload; low altitude; congested environment.

Google
 

Original NASA ASRS Text

Title: A passenger jet departed TEB on the RUUDY 2 RNAV but was unexpectedly cleared to intercept the COL 350 degree radial. The crew was distracted and confused so while programming the FMC the crew overshot the assigned altitude by 400 FT.

Narrative: During departure from TEB with clearance for the RUUDY 2 RNAV Departure; WHITE intersection; as filed; and after complying with initial altitude restrictions of departure procedure; was cleared to 4;000 and asked if familiar with ELVAE Intersection. Then was cleared to intercept COL 350 radial to COL with no further instruction after intercept. While trying to set up for the new instructions and climb an overshoot of the assigned altitude occurred by approximately 400 FT and followed by Controller inquiry of altitude. He informed us of approaching traffic 2;000 FT above; we confirmed leveling at 4;000 FT. This clearance deviation from issued clearance occurs on a regular basis for southbound departures for the WHITE transition. Departure Control issues these changes which are not part of the RUUDY 2 RNAV Departure but appear to be referenced on the LIBERTY Departure for EWR. When questioning further clearance instructions we are told to fly the departure procedure. This is confusing since clearance issued is a conflict with controller instructions. These last minute changes require heads down and multiple actions to try and set up for the non-standard departure that was already set up in the FMS as part of the original clearance. This creates unneeded cockpit distraction. It appears that the controllers are unfamiliar with the RUUDY 2 RNAV Departure. When questioning Controllers we are told to fly procedure assigned; when their instructions are contrary to published procedure. These actions are very distracting to the cockpit while trying operate in a high workload; low altitude; congested environment.

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.