Crash of a Canadair CL-600-2B16 Challenger 604 in Heraklion

Date & Time: Jan 27, 2022 at 0330 LT
Type of aircraft:
Operator:
Registration:
2-SLOW
Flight Type:
Survivors:
Yes
Schedule:
Oxford - Heraklion
MSN:
5422
YOM:
1999
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Oxford-Kidlington Airport, the airplane landed at night on runway 27 at Heraklion-Nikos Kazantzakis Airport. After touchdown, the nose gear failed and the airplane slid for few dozen metres before coming to rest. All seven occupants evacuated safely and the airplane was later considered as damaged beyond repair.

Crash of a Piper PA-31P-425 Pressurized Navajo in Oxford: 2 killed

Date & Time: Jan 15, 2010 at 1407 LT
Type of aircraft:
Operator:
Registration:
N95RS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Oxford - Oxford
MSN:
31-7400221
YOM:
1974
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
12500
Circumstances:
The aircraft had recently been purchased in Germany and was flown to the United Kingdom on 11 December 2009 by the pilot of the accident flight. The new owner, who accompanied him for the flight from Germany, was a private pilot himself and was the passenger in the accident. The aircraft landed at Oxford on the evening of 11 December. The pilot reported to a maintenance organisation that there had been a problem with the brakes after landing and the aircraft was left parked outside a hangar. Minor maintenance was carried out on 20 December 2009 and on 9 January 2010 the aircraft was refuelled, but it was not flown again until the accident flight. On the morning of 15 January 2010 the pilot and his passenger met at Oxford Airport and prepared the aircraft for flight. The plan was to carry out an air test, although its exact nature was not established. The flight was pre‑notified to Royal Air Force (RAF) Brize Norton as an air test with a requested level of FL190. At 1344 hrs the aircraft taxied out to Holding Point C for Runway 19 at Oxford. The pilot reported ‘READY FOR DEPARTURE’ at 1400 hrs and was given a clearance for a right turn after takeoff with a climb initially to FL80. The pilot then requested the latest weather information and the tower controller provided the following information: ‘........TWO THOUSAND METRES IN MIST AND CLOUD IS BROKEN AT 200 FEET.’ At 1403 hrs the takeoff commenced and shortly after liftoff Oxford ATC suggested that the pilot should contact Brize Radar on 124.275 Megahertz (MHz). The pilot made contact with Brize Radar at 1404 hrs, two-way communication was established and the provision of a Deconfliction Service was agreed. On the radar screen the Brize Norton controller observed the ‘Mode C’ (altitude) return increase to around 1,500 ft and then noticed it decrease, seeing returns of 1,300 ft and 900 ft, before the secondary return disappeared. At 1406 hrs the Brize Norton controller contacted Oxford ATC to ask if the aircraft had landed back there and was advised that it had not done so, but that it could be heard overhead. The Brize Norton controller told Oxford ATC that they had a continuing contact, but no Secondary Surveillance Radar (SSR). The Oxford controller could still hear an aircraft in the vicinity and agreed with the Brize Norton controller to attempt to make contact. At 1407 hrs Oxford ATC made several calls to the aircraft but there was no reply. The Oxford controller told the Brize Norton controller there was no reply and was informed in return that there was no longer any radar contact either. The Brize Norton controller also attempted to call the aircraft at 1407 hrs but without success. At 1410 hrs the Oxford controller advised the Brize Norton controller that there was smoke visible to the west of the airfield and they would alert both the airport and local emergency services. In the meantime several witnesses saw the aircraft crash into a field to the west of Oxford Airport. A severe fire started soon afterwards and bystanders who arrived at the scene were not able to get close to the aircraft. The local emergency services were notified of the accident by witnesses at 1407 hrs.
Probable cause:
The post-mortem examination showed that the pilot had severe coronary heart disease and there was evidence to suggest that he may have been incapacitated, or died, prior to the collision with the ground. The passenger was a qualified private pilot but was not experienced with either the aircraft or flight in IMC.
Final Report:

Crash of a Socata TBM-700 in Oxford: 3 killed

Date & Time: Dec 6, 2003 at 1124 LT
Type of aircraft:
Operator:
Registration:
N30LT
Flight Type:
Survivors:
No
Schedule:
Brussels - Oxford
MSN:
201
YOM:
2001
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1573
Captain / Total hours on type:
500.00
Circumstances:
Towards the end of a flight from Brussels to Oxford (Kidlington), the pilot was cleared to land from a visual straight-in approach to Runway 01. The surface wind was reported as 030°/15 kt. As the aircraft crossed the airfield boundary, it started to roll to the left. Shortly after, it struck the ground to the west of the runway threshold. Despite an extensive investigation, no technical malfunction was identified which could have caused the apparent uncontrolled roll to the left. Although there was no other conclusive evidence which would explain the manoeuvre, it is possible that control of the aircraft was lost during application of power to adjust the flight path or in an attempted late go-around, or as a result of an unknown distraction. The passengers was the French businessman Paul-Louis Halley, CEO of Carrefour, accompanied by his wife. They were en route to England to take part to a wedding.
Probable cause:
Despite an extensive investigation, no definite conclusion could be reached as to why N30LT crashed on a visual approach to Oxford (Kidlington) Airport. No technical evidence was found which would explain the uncontrolled roll but there were certain operational possibilities. Without hard evidence, however, none could be fully supported, but loss of control resulting from an unknown distraction, or during the application of power for flight path adjustment or an attempted late go-around, must be considered as possibilities. The lack of a crash protected data, voice or image recording system on N30LT made it impossible to successfully determine a specific cause or causes of this accident.
Final Report:

Crash of a Cessna 550 Citation II in Southampton

Date & Time: May 26, 1993 at 0634 LT
Type of aircraft:
Registration:
G-JETB
Flight Type:
Survivors:
Yes
Schedule:
Oxford - Southampton - Eindhoven
MSN:
550-0288
YOM:
1981
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
16700
Captain / Total hours on type:
850.00
Copilot / Total flying hours:
1322
Copilot / Total hours on type:
109
Aircraft flight hours:
4315
Aircraft flight cycles:
3306
Circumstances:
Cessna Citation G-JETB was to fly eight passengers from Southampton (SOU) to Eindhoven (EIN). Because G-JETB had arrived at Oxford (OXF) the previous evening, the airplane had to be ferried to Southampton early in the morning. This as a regular occurrence. The co-pilot had agreed with the airport authorities at both Oxford and Southampton that the aircraft would operate outside normal hours on the understanding that no fire cover would be provided. Following the takeoff from Oxford at 05:19 the crew contacted Brize Norton ATC and agreed a Flight Information Service. They maintained VMC for the transit at 2,400 feet QNH and called Southampton ATC on their alternate radio at 05:25 when they were approximately 30 nm from Southampton. The Southampton controller was surprised at their initial call and advised them that the airport did not open until 06:00. The crew informed him that arrangements had been made for an early arrival and the controller asked them to standby while he checked this agreement. At 05:27 he called G-JETB, informed the crew that they could land before the normal opening hours and asked them to confirm that no fire cover was required. The crew confirmed this and were then told that runway 02 was in use with a wind of 020 deg./14 kt and that there was a thunderstorm right over the airport. The crew then advised Brize Norton radar that they were going to Southampton ATC and left the Brize Norton frequency. Following a further check with Southampton they were given the 0520 weather observation: "Surface wind 040 deg/12 kt, thunderstorms, 2 oktas of stratus at 800 feet, 3 oktas of cumulonimbus at 1,800 feet, temperature 12 C, qnh 1007 mb, qfe 1006 mb, the runway is very wet." At 05:30 the controller asked the crew for the aircraft type and, after being told that it was a Citation II, told the crew that the visibility was deteriorating ("Now 2,000 metres in heavy thunderstorms" ) and cleared them to the Southampton VOR at 3,000 feet QNH. After checking that they were now IFR the controller confirmed the clearance, and the QNH of 1007 mb, and informed the crew that there was no controlled airspace and that he had no radar available to assist them. Shortly afterwards the controller advised the crew that: "Entirely at your discretion you may establish on the ILS localiser for runway 20 for visual break-off to land on runway 02." The commander accepted this offer and, within the cockpit, asked the co-pilot for the surface wind. He was informed that it was 040 degrees but that earlier they had been given 020 deg/14 kt. At 05:32 the commander had positioned on the ILS for runway 20 and began his descent; the co-pilot advised Southampton that they were established. The controller acknowledged this and again passed the QNH. Shortly afterwards he asked the crew to report at the outer marker and this message was acknowledged. At 05:33 the crew called that they were visual with the runway and the controller cleared them for a visual approach, left or right at their convenience, for runway 02. As this transmission was taking place, the commander informed his co-pilot that they would land on runway 20. The commander decided this because he could see that the weather at the other end of the runway appeared very black and he had mentally computed the tailwind component to be about 10 kt. After a confirmation request from the co-pilot to the commander, the co-pilot informed the Southampton controller that they would land on runway 20. The controller then advised them that: "You'll be landing with a fifteen knot, one five knot, tailwind component on a very wet runway" ; this was immediately acknowledged by the co-pilot with: "roger, copied thank you". The crew continued with their approach, initially at 15 kt above their computed threshold speed (VREF) of 110 kt and then at a constant VREF+10 kt. Within the cockpit the commander briefed the co-pilot that if they were too fast the co-pilot was to select flap to the takeoff position and they would go-around; they also discussed the use of the speedbrake and the commander stated that he would call for it when he wanted it. The speed at touchdown was within 5 kt of the target threshold speed and touchdown was in the vicinity of the Precision Approach Path Indicators (PAPIs), according to witnesses in the Control Tower and on the airport; the commander was certain that he had made a touchdown within the first 300 feet of the runway. The PAPIs are located 267 metres along the runway. Speedbrake was selected as the aircraft touched down and, although the commander applied and maintained heavy foot pressure on the brakes, no retardation was apparent; external observers reported heavy spray from around the aircraft. At some stage down the runway the commander stated that the brakes were not stopping them and the co-pilot called for a go-around ; the commander replied : "No we can't" as he considered that a go-around at that stage would be more dangerous. He maintained brake pressure and, in an attempt to increase distance, steered the aircraft to the right edge of the runway before trying to steer back left. Initially the aircraft nose turned to the left and the aircraft slid diagonally off the right side of the runway on to the grass. It continued across the grass for a distance of approximately 233 metres while at the same time yawing to the left. However, 90 metres beyond the end of the runway there is an embankment which forms the side of the M27 motorway and G-JETB slid down this embankment on to the motorway. The aircraft continued to rotate as it descended and came to rest, having turned through approximately 150 degrees, with its tail on the central barrier. During these final manoeuvres the aircraft collided with two cars travelling on the eastbound carriageway; the aircraft and one of the cars caught fire. During the approach of the aircraft, the airport Rescue and Fire Fighting Service (RFFS) duty officer had discussed with the duty ATC controller the imminent arrival of G-JETB. Although not all checks had been complete, the fire officer offered his two fire vehicles as a weather standby ; he did not declare his section operational but agreed with ATC that they would position themselves to the west of the runway. When the aircraft was 1/2 to 2/3 down the runway, the ATC controller considered that the aircraft would not stop in the runway available and activated the crash alarm. The fire section obtained clearance to enter the runway after G-JETB had passed their position and followed the aircraft. Assessing the situation on the move, the fire officer ordered the FIRE 2 vehicle to disperse through the crash gate to the motorway, and took his own vehicle (FIRE 1) to the edge of the embankment. On arrival, the fire section contained the fires. The occupants of the aircraft and cars escaped with minor injuries.
Probable cause:
The investigation identified the following causal factors:
- The commander landed with a reported tailwind of 15 knots which was outside the aircraft maximum tailwind limit of 10 knots specified in the Cessna 550 Flight Manual.
- The copilot did not warn the commander that he was landing with a reported tailwind component which was outside the aircraft limit.
- With a tailwind component of 10 knots, the landing distance available was less than the landing distance required.
Final Report: