On 13 January 2023, in good night visibility, a Boeing 777-200 with an augmented crew did not comply with its departure taxi clearance and crossed a runway in front of a 737 on the takeoff roll. ATC responded to an automated conflict warning by cancelling the takeoff clearance, and the 737 initiated a high-speed rejected takeoff from approximately 105 knots. Minimum separation as the 777 cleared the edge of the departure runway was approximately 300 metres. The investigation concluded that the 777 operator’s risk controls and the airport’s methods for detecting and preventing runway conflicts were both inadequate.

On 12 March 2022, an ATR76-600 captain made an unstabilised approach to Jabalpur, India, leading to a first bounce more than halfway along the runway and a final touchdown 400 metres from the runway end. The first officer took control but did not commence a go-around, and the aircraft overran the runway before stopping. The captain had just over four months command experience and had made six similar "high-severity long-flare" approaches in the previous five days. These had gone undetected because although such exceedances were supposedly being tracked by company flight data monitoring, this event was not being tracked.

On 16 February 2023, a Boeing 737-700 took off from Las Vegas in excellent night visibility aligned with the right-hand runway edge lights instead of the unlit centreline without pilot awareness during or after the takeoff. Minor nosewheel tyre damage found after flight did not trigger an operator investigation, and the airport only discovered the runway edge lighting damage two days later and did not identify and advise the operator until over a week had passed. The experienced captain had misaligned the aircraft whilst the inexperienced first officer was too busy to monitor the captain’s actions.

On 11 February 2022 an Airbus A320 making a visual approach to Guadeloupe at night was advised by ATC of a descent below the minimum safe altitude. This advisory came as the crew continued the approach after visual reference was temporarily lost. A repeat of this warning by ATC prompted crew recognition that the aircraft was low and off the required approach track. A go-around was initiated from 460 feet agl. The decision to attempt a visual approach in unsuitable circumstances and a delay in recognising the need for a go-around were found to have been symptomatic of poor tactical decision-making.

On 14 September 2022, a Boeing 787-9 inbound to Mumbai lost separation with a Boeing 787-8 also inbound to Mumbai on the same airway. The 787-9 began a descent from FL410 to FL340 at night without clearance close to an air traffic control sector boundary. ATC soon observed the error, but a delay in contacting the 787-9 resulted in it descending to FL389 before being instructed to return to its cleared level. As it passed through FL390 descending and then again when climbing, it came within 3nm of the same-direction 787-8, which was level as cleared at FL390.

On 2 March 2023, an Airbus A380-800 landing at Singapore in heavy rain drifted to the right of the runway centreline after the autopilot was disengaged before touching down close to the runway edge. The aircraft continued to drift right, and the right main landing gear briefly left the runway and damaged several edge lights before regaining it. The handling pilot did not use correct technique to regain the runway centreline, and go-around calls from the monitoring pilot shortly before and immediately after touchdown were not understood/heard despite compliance with such calls being mandatory. 

On 31 January 2022, a Bombardier Challenger 604 pilot lost control during the final stages of a London Stansted night crosswind landing. A bounced nose-gear-first touchdown was followed by a brief runway excursion onto grass before a return to the runway and a climb away. A diversion to London Gatwick followed without further event but subsequent inspection revealed structural and other damage sufficient to result in the aircraft being declared an economic hull loss. The Stansted touchdown was found to have occurred after a premature flare at idle thrust continued towards the stall and a momentary stick pusher activation occurred.

On 24 October 2021, a Bombardier DHC8-400 inbound to Belagavi initially advised to expect a non-precision approach to runway 08 was subsequently cleared for an equivalent approach to runway 26. An approach to runway 08 was then flown without ATC intervention or pilot error recognition, but with no actual consequences. The error was attributed to pilot expectation bias and distraction and controller failure to order a go-around after eventually realising what was happening. The context that had facilitated the errors was considered to be procedure and performance inadequacy at both the aircraft operator and ATC.

On 8 June 2022, a Boeing 757-200 making a night visual approach to Tulsa inadvertently landed on runway 18R instead of 18L as briefed and cleared. ATC did not intervene. Neither pilot recognized the error until the captain realized there was less runway ahead than he had expected. He had planned to "roll long," expecting a the turnoff at the end of the much longer runway 18L. Although both pilots reported not being fatigued, it was concluded that lack of recognition of their error suggested otherwise, and probably facilitated plan continuation bias aided by inability to efficiently integrate available information.

On 3 February 2022, a Boeing 737-200F collided with a tree shortly after a daylight normal visibility takeoff from Puerto Carreño which resulted in engine stoppage although a subsequent restart was partially successful and a return to land was subsequently completed without further event. The collision was attributed to a combination of a slightly overweight takeoff and a slight delay in rotation which in the prevailing density altitude conditions prevented the rate of climb necessary to clear the obstacle. The context for the accident was assessed as a deficient operational safety culture at the company involved. 

On 27 January 2020, an MD83 made an unstabilised tailwind non-precision approach to Mahshahr with a consistently excessive rate of descent and corresponding EGPWS Warnings followed by a very late nose-gear-first touchdown. It then overran the runway end, continued through the airport perimeter fence and crossed over a ditch before coming to a stop partly blocking a busy main road. The aircraft sustained substantial damage and was subsequently declared a hull loss but all occupants completed an emergency evacuation uninjured. The accident was attributed to the actions of the Captain which included not following multiple standard operating procedures.

On 24 October 2021, a Shorts SD360 intending to land at the international airport serving Ndola did so at the recently closed old international airport after visually navigating there in hazy conditions whilst unknowingly in contact with ATC at the very recently opened new airport which had taken the same name and radio frequencies as the old one. The Investigation found multiple aspects of the airport changeover and re-designation had been mismanaged, particularly but not only failure to publish new flight procedures for both airports and ensure that NOTAM communication of the changes internationally had been effective.

On 6 December 2018, a Boeing 737-700 overran the 1,770 metre-long landing runway at destination by 45 metres after entering the EMAS. Normal visibility prevailed but heavy rain was falling and a 10 knot tailwind component existed. The event was attributed to the pilots’ continuation bias in the face of deteriorating conditions and a late touchdown on the relatively short runway. A lack of guidance from the operator on the need for pilots to re-assess the validity of landing data routinely obtained at the top of descent was identified.

On 4 March 2019, an Embraer 145 attempting to land off an ILS approach at Presque Isle in procedure-minima weather conditions flew an unsuccessful first approach and a second in similar conditions which ended in a crash landing abeam the intended landing runway substantially damaging the aircraft. The accident was attributed to the crew decision to continue below the applicable minima without acquiring the required visual reference and noted that the ILS localiser had not been aligned with the runway extended centreline and that a recent crew report of this fault had not been promptly passed to the same Operator.

On 29 November 2017, a Boeing 737-900 on an ILS approach at Atlanta became unstable after the autothrottle and autopilot were both disconnected and was erroneously aligned with an occupied taxiway parallel to the intended landing runway. A go-around was not commenced until the aircraft was 50 feet above the ground after which it passed low over another aircraft on the taxiway. The Investigation found that the Captain had not called for a go around until well below the Decision Altitude and had then failed to promptly take control when the First Officer was slow to begin climbing the aircraft.