Narrative:

Air carrier X departed runway 4L. Air carrier Y was landing on runway 4R. The preceding aircraft on runway 4R did not clear the runway so I sent air carrier Y around. Air carrier X was departing on the SID which had him on a 060 heading climbing to 3;000 ft. I gave air carrier Y a 080 heading to maintain 2;000 ft. Air carrier X was at 3;000 ft so I turned air carrier Y to a 040 heading to maintain 2;000 ft. As stated in north jo 7210.819-6 when proper spacing cannot be achieved; the go-around maneuver is used to de-conflict aircraft. When IFR aircraft are involved and visual separation; either tower applied or pilot applied cannot be achieved; controllers must issue instructions to establish separation. This could be in the form of vertical separation; passing or diverging separation or vectors to achieve other approved separation. Where wake turbulence may be a factor controllers must exercise their best judgment and issue control instructions to minimize its impact with the proximity of teb arrivals just to the west of ewr departures and lga just to the east of ewr departures there is very little room to do anything but what I did during this event. A recent change of altitudes for the SID from 2;500 ft to 3;000 ft has helped us to obtain altitude separation while staying above the MVA. Unless the teb approach are moved further west and the lga arrivals are moved further east; this maybe the only fix that is possible. We have had some cases of wake remnant events at ewr. We work by the rules set further in the 7110.65; and I can not find my responsibilities for wake remnant. If wake remnant is something that is of concern; can we please have a definition of it and some sort of standard separation put in the 7110.65. Once again I reference the above: where wake turbulence may be a factor controllers must exercise their best judgment and issue control instructions to minimize its impact.

Google
 

Original NASA ASRS Text

Title: EWR Controller described a go around event; the Controller questioning the 'wake remnant' separation standard; noting no rules are currently described in any ATC Directives.

Narrative: Air Carrier X departed Runway 4L. Air Carrier Y was landing on Runway 4R. The preceding aircraft on Runway 4R did not clear the runway so I sent Air Carrier Y around. Air Carrier X was departing on the SID which had him on a 060 heading climbing to 3;000 FT. I gave Air Carrier Y a 080 heading to maintain 2;000 FT. Air Carrier X was at 3;000 FT so I turned Air Carrier Y to a 040 heading to maintain 2;000 FT. As stated in N JO 7210.819-6 When proper spacing cannot be achieved; the go-around maneuver is used to de-conflict aircraft. When IFR aircraft are involved and visual separation; either Tower applied or pilot applied cannot be achieved; controllers must issue instructions to establish separation. This could be in the form of vertical separation; passing or diverging separation or vectors to achieve other approved separation. Where wake turbulence may be a factor controllers must exercise their best judgment and issue control instructions to minimize its impact with the proximity of TEB arrivals just to the west of EWR departures and LGA just to the east of EWR departures there is very little room to do anything but what I did during this event. A recent change of altitudes for the SID from 2;500 FT to 3;000 FT has helped us to obtain altitude separation while staying above the MVA. Unless the TEB approach are moved further west and the LGA arrivals are moved further east; this maybe the only fix that is possible. We have had some cases of WAKE REMNANT events at EWR. We work by the rules set further in the 7110.65; and I can not find my responsibilities for WAKE REMNANT. If WAKE REMNANT is something that is of concern; can we please have a definition of it and some sort of standard separation put in the 7110.65. Once again I reference the above: Where wake turbulence may be a factor controllers must exercise their best judgment and issue control instructions to minimize its impact.

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