An easyJet flight bound for Edinburgh returned to Bristol Airport on Wednesday, November 18, 2026, after striking a bird during take-off. The aircraft landed safely, emergency services attended as a precaution, and the airline reported no injuries.

The incident prompted a surge of questions online as flight-tracking services showed the aircraft turning back rather than completing its journey to Scotland. What happened to easyJet flight EZY213, why did the crew declare an emergency, and did passengers eventually reach Edinburgh?

The airline’s account and independent flight reports establish the main sequence of events.

What happened to the easyJet flight from Bristol to Edinburgh?

Flight EZY213, also identified in schedules as U2213, departed Bristol at about 9:24 a.m. GMT on November 18 for a domestic service to Edinburgh.

Shortly after take-off, the aircraft was involved in a bird strike. The crew declared an emergency and turned back, with tracking reports showing the jet returning to Bristol Airport shortly after 10 a.m.

An easyJet spokesperson told the BBC, in comments reported by The Independent, that the aircraft had encountered a bird strike after departure and returned to Bristol as a precaution.

The aircraft landed safely and was met by the airport’s emergency response services. No injuries were reported.

Those details are important because early flight-tracking reports can show an emergency declaration before the public knows why the aircraft has turned around. In this case, the airline provided a specific explanation.

Why did flight trackers show EZY897J?

The flight can appear under several related identifiers depending on the timetable or tracking system.

The commercial flight was identified as EZY213 or U2213 on the Bristol–Edinburgh route. Some tracking displays showed the radio callsign EZY897J.

These identifiers refer to the same affected service, according to contemporaneous aviation tracking coverage. A callsign used by air-traffic control can differ from the passenger-facing number printed in a booking confirmation.

This helps explain apparently conflicting searches for EZY213, U2213 and EZY897J on November 18. Users looking at different tracking applications may encounter different labels for the same aircraft.

The incident concerned the Bristol–Edinburgh flight, rather than a separate emergency involving another easyJet route.

What is a bird strike, and why can it force an aircraft to return?

A bird strike occurs when a bird collides with an aircraft, often during take-off, landing or flight at relatively low altitude.

Birds may strike an aircraft’s fuselage, windscreen or engine. The potential consequences vary widely, from superficial damage to conditions that require pilots to abandon their original flight plan.

The key aviation issue is not the mere presence of a bird. It is whether the collision could affect engine performance, instruments or another part of the aircraft’s safe operation.

An airline may therefore choose to return to the departure airport so that the aircraft can land, undergo inspection and have any necessary repairs performed.

Some aviation coverage has described possible engine damage in the Bristol incident, but the airline’s publicly reported statement confirms the bird strike and safe return rather than providing a complete technical inspection report. The precise extent of any damage should remain subject to engineering confirmation.

What does emergency code 7700 mean?

Flight-tracking services reported an emergency transponder code, commonly known as squawk 7700, while the aircraft was returning.

Code 7700 is the standard general-emergency code used in civil aviation. It helps air-traffic controllers identify an aircraft requiring priority attention.

The code can be associated with many situations, including technical issues, smoke, medical emergencies and other urgent circumstances. It does not by itself prove that an aircraft is about to crash.

In this incident, the declared emergency prompted an appropriate response and return to a suitable airport.

The visible code and flight path can be alarming to people tracking an aircraft online, but the final outcome must be evaluated separately from the alert. The reported result was a safe landing.

Was anybody injured on board?

EasyJet reported that nobody was hurt and the aircraft landed safely at Bristol. Emergency services attended as a precaution, consistent with established procedures when a crew declares an emergency.

The available reports do not establish any passenger or crew injuries. They also do not provide a complete engineering finding or a detailed count of people aboard the affected flight.

It is therefore reasonable to describe the outcome as a safe return with no reported injuries, while leaving technical conclusions to the airline and relevant aviation authorities.

Did the passengers reach Edinburgh?

EasyJet arranged replacement travel so passengers could complete the journey to Scotland. The Independent reported that another easyJet aircraft departed Bristol shortly after midday and reached Edinburgh roughly an hour later.

A detailed aviation report identifies the replacement departure at approximately 12:04 p.m. and arrival at 12:58 p.m., rather than the originally planned arrival around 10:35 a.m.

The result was a delay of a few hours for those travelling on the affected service, rather than the permanent cancellation of their travel plans.

Individual passengers’ final arrangements and any reimbursement rights depend on their booking details and the airline’s response.

Does a bird strike qualify passengers for compensation?

A bird strike can be an extraordinary circumstance under UK and European air-passenger compensation rules. Whether an individual passenger is entitled to compensation depends on the applicable law and the facts of the disruption.

An airline must still assess its obligations relating to care, assistance and onward transport. Those duties can be relevant even when a compensation payment for a disruption is not due.

Passengers should retain their booking details, correspondence and receipts for reasonable expenses and review the airline’s official disruption guidance if they incurred costs.

A precise entitlement cannot be determined solely from the words “emergency landing” or from the flight number; the cause, timing, delay and operator’s reasonable measures matter.

How common are bird strikes at UK airports?

Bird strikes are a known and monitored aviation hazard, and airports use wildlife-management measures to reduce the risk around runways.

Reporting based on UK Civil Aviation Authority data indicates that there were 1,702 recorded bird strikes in the UK during 2025, demonstrating that such encounters are not unprecedented.

The majority of incidents vary in severity, and a reported strike does not automatically mean that passengers were in immediate danger. Flight crews train to deal with abnormal situations, while airlines can remove aircraft from service for inspection where necessary.

The Bristol event illustrates how these layers of aviation safety interact: a crew identified an issue, chose to return, and airport teams prepared for the landing.

What is confirmed about the Bristol emergency landing?

EasyJet flight EZY213/U2213 from Bristol to Edinburgh returned on November 18 after a bird strike shortly after take-off. It declared an emergency, landed safely back at Bristol shortly after 10 a.m., and was met by emergency crews as a precaution.

The airline reported no injuries, while a replacement service subsequently carried passengers onward to Edinburgh.

For anyone searching for easyJet emergency landing, Bristol Airport bird strike or EZY897J, that is the verified explanation. The presence of an emergency code on a flight tracker was the beginning of the response—not the outcome of the flight.