MD11 flight crew reported going around at low altitude from an approach to runway 4R at ewr due to w...

Attributes
ACN	1347580
Time
Date	201604
Local Time Of Day	1201-1800
Place
Locale Reference	EWR.Airport
State Reference	NJ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	MD-11
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb Landing
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Captain Pilot Flying
Experience	Flight Crew Last 90 Days 50 Flight Crew Total 12000 Flight Crew Type 1500
Person 2
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 40 Flight Crew Total 6500 Flight Crew Type 2000
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Inflight Event / Encounter Unstabilized Approach
Miss Distance	Horizontal 2000 Vertical 1000

Narrative:

Winds at ewr [were] reporting 310/18 kts gusting 26 kts. But changing constantly. At 100 feet we had a gain of 10 kts followed by a loss of 15 kts at 50 feet. We were sinking at an unstable rate. I immediately set go around thrust and we were flying the missed approach profile 060 heading to 2;500 feet. At about 1;000 feet I saw an airplane in the left corner of my eye crossing our path. I elected to level to 1500 feet and shortly thereafter we received an RA to stay level at that altitude. A lot of radio chatter was taking place during our instructions from the tower to take an immediate right turn to 080 to avoid the traffic. We then turned and climbed to the missed approach altitude of 2;500. Later after reviewing the situation; the departure SID for 4L crosses the departure path of 4R. When you fly the missed approach for 4R to the same altitude both flight paths can cross depending on where the takeoff aircraft on 4L is located. We took corrective action before the RA actually occurred. If we would have climbed to 2;500 and not have turned right; it could have been a closer midair situation.

Original NASA ASRS Text

Title: MD11 flight crew reported going around at low altitude from an approach to Runway 4R at EWR due to windshear. They then discovered that they were in conflict with a departure from Runway 4L and level off at 1;500 feet just as TCAS announces the conflict. Post flight reveals that the EWR2 SID and the missed approach procedure for Runway 4L are initially identical.

Narrative: Winds at EWR [were] reporting 310/18 kts gusting 26 kts. But changing constantly. At 100 feet we had a gain of 10 kts followed by a loss of 15 kts at 50 feet. We were sinking at an unstable rate. I immediately set Go Around thrust and we were flying the missed approach profile 060 heading to 2;500 feet. At about 1;000 feet I saw an airplane in the left corner of my eye crossing our path. I elected to level to 1500 feet and shortly thereafter we received an RA to stay level at that altitude. A lot of radio chatter was taking place during our instructions from the tower to take an immediate right turn to 080 to avoid the traffic. We then turned and climbed to the missed approach altitude of 2;500. Later after reviewing the situation; the departure SID for 4L crosses the departure path of 4R. When you fly the missed approach for 4R to the same altitude both flight paths can cross depending on where the takeoff aircraft on 4L is located. We took corrective action before the RA actually occurred. If we would have climbed to 2;500 and not have turned right; it could have been a closer midair situation.

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