Luxwing DH8D at Guernsey on Apr 23rd 2024, runway overrun on landing
Last Update: July 2, 2026 / 09:31:42 GMT/Zulu time
Incident Facts
Date of incident
Apr 23, 2024
Classification
Incident
Airline
Luxwing
Flight number
GR-609
Departure
London Gatwick, United Kingdom
Destination
Guernsey, United Kingdom
Aircraft Registration
9H-LWB
Aircraft Type
De Havilland Dash 8 (400)
ICAO Type Designator
DH8D
Airport ICAO Code
EGJB
On Jul 2nd 2026 the AAIB released their final report concluding the probable causes of the serious incident were:
The runway excursion occurred because the Commander, while trying to perform a gentle landing, touched down a considerable distance beyond the landing zone with insufficient runway left to arrest the aircraft using normal braking. The application of full braking force was too late to prevent a low-speed departure from the runway. More proactive exploitation of FDM data may have detected how the flights were being conducted in the early stages of the contract as there was evidence available of previous landings beyond the touchdown zone. In response to the serious incident both the Lessee and the Lessor identified and made changes to their safety management systems.
The AAIB analysed:
Operations
Both the available flight data and CCTV demonstrated the aircraft ‘floating’ down the runway for an extended period of time before touching down. The aircraft was flown below 10 feet above the runway surface for some 10 seconds without reducing below Vapp, during which time it consumed nearly half of the landing distance available. The reason given for this was the commander, as handling pilot, wanting a gentle touchdown.
All three pilots occupying the flightdeck stated that the runway slope had contributed to a lack of visual perspective, meaning that none of them was aware how far down the runway the aircraft had travelled by the time it did finally touchdown. They would, however, have been aware of the prolonged period of time the aircraft had been over the runway, in excess of what should have been considered normal. Equally, all three would have known the relatively short landing distance available, not least because this was the reason given for the commander choosing to be the handling pilot. Under the circumstances, having overshot the touchdown zone on a relatively short runway a go-around would have been expected.
The lack of experience of both the co-pilot and safety pilot, and the seniority gradient existing between them and one of the company’s senior managers, would have made their ability to both identify and communicate any concerns to the commander challenging.
Having touched down, the runway remaining was considerably shorter than planned but, judging he had sufficient runway ahead, the commander delayed applying full braking and did not make use of reverse propeller pitch to slow the aircraft. This proved inadequate to stop the aircraft in the remaining distance, although the aircraft left the runway at relatively low speed. There was still, however, the potential for damage to have been caused, without the crew’s knowledge. This, and the potential to cause damage in trying to taxi back to the runway, should have resulted in a quick decision to shut the aircraft down whilst awaiting assistance. Instead, it was some six minutes before the engines were shut down, and then only after two attempts to taxi the aircraft back onto the runway. Despite an apparent lack of urgency to shut the engines down, when this was done it was without adherence to any normal or emergency checklist, leaving potential for items to be missed.
The investigation highlighted the difficulty of finding the appropriate emergency shutdown checklist in the manufacturer’s QRH. It is accepted that the crew did not attempt to find the checklist and so, in this instance, it is unlikely that this contributed to their failure to use them. It is, however, considered that in other circumstances the difficulty in identifying the emergency shutdown and evacuation checklist may have a significant outcome. The manufacturer is of the view that there is not an issue based on many years of operation and that it is for operators to develop and train on the use of the normal and abnormal emergency procedures. The operators will base their QRH on that provided by the manufacturer and are unlikely to deviate. However, at least one major operator has taken it upon themselves to make the checklist more easily identifiable and accessible.
Organisational factors
An imperative to generate capacity through ACMI contracts was due to a lack of aircraft availability primarily caused by unforeseen problems in the transition from a mixed aircraft fleet to a predominately ATR fleet. This particular ACMI contract was required at short notice after a long-planned alternative fell through unexpectedly.
The short notice nature of the ACMI meant that the change management process for both the Lessee and Lessor, whilst compliant, was time pressured. But there was no evidence that required safety activities or due diligence were compromised prior to the letting of the contract.
Once the contract was established the relationship between the parties appears to have been positive although reactive in nature. For example, agreements on the provision of FDM data were in place but no information containing any safety triggers had been provided to the Lessee by the Lessor prior to the serious incident.
Whilst the Lessor identified problems after the event with the FDM data, analysis of the data provided to the investigation showed there were some triggers for minimal braking and excessive speed at touchdown indicated in the data available to the Lessor prior to the incident flight. The braking triggers were of low severity and some of the airspeed triggers may have been spurious due to wind conditions. However, the investigation considered that a more proactive approach to exploiting the FDM data available may have provided indications to the Lessee and Lessor of how the ACMI flights were being flown in the early stages of the contract. Particularly as CCTV footage identified instances prior to the runway excursion where the aircraft had landed beyond the touchdown zone.
Post the serious incident both the Lessee and the Lessor identified and made changes to their safety management systems. These were primarily aimed at improving operational collaboration in ACMI scenarios, eg observational flight check rides and improved liaison between the operational training and flight crews of the contracting parties.
Engineering
No technical reason could be established to explain why the aircraft veered to the right under braking. The differential in tyre wear between the left and right MLG was assessed by the aircraft design authority as being within the capabilities of the Anti-skid system to manage and performance modelling showed that the single broken stator in one brake unit would have a minimal effect on braking performance.
Regulatory
The ACMI activity was conducted in accordance with regulation and this was not considered a factor in this serious incident. However, during the investigation it was agreed by the UK CAA and CIDCA that enhancements to the current sharing of safety information should be expedited and this resulted in an agreement to generate a formal MoU on safety information exchange between the respective regulators.
Metars:
EGJB 231950Z 36003KT 9999 FEW012 BKN045 09/08 Q1021=
EGJB 231920Z 01003KT 9999 FEW012 BKN048 10/09 Q1021=
EGJB 231850Z 31002KT 9999 FEW010 BKN048 10/09 Q1021=
EGJB 231820Z 27003KT 9999 FEW010 10/09 Q1022=
EGJB 231750Z 30005KT 9999 FEW010 SCT018 10/08 Q1022=
EGJB 231720Z 30006KT 9999 FEW013 SCT018 10/08 Q1022=
EGJB 231650Z 33005KT 9999 -RA FEW013 SCT018 BKN023 09/07 Q1022=
EGJB 231620Z 31005KT 280V360 9999 -RA FEW016 BKN023 09/07 Q1022=
EGJB 231550Z 30007KT 9999 -RA BKN025 10/06 Q1022=
EGJB 231520Z 29008KT 9999 SCT030 BKN045 10/06 Q1022=
EGJB 231450Z 30006KT 270V330 9999 FEW030 BKN045 11/05 Q1023=
Incident Facts
Date of incident
Apr 23, 2024
Classification
Incident
Airline
Luxwing
Flight number
GR-609
Departure
London Gatwick, United Kingdom
Destination
Guernsey, United Kingdom
Aircraft Registration
9H-LWB
Aircraft Type
De Havilland Dash 8 (400)
ICAO Type Designator
DH8D
Airport ICAO Code
EGJB
This article is published under license from Avherald.com. © of text by Avherald.com.
Article source
You can read 2 more free articles without a subscription.
Subscribe now and continue reading without any limits!
Read unlimited articles and receive our daily update briefing. Gain better insights into what is happening in commercial aviation safety.
Send tip
Support AeroInside by sending a small tip amount.
Newest articles
Fleet type match
Iberia A21N and Europa B789 over Atlantic on Jul 10th 2026, TCAS saves the day
An Iberia Airbus A321-200N, registration EC-OLE performing flight IB-140 (dep Jul 9th) from Recife,PE (Brazil) to Madrid,SP (Spain), was enroute…
Fleet type match
Delta B763 near Bangor on Jul 10th 2026, fumes in cockpit
A Delta Airlines Boeing 767-300, registration N178DZ performing flight DL-244 from New York JFK,NY (USA) to Catania (Italy), was enroute at FL350…
Subscribe today
Are you researching aviation incidents? Get access to AeroInside Insights, unlimited read access and receive the daily newsletter.
Pick your plan and subscribePartner
ELITE Simulation Solutions is a leading global provider of Flight Simulation Training Devices, IFR training software as well as flight controls and related services. Find out more.
SafetyScan Pro provides streamlined access to thousands of aviation accident reports. Tailored for your safety management efforts. Book your demo today
AeroInside Blog
Popular aircraft
Airbus A320Boeing 737-800
Boeing 737-800 MAX
Popular airlines
American AirlinesUnited
Delta
Air Canada
Lufthansa
British Airways