EMB-135 flight crew reported after push back and beginning of taxi they had to stop to avoid a helicopter descending to land on the ramp. The helicopter also took evasive action.

2025-02 · NASA ASRS report 2212482

Date: 2025-02 · Aircraft: EMB ERJ 135 ER/LR · Phase: taxi

Anomalies: atc-issue-all-types|conflict-ground-conflict|critical

Synopsis

EMB-135 flight crew reported after push back and beginning of taxi they had to stop to avoid a helicopter descending to land on the ramp. The helicopter also took evasive action.

Narrative

As we were preparing to taxi out of the ramp; First Officer (FO) called ZZZ ATC Ground Control. The frequency was combined on 121.1; so it was very busy. We were positioned with the aircraft facing north. We received clearance to taxi Runway XXL at Taxiway 1 via 2. I signaled to our ramp agent that we were ready to taxi as FO read back our taxi clearance. The ramp agent waved us forward without any indication of an issue. As we began to turn out of the ramp onto [Taxiway] 2; I stated 'clear left;' and FO said 'stop.' I stopped and watched a helicopter; fly over the top of the aircraft and land at the nearby helicopter hangar. The helicopter appeared extremely low - approximately 20 feet over the ground when I saw it off my left side. Our aircraft physically shook from the vibrations and I could hear its engine over my noise cancelling headphones. I believe it was low enough that had FO not ordered me to stop; the helicopter would have hit our tail. FO stated that it appeared the helicopter pulled up briefly when they had gotten it in sight. It did not appear the ramp agent saw the helicopter until after the incident. After the helicopter passed; we continued our taxi. Ground frequency was still busy so I called our ZZZ station and informed them of the incident. It is unclear to us what frequency ZZZ helicopter control was on; but we did not hear any communication between the helicopter and ATC. We taxied and took off without further incident.Cause: Radio congestion/lack of communication and coordination between ATC and themselves/other aircraft. Being in a position where we could not see traffic until last second. Helicopter was too low. No alert of potential conflict from ramp. Complacency/not expecting the helicopter to be there. Bad timing.Suggestions: ATC should have alerted us to the helicopter traffic or ordered the helicopter to give way. Helicopter should not come in so low when an aircraft is parked in a position to exit ramp; especially with beacon on.

Second reporter narrative

Captain and First Officer (FO) received taxi clearance to XXL at [Taxiway] 1 via 2. ATC was extremely busy. Aircraft had emerged from spot X; between parked aircraft and another company aircraft. Ramp agent give ok signals to taxi out; no references to traffic. Beginning taxi from non-movement to [Taxiway] 2; Captain verbalizes 'clear left' while FO checks the right; scanning till the end of the right wingtip; seeing no obstructions or traffic in sight. FO checks again and says 'wait' when seeing a helicopter suddenly emerge; who is aggressively pulling up to avoid collision. Captain immediately stops taxi as helicopter flies over our aircraft. Should Captain had continued taxi; helicopter would have struck our tail. Ground crew later mentioned that helicopter cleared our tail by a few feet. Captain notified company ground crew of the event. Flight continued and operations continued as normal.Cause: Lack of communication between helicopters and company ground crews. Lack of communication between ground crews and helicopter. Lack of communication between company ground crew and flight crew. 'Blind spots' for helicopter and ground crew due to tail of the aircraft parked in spot Y. Abnormal approach and landing pattern from helicopter.Suggestions: Visual communication between helicopter and ground crew. Normal traffic pattern for helicopter. Communication between helicopter company and company ground crew. Assurance from ramp agents to flight crew of no approaching helicopters.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.