Aviation incidents peaked this year, following the Federal Aviation Administration’s four-hour ground stop. On November 14, a new airline incident happened when a UPS cargo plane and a Copa Airlines passenger jet collided while taxiing at Miami International Airport at night. This collision resulted in two passengers sustaining minor injuries. The Federal Aviation Administration is investigating the incident.
The airport officials reported that the accident occurred at nearly 9:15 p.m. at the intersection of two taxiways. The aircraft involved were a Copa Airlines Boeing 737 and a UPS Boeing 767.
The Federal Aviation Administration reported that the Copa Airlines aircraft’s wingtip struck the nose of the UPS cargo plane. The Copa jet came from Panama City and was taxiing towards the gate. Meanwhile, the UPS aircraft was preparing to depart Miami for Bogotá, Colombia.
Copa Airlines Flight CM427 had 172 people on board, including passengers and staff members. The airline reported that everyone had disembarked at the terminal after the collision. Two passengers sustained minor injuries and received treatment at the scene and did not need hospital transportation.
Air Traffic Control communications are also under investigation; reports indicate controllers instructed the UPS crew to yield to the incoming Copa aircraft. An audio recording of the UPS pilot acknowledging the instruction shows the plane had gone too far past the taxiway intersection. The National Transportation Safety Board is collecting information and is expected to issue a preliminary report in 30 days.
How did the collision affect flights at Miami Airport?
The collision did not cause major flight problems at Miami International Airport. The Miami-Dade Aviation Department reported that aircraft were directed to other taxiways after the incident, and airport operations continued without disruption.
Officials confirmed the collision had no major impact on airport operations, with no widespread delays or cancellations reported after the incident. That said, share your thoughts on the incident above in the comments below, and stay tuned to Travel to Recovery for more updates like this.
Error: No feed found.
Please go to the Instagram Feed settings page to create a feed.
Error: No feed found.
Please go to the Instagram Feed settings page to create a feed.
Error: No feed found.
Please go to the Instagram Feed settings page to create a feed.