37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1434628 |
Time | |
Date | 201703 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | EWR.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 240 Flight Crew Type 7425 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Ground Event / Encounter Other / Unknown Inflight Event / Encounter Other / Unknown |
Narrative:
Approaching newark airport the current winds with gusts favored a visual approach to runway 29. Runway 22 left was also available for landings. We asked for; and received a clearance to proceed with the stadium visual approach to runway 29. Runway 22 right at intersection whiskey was being used for departures. As we proceeded with the approach; at approximately 1.5 miles from touchdown; we asked for and received a wind check. As I flared for landing; I was hit by the jet blast from a departing B737 on runway 22 right. I was able to recover and make a normal landing on runway 29. The side load on the aircraft was substantial. The tower controller asked us for a braking action report. We responded with 'good'; followed by a comment about being hit by jet blast from the departing B737. The response from tower was unreadable followed by 'contact ramp'. Once we were clear of the runway; we contacted ramp. They asked if we were assigned runway 29 for landing. We told them we requested runway 29. Once in the gate; I called ground control and asked for a phone number to call the tower and discuss what had happened.I called the tower and talked to a controller about what had occurred. I asked him about the procedures for simultaneous departures and arrivals with regards to jet blast avoidance. The controller told me they are allowed to depart aircraft off of 22 right at whiskey as long as the aircraft is given a takeoff clearance prior to and is rolling prior to the landing aircraft reaches 1 mile final for runway 29. Heavy aircraft must hold with idle thrust only. Of course; the tower expects aircraft cleared to depart immediately. This is not what occurred.after reviewing the ATC transmissions for ewr tower; it was obvious the protocols for simultaneous departures were followed; but due to a delayed departure by [the B737] resulted in the jet blast hitting a landing aircraft.I did have an opportunity to speak with [the] ops manager at the ewr tower. He knew about the occurrence; and that an investigation had been started. He also told me the controller was being given a performance review. He also admitted mistakes were made. Obviously; this could have been a real disaster with loss of aircraft and life. After further thought and research on what occurred; I have come to some conclusions and recommendations to help create a safer environment for simultaneous arrivals and departures for runway 22 right and runway 29. Strict adherence to the one mile rule with simultaneous arrivals and departures runway 22 right and 29. The controller must maintain vigilance whether the aircraft cleared for takeoff on 22 right is actually rolling with takeoff thrust. If the departing aircraft on 22 right delays in any way; or takes longer than the norm; the controller should cancel the takeoff clearance. The 22 right departing aircraft must be made aware of the aircraft approaching to land on 29. While the departing aircraft is relying on the controller for separation and guidance; they also need to exercise common sense. If the pilots feel it's taking longer to depart when the tower expects an immediate departure; the pilot should cancel his or her takeoff clearance. In other words; the pilot should be the final person to determine whether their jet blast will become a safety issue. As the 22 right departing aircraft is taxiing into position; the pilots should take a look up the final for 29. Getting the big picture so to speak. I mentioned this particular controller was unreadable at times and spoke way too fast to be understood. He stated this was also being looked at.the following day; we [departed] ewr. The roles were reversed; in that we were the departing aircraft on 22 right at yankee; not whiskey. There is apparently no restrictions for departing aircraft from 22 right from yankee versus whiskey. We were cleared for takeoff while off the runway. As I was 90 degrees to runway 22 right; I could see an aircraft on short finalfor 29. I elected to cancel our takeoff clearance and hold on the runway. The controller was not happy. I later told him why we waited. He explained that yankee does not have the restriction. I gave the landing aircraft due consideration. I saw the big picture. I broke the chain of events. Consideration by all involved promotes a safe environment for all. I recommend that our safety committee review this occurrence and come up with recommendations for our pilots to follow. Being considerate of all those aircraft around you may save lives.
Original NASA ASRS Text
Title: B757 Captain reported the aircraft was subjected to 'substantial' side loads while landing at EWR on Runway 29 when they encountered jet blast from an aircraft departing Runway 22R.
Narrative: Approaching Newark airport the current winds with gusts favored a visual approach to runway 29. Runway 22 left was also available for landings. We asked for; and received a clearance to proceed with the Stadium Visual approach to runway 29. Runway 22 right at intersection Whiskey was being used for departures. As we proceeded with the approach; at approximately 1.5 miles from touchdown; we asked for and received a wind check. As I flared for landing; I was hit by the jet blast from a departing B737 on runway 22 right. I was able to recover and make a normal landing on runway 29. The side load on the aircraft was substantial. The tower controller asked us for a braking action report. We responded with 'good'; followed by a comment about being hit by jet blast from the departing B737. The response from tower was unreadable followed by 'contact ramp'. Once we were clear of the runway; we contacted ramp. They asked if we were assigned runway 29 for landing. We told them we requested runway 29. Once in the gate; I called ground control and asked for a phone number to call the Tower and discuss what had happened.I called the Tower and talked to a Controller about what had occurred. I asked him about the procedures for simultaneous departures and arrivals with regards to jet blast avoidance. The Controller told me they are allowed to depart aircraft off of 22 right at whiskey as long as the aircraft is given a takeoff clearance prior to and is rolling prior to the landing aircraft reaches 1 mile final for runway 29. Heavy aircraft must hold with idle thrust only. Of course; the tower expects aircraft cleared to depart immediately. This is not what occurred.After reviewing the ATC transmissions for EWR tower; it was obvious the protocols for simultaneous departures were followed; but due to a delayed departure by [the B737] resulted in the jet blast hitting a landing aircraft.I did have an opportunity to speak with [the] ops manager at the EWR tower. He knew about the occurrence; and that an investigation had been started. He also told me the controller was being given a performance review. He also admitted mistakes were made. Obviously; this could have been a real disaster with loss of aircraft and life. After further thought and research on what occurred; I have come to some conclusions and recommendations to help create a safer environment for simultaneous arrivals and departures for runway 22 right and runway 29. Strict adherence to the one mile rule with simultaneous arrivals and departures runway 22 right and 29. The controller must maintain vigilance whether the aircraft cleared for takeoff on 22 right is actually rolling with takeoff thrust. If the departing aircraft on 22 right delays in any way; or takes longer than the norm; the controller should cancel the takeoff clearance. The 22 right departing aircraft must be made aware of the aircraft approaching to land on 29. While the departing aircraft is relying on the controller for separation and guidance; they also need to exercise common sense. If the pilots feel it's taking longer to depart when the tower expects an immediate departure; the pilot should cancel his or her takeoff clearance. In other words; the pilot should be the final person to determine whether their jet blast will become a safety issue. As the 22 right departing aircraft is taxiing into position; the pilots should take a look up the final for 29. Getting the big picture so to speak. I mentioned this particular controller was unreadable at times and spoke way too fast to be understood. He stated this was also being looked at.The following day; we [departed] EWR. The roles were reversed; in that we were the departing aircraft on 22 right at yankee; not whiskey. There is apparently no restrictions for departing aircraft from 22 right from yankee versus whiskey. We were cleared for takeoff while off the runway. As I was 90 degrees to runway 22 right; I could see an aircraft on short finalfor 29. I elected to cancel our takeoff clearance and hold on the runway. The controller was not happy. I later told him why we waited. He explained that yankee does not have the restriction. I gave the landing aircraft due consideration. I saw the big picture. I broke the chain of events. Consideration by all involved promotes a safe environment for all. I recommend that our safety committee review this occurrence and come up with recommendations for our pilots to follow. Being considerate of all those aircraft around you may save lives.
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.