37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1319074 |
Time | |
Date | 201512 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | EWR.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 209 Flight Crew Total 15000 Flight Crew Type 7138 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe |
Narrative:
While descending into ewr; we briefed a visual approach to 22L as per the ATIS. Approach control assigned us runway 11 which was not advertised on ATIS. We re-briefed and then flew the 11 visual. Approach control began a series of speed reductions (180; 170; 160; etc). We complied with all requests promptly. There was no traffic ahead of us for 11 so we were a bit confused as to why there was so many speed reductions. I'm guessing they were sequencing us with 22L traffic. At about 1000 feet ATC said 'this is not going to work; aircraft X go around.' we executed the missed approach and were vectored to downwind for runway 11 again. I was doing 180 kts on downwind which I thought was very reasonable. ATC pointed out traffic on final to us. We called traffic in sight and we were cleared for the visual approach. I planned to give myself a little room so as not to crowd the preceding aircraft. Soon thereafter ATC said 'aircraft X; start your base turn now. I need to keep you in tight.' we complied with instructions and didn't feel we were too fast. We configured and were stabilized; and then shortly thereafter ATC said 'aircraft X; you've got 60 kts overtake; s-turn to the right approved; slow to lowest practical.' we did this; and things looked good initially. The preceding aircraft was told 'minimum time on runway.' unfortunately; they missed their expected right turnoff. Tower then said exit runway to the left. The preceding aircraft said 'unable.' at this point; tower said 'aircraft X; go around.' we performed another missed approach. The missed approaches were performed per SOP. We were vectored for runway 22L and landed without incident. I believe ATC failed to keep us adequately spaced and set us up for these multiple missed approaches. The most confusing part was when ATC initiated our base turn and told us to keep it tight. Shortly thereafter; they told us we were too tight. Our speed was not excessive-180 kts to the marker; and then a normal speed reduction to approach speed. I also think trying to sequence runway 11 traffic with 22L traffic was a contributing factor. The only thing I would possibly do differently is disregard the early base turn instructions; but it is not my habit to disregard ATC instructions. Another factor was the preceding aircraft's failure to exit the runway promptly.
Original NASA ASRS Text
Title: After complying with multiple ATC speed and heading clearance modifications during two visual approaches to EWR; air carrier crew performed two Tower-directed go-around procedures. The third visual approach; to a different runway; was successful.
Narrative: While descending into EWR; we briefed a visual approach to 22L as per the ATIS. Approach Control assigned us runway 11 which was not advertised on ATIS. We re-briefed and then flew the 11 visual. Approach Control began a series of speed reductions (180; 170; 160; etc). We complied with all requests promptly. There was no traffic ahead of us for 11 so we were a bit confused as to why there was so many speed reductions. I'm guessing they were sequencing us with 22L traffic. At about 1000 feet ATC said 'This is not going to work; Aircraft X go around.' We executed the missed approach and were vectored to downwind for runway 11 again. I was doing 180 kts on downwind which I thought was very reasonable. ATC pointed out traffic on final to us. We called traffic in sight and we were cleared for the visual approach. I planned to give myself a little room so as not to crowd the preceding aircraft. Soon thereafter ATC said 'Aircraft X; start your base turn now. I need to keep you in tight.' We complied with instructions and didn't feel we were too fast. We configured and were stabilized; and then shortly thereafter ATC said 'Aircraft X; you've got 60 kts overtake; S-turn to the right approved; slow to lowest practical.' We did this; and things looked good initially. The preceding aircraft was told 'minimum time on runway.' Unfortunately; they missed their expected right turnoff. Tower then said exit runway to the left. The preceding aircraft said 'unable.' At this point; tower said 'Aircraft X; Go Around.' We performed ANOTHER missed approach. The missed approaches were performed per SOP. We were vectored for runway 22L and landed without incident. I believe ATC failed to keep us adequately spaced and set us up for these multiple missed approaches. The most confusing part was when ATC initiated our base turn and told us to keep it tight. Shortly thereafter; they told us we were too tight. Our speed was not excessive-180 kts to the marker; and then a normal speed reduction to approach speed. I also think trying to sequence runway 11 traffic with 22L traffic was a contributing factor. The only thing I would possibly do differently is disregard the early base turn instructions; but it is not my habit to disregard ATC instructions. Another factor was the preceding aircraft's failure to exit the runway promptly.
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.