Narrative:

We took off on runway 22L at newark and the tower had cleared us to 4000 ft versus 5000 ft specified in the newark 4 departure. Reason being that traffic was holding southwest of the airport at 4700 ft. The captain missed the coplts not calling for climb setting at 1000 ft because he was xchking ILS DME with the HSI DME to see if they matched. In the turn we were both looking for the holding traffic and the TCASII in TA started announcing 'traffic, traffic.' we never saw the traffic and when the copilot returned his scan to the instruments he stated 'why are we going so fast?' he immediately retarded the throttles to idle and pulled the spdbrakes, slowing to 250 KTS from 300 KTS. Factors contributing to the incident are distraction of the captain caused by inadequate knowledge of flight management computer; and standard procedures requiring 2 pilots to simultaneously fly the airplane. A TCASII screaming 'traffic, traffic' demands attention and usually gets it. If we had selected a lower mileage setting on our HSI the traffic may not have seemed so hazardously close. Supplemental information from acn 212652. I as the PF neglected to ask for a climb mode (VNAV or fl ch), but brought flaps up on speed schedule and asked for after takeoff checklist. We changed to departure control after takeoff when instructed. We also were making 'runway 4' turns to 190 degrees, then 220 degrees. I noticed that speed marker was not correct and asked PNF to set 250 but he was busy with radios and xchking DME turn point, so missed it. Caused by poor procedures by not calling for climb mode at 1000 ft, but complicated by poor selection by ewr departure of a holding pattern at the normal departure level off altitude and directly on the departure pattern flight path.

Google
 

Original NASA ASRS Text

Title: SPD DEV IN DEP PROC SID.

Narrative: WE TOOK OFF ON RWY 22L AT NEWARK AND THE TWR HAD CLRED US TO 4000 FT VERSUS 5000 FT SPECIFIED IN THE NEWARK 4 DEP. REASON BEING THAT TFC WAS HOLDING SW OF THE ARPT AT 4700 FT. THE CAPT MISSED THE COPLTS NOT CALLING FOR CLB SETTING AT 1000 FT BECAUSE HE WAS XCHKING ILS DME WITH THE HSI DME TO SEE IF THEY MATCHED. IN THE TURN WE WERE BOTH LOOKING FOR THE HOLDING TFC AND THE TCASII IN TA STARTED ANNOUNCING 'TFC, TFC.' WE NEVER SAW THE TFC AND WHEN THE COPLT RETURNED HIS SCAN TO THE INSTS HE STATED 'WHY ARE WE GOING SO FAST?' HE IMMEDIATELY RETARDED THE THROTTLES TO IDLE AND PULLED THE SPDBRAKES, SLOWING TO 250 KTS FROM 300 KTS. FACTORS CONTRIBUTING TO THE INCIDENT ARE DISTR OF THE CAPT CAUSED BY INADEQUATE KNOWLEDGE OF FLT MGMNT COMPUTER; AND STANDARD PROCS REQUIRING 2 PLTS TO SIMULTANEOUSLY FLY THE AIRPLANE. A TCASII SCREAMING 'TFC, TFC' DEMANDS ATTN AND USUALLY GETS IT. IF WE HAD SELECTED A LOWER MILEAGE SETTING ON OUR HSI THE TFC MAY NOT HAVE SEEMED SO HAZARDOUSLY CLOSE. SUPPLEMENTAL INFO FROM ACN 212652. I AS THE PF NEGLECTED TO ASK FOR A CLB MODE (VNAV OR FL CH), BUT BROUGHT FLAPS UP ON SPD SCHEDULE AND ASKED FOR AFTER TKOF CHKLIST. WE CHANGED TO DEP CTL AFTER TKOF WHEN INSTRUCTED. WE ALSO WERE MAKING 'RWY 4' TURNS TO 190 DEGS, THEN 220 DEGS. I NOTICED THAT SPD MARKER WAS NOT CORRECT AND ASKED PNF TO SET 250 BUT HE WAS BUSY WITH RADIOS AND XCHKING DME TURN POINT, SO MISSED IT. CAUSED BY POOR PROCS BY NOT CALLING FOR CLB MODE AT 1000 FT, BUT COMPLICATED BY POOR SELECTION BY EWR DEP OF A HOLDING PATTERN AT THE NORMAL DEP LEVEL OFF ALT AND DIRECTLY ON THE DEP PATTERN FLT PATH.

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