The Smart Marty Sky Dispatch
Jet2 Boeing 737-800 Swerves Off Runway At Birmingham Airport
Jet2 flight LS1310, operated by a Boeing 737-800, swerved off the runway at Birmingham International Airport (BHX) due to Storm Boelo.
Jet2 flight LS1310, operated by a Boeing 737-800, swerved off the runway during its landing at Birmingham International Airport (BHX), according to Travel Radar’s breaking-news report. The incident occurred in conditions associated with Storm Boelo, with strong winds reported as a contributing factor to the deviation from the runway, Travel Radar notes. The event is described as a runway excursion at BHX during the landing phase.
Aviation.Direct adds that the Jet2 passenger aircraft temporarily veered off the runway during its landing at Birmingham Airport. The reporting notes the incident happened on the day of the aircraft’s arrival at Birmingham, and that the account does not specify the exact aircraft model or flight number in the material provided by Aviation.Direct. The source further states that there is no information in the material about injuries, damage, or subsequent actions by airport authorities or Jet2.
Foro3D supplies more precise aircraft details, identifying the involved aircraft as a Jet2 Boeing 737-800 with the registration G-JZHE. Foro3D attributes the event to Birmingham during a storm event locally referred to as Boelo, and timestamps the incident to 25 October 2026, with gusts of wind reaching 29 knots cited as contributing to the runway deviation. The outlet also indicates that there were no serious injuries reported and does not mention any fatalities or significant injuries among passengers or crew, nor details about cabin damage or the number aboard.
According to Foro3D, the Jet2 737-800 (G-JZHE) remains out of service while investigators determine the causes of the runway excursion, signaling that formal assessments and inquiries have begun. This detail aligns with the multi-source narrative that investigators were initiated, though the supplied material does not include formal findings or a cause determination.
Routesonline, in its multi-source aviation update framework, references broader regional and international aviation developments while noting the Birmingham incident within the late-October 2026 window. Routesonline’s contribution clarifies the timing around 25 October 2026 but does not provide additional operational specifics about the flight, aircraft, or immediate airport response beyond the initial reports implicating a Jet2 traveler aircraft veering during landing at Birmingham Airport.
Taken together, the consolidated materials indicate that the incident occurred on 25 October 2026 at Birmingham Airport during a landing in stormy conditions associated with Boelo, with wind gusts reported up to about 29 knots per Foro3D. The material does not provide details about emergency-response actions at the airfield, extent of any damage, or the immediate measures taken by airport authorities beyond stating that the aircraft remains out of service pending investigation. There is no consistent reporting of injuries or fatalities across the supplied sources.
The compiled material consistently identifies the operator as Jet2 and the aircraft type as a Boeing 737-800, with the registration for the referenced airframe noted by Foro3D as G-JZHE. However, the material does not uniformly specify the exact flight number LS1310 in all sources, nor does it detail the number of people aboard, the extent of cabin damage, or any immediate airport-wide operational disruptions beyond the notice that the aircraft is out of service while investigators proceed.
Overall, the event is characterized as a runway excursion during landing at BHX in storm-impacted conditions related to Storm Boelo, with wind gusts cited by a single source as contributing factors. The available sources converge on the core facts: Jet2, 737-800, registration G-JZHE, Birmingham Airport, 25 October 2026, runway deviation during landing, no reported serious injuries or fatalities in the provided material, and an ongoing investigation with the aircraft out of service. The reporting also notes that the exact sequence details, damage assessment, and formal investigation outcomes were not disclosed in the supplied material.