Crash of a PZL-Mielec AN-2T in Boralday

Date & Time: Feb 26, 2021 at 1226 LT
Type of aircraft:
Operator:
Registration:
UP-A0351
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Boralday - Kegen
MSN:
1G194-19
YOM:
1981
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft departed Boralday Airport in the suburb of Almaty on an ambulance flight to Kegen with five people on board. Shortly after takeoff, while climbing, the engine suffered a loss of power. The crew attempted an emergency landing when the aircraft lost height and crashed in hilly terrain. All five occupants escaped uninjured while the aircraft was damaged beyond repair. Operator reported as Asia Continental Airlines.

Crash of a Boeing 737-524 off Jakarta: 62 killed

Date & Time: Jan 9, 2021 at 1440 LT
Type of aircraft:
Operator:
Registration:
PK-CLC
Flight Phase:
Survivors:
No
Schedule:
Jakarta - Pontianak
MSN:
27323/2616
YOM:
1994
Flight number:
SJY182
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
56
Pax fatalities:
Other fatalities:
Total fatalities:
62
Captain / Total flying hours:
17904
Captain / Total hours on type:
9023.00
Copilot / Total flying hours:
5107
Copilot / Total hours on type:
4957
Aircraft flight hours:
62983
Aircraft flight cycles:
40383
Circumstances:
On 9 January 2021, a Boeing 737-500 aircraft, registration PK-CLC, was being operated by PT. Sriwijaya Air on a scheduled passenger flight from Soekarno-Hatta International Airport (WIII), Jakarta to Supadio International Airport (WIOO), Pontianak . The flight number was SJY182. According to the flight plan filed, the fuel endurance was 3 hours 50 minutes. At 0736 UTC (1436 LT) in daylight conditions, Flight SJY182 departed from Runway 25R of Jakarta. There were two pilots, four flight attendants, and 56 passengers onboard the aircraft. At 14:36:46 LT, the SJY182 pilot contacted the Terminal East (TE) controller and was instructed “SJY182 identified on departure, via SID (Standard Instrument Departure) unrestricted climb level 290”. The instruction was read back by the pilot. At 14:36:51 LT, the Flight Data Recorder (FDR) data recorded that the Autopilot (AP) system engaged at altitude of 1,980 feet. At 14:38:42 LT, the FDR data recorded that as the aircraft climbed past 8,150 feet, the thrust lever of the left engine started reducing, while the thrust lever position of the right engine remained. The FDR data also recorded the left engine N1 was decreasing whereas the right engine N1 remained. At 14:38:51 LT, the SJY182 pilot requested to the TE controller for a heading change to 075° to avoid weather conditions and the TE controller approved the request. At 14:39:01 LT, the TE controller instructed SJY182 pilot to stop their climb at 11,000 feet to avoid conflict with another aircraft with the same destination that was departing from Runway 25L. The instruction was read back by the SJY182 pilot. At 14:39:47 LT, the FDR data recorded the aircraft’s altitude was about 10,600 feet with a heading of 046° and continuously decreasing (i.e., the aircraft was turning to the left). The thrust lever of the left engine continued decreasing. The thrust lever of the right engine remained. At 14:39:54 LT, the TE controller instructed SJY182 to climb to an altitude of 13,000 feet, and the instruction was read back by an SJY182 pilot at 14:39:59 LT. This was the last known recorded radio transmission by the flight. At 14:40:05 LT, the FDR data recorded the aircraft altitude was about 10,900 feet, which was the highest altitude recorded in the FDR before the aircraft started its descent. The AP system then disengaged at that point with a heading of 016°, the pitch angle was about 4.5° nose up, and the aircraft rolled to the left to more than 45°. The thrust lever position of the left engine continued decreasing while the right engine thrust lever remained. At 14:40:10 LT, the FDR data recorded the autothrottle (A/T) system disengaged and the pitch angle was more than 10° nose down. About 20 seconds later the FDR stopped recording. The last aircraft coordinate recorded was 5°57'56.21" S 106°34'24.86" E. At 14:40:37 LT, the TE controller called SJY182 to request for the aircraft heading but did not receive any response from the pilot. At 14:40:48 LT, the radar target of the aircraft disappeared from the TE controller radar screen. At 14:40:46 LT, the TE controller again called SJY182 but did not receive any response from the pilot. The TE controller then put a measurement vector on the last known position of SJY182 and advised the supervisor of the disappearance of SJY182. The supervisor then reported the occurrence to the operation manager. The TE controller repeatedly called SJY182 several times and also asked other aircraft that flew near the last known location of SJY182 to call the SJY182. The TE controller then activated the emergency frequency of 121.5 MHz and called SJY182 on that frequency. All efforts were unsuccessful to get any responses from the SJY182 pilot. About 1455 LT, the operation manager reported the occurrence to the Indonesian Search and Rescue Agency (Badan Nasional Pencarian dan Pertolongan/BNPP). At 1542 LT, the Air Traffic Services (ATS) provider declared the uncertainty phase (INCERFA) of the SJY182. The distress phase of SJY182 (DETRESFA) was subsequently declared at 1643 LT.
Probable cause:
The following contributing factors were identified:
• The corrective maintenance processes of the A/T problem were unable to identify the friction or binding within the mechanical system of the thrust lever and resulted in the prolonged and unresolved of the A/T problem.
• The right thrust lever did not reduce when required by the A/P to obtain selected rate of climb and aircraft speed due to the friction or binding within the mechanical system, as a result, the left thrust lever compensated by moving further backward which resulted in thrust asymmetry.
• The delayed CTSM activation to disengage the A/T system during the thrust asymmetry event due to the undervalued spoiler angle position input resulted in greater power asymmetry.
• The automation complacency and confirmation bias might have led to a decrease in active monitoring which resulted in the thrust lever asymmetry and deviation of the flight path were not being monitored.
• The aircraft rolled to the left instead of to the right as intended while the control wheel deflected to the right and inadequate monitoring of the EADI might have created assumption that the aircraft was rolling excessively to the right which resulted in an action that was contrary in restoring the aircraft to safe flight parameters.
• The absence of the guidance of the national standard for the UPRT, may have contributed to the training program not being adequately implemented to ensure that pilots have enough knowledge to prevent and recover of an upset condition effectively and timely.
Final Report:

Crash of an Antonov AN-124-100 in Novosibirsk

Date & Time: Nov 13, 2020 at 1210 LT
Type of aircraft:
Operator:
Registration:
RA-82042
Flight Type:
Survivors:
Yes
Schedule:
Seoul - Novosibirsk - Vienna
MSN:
9773054055093
YOM:
1991
Flight number:
VI4066
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine airplane departed Seoul-Incheon Airport on a cargo flight to Vienna, with an intermediate stop in Novosibirsk, carrying 14 crew members and a load consisting of 84 tons of automobile parts. Shortly after takeoff from runway 25 at Novosibirsk-Tolmachevo Airport, while in initial climb, a catastrophic failure occurred on the engine n°2. Several debris punctured the fuselage, damaging slats on both left and right side. As a result, radio communications were cut, the power supply failed and the thrust control on all three remaining engines dropped. The crew entered a circuit for an immediate return despite the aircraft was in an overweight condition for an emergency landing. After touchdown on runway 25 that offered an LDA of 3,597 metres, the crew started the braking procedure but the aircraft was unable to stop within the remaining distance. It overran, lost its both nose gears and slid in a snow covered field before coming to rest 300 metres further. All 14 occupants evacuated safely and the aircraft seems to be damaged beyond repair.
Probable cause:
Failure of the high pressure compressor disk on the engine n°2 during the takeoff procedure.

Crash of a Cessna AC-208B Combat Caravan near Balad: 2 killed

Date & Time: Oct 31, 2020
Type of aircraft:
Operator:
Registration:
YI-118
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Balad - Balad
MSN:
208B-2016
YOM:
2008
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The single engine airplane crashed in unknown circumstances near Balad Airport while completing a local mission. The aircraft was destroyed by a post crash fire and both pilots were killed.

Crash of a Boeing 737-8HG in Kozhikode: 21 killed

Date & Time: Aug 7, 2020 at 1941 LT
Type of aircraft:
Operator:
Registration:
VT-AXH
Survivors:
Yes
Schedule:
Dubai - Kozhikode
MSN:
36323/2109
YOM:
2006
Flight number:
IX1344
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
184
Pax fatalities:
Other fatalities:
Total fatalities:
21
Captain / Total flying hours:
10848
Captain / Total hours on type:
4612.00
Copilot / Total flying hours:
1989
Copilot / Total hours on type:
1723
Aircraft flight hours:
43691
Aircraft flight cycles:
15309
Circumstances:
Air-India Express Limited B737-800 aircraft VT-AXH was operating a quick return flight on sector Kozhikode-Dubai-Kozhikode under ‘Vande Bharat Mission’ to repatriate passengers who were stranded overseas due to closure of airspace and flight operations owing to the Covid-19 pandemic. The aircraft departed from Kozhikode for Dubai at 10:19 IST (04:49 UTC) on 07 August 2020 and landed at Dubai at 08:11 UTC. The flight was uneventful. There was no change of crew and no defect was reported on the first sector. The aircraft departed from Dubai for Kozhikode at 10:00 UTC as flight AXB 1344 carrying 184 passengers and six crew members. AXB 1344 made two approaches for landing at Kozhikode. The aircraft carried out a missed approach on the first attempt while coming into land on runway 28. The second approach was on runway 10 and the aircraft landed at 14:10:25 UTC. The aircraft touched down approximately at 4,438 ft on 8,858 ft long runway, in light rain with tailwind component of 15 knots and a ground speed of 165 knots. The aircraft could not be stopped on the runway and this ended in runway overrun. The aircraft exited the runway 10 end at a ground speed of 84 knots and then overshot the RESA, breaking the ILS antennae and a fence before plummeting down the tabletop runway. The aircraft fell to a depth of approximately 110 ft below the runway elevation and impacted the perimeter road that runs just below the tabletop runway, at a ground speed of 41 knots and then came to an abrupt halt on the airport perimeter road just short of the perimeter wall. There was fuel leak from both the wing tanks; however, there was no postcrash fire. The aircraft was destroyed and its fuselage broke into three sections. Both engines were completely separated from the wings. The rescue operations were carried out by the ARFF crew on duty with help of Central Industrial Security Force (CISF) personnel stationed at the airport and several civilians who rushed to the crash site when the accident occurred. Upon receipt of the information about the aircraft crash the district administration immediately despatched fire tenders and ambulances to the crash site. Nineteen passengers were fatally injured and Seventy Five passengers suffered serious injuries in the accident while Ninety passengers suffered minor or no injuries. Both Pilots suffered fatal injuries while one cabin crew was seriously injured and three cabin crew received minor injuries. The rescue operation was completed at 16:45 UTC (22:15 IST).
Probable cause:
The probable cause of the accident was the non adherence to SOP by the PF, wherein, he continued an unstabilized approach and landed beyond the touchdown zone, half way down the runway, in spite of ‘Go Around’ call by PM which warranted a mandatory ‘Go Around’ and the failure of the PM to take over controls and execute a ‘Go Around’.

The following contributing factors were identitified:

The investigation team is of the opinion that the role of systemic failures as a contributory factor cannot be overlooked in this accident. A large number of similar accidents/incidents that have continued to take place, more so in AIXL, reinforce existing systemic failures within the aviation sector. These usually occur due to prevailing safety culture that give rise to errors, mistakes and violation of routine tasks performed by people operating within the system. Hence, the contributory factors enumerated below include both the immediate causes and the deeper or systemic causes.

(i) The actions and decisions of the PIC were steered by a misplaced motivation to land back at Kozhikode to operate next day morning flight AXB 1373. The unavailability of sufficient number of Captains at Kozhikode was the result of faulty AIXL HR policy which does not take into account operational requirement while assigning permanent base to its Captains. There was only 01 Captain against 26 First Officers on the posted strength at Kozhikode.

(ii) The PIC had vast experience of landing at Kozhikode under similar weather conditions. This experience might have led to over confidence leading to complacency and a state of reduced conscious attention that would have seriously affected his actions, decision making as well as CRM.

(iii) The PIC was taking multiple un-prescribed anti-diabetic drugs that could have probably caused subtle cognitive deficits due to mild hypoglycaemia which probably contributed to errors in complex decision making as well as susceptibility to perceptual errors.

(iv) The possibility of visual illusions causing errors in distance and depth perception (like black hole approach and up-sloping runway) cannot be ruled out due to degraded visual cues of orientation due to low visibility and suboptimal performance of the PIC’s windshield wiper in rain.

(v) Poor CRM was a major contributory factor in this crash. As a consequence of lack of assertiveness and the steep authority gradient in the cockpit, the First Officer did not take over the controls in spite of being well aware of the grave situation. The lack of effective CRM training of AIXL resulted in poor CRM and steep cockpit gradient.

(vi) AIXL policies of upper level management have led to a lack of supervision in training, operations and safety practices, resulting in deficiencies at various levels causing repeated human error accidents in AIXL

(vii) The AIXL pilot training program lacked effectiveness and did not impart the requisite skills for performance enhancement. One of the drawbacks in training was inadequate maintenance and lack of periodic system upgrades of the simulator. Frequently recurring major snags resulted in negative training. Further, pilots were often not checked for all the mandatory flying exercises during simulator check sessions by the Examiners.

(viii) The non availability of OPT made it very difficult for the pilots to quickly calculate accurate landing data in the adverse weather conditions. The quick and accurate calculations would have helped the pilots to foresee the extremely low margin for error, enabling them to opt for other safer alternative.

(ix) The scrutiny of Tech Logs and Maintenance Record showed evidence of nonstandard practice of reporting of certain snags through verbal briefing rather than in writing. There was no entry of windshield wiper snag in the Tech log of VT-AXH. Though it could not be verified, but a verbal briefing regarding this issue is highly probable.

(x) The DATCO changed the runway in use in a hurry to accommodate the departure of AIC 425 without understanding the repercussions on recovery of AXB 1344 in tail winds on a wet runway in rain. He did not caution AXB 1344 of prevailing strong tail winds and also did not convey the updated QNH settings.

(xi) Accuracy of reported surface winds for runway 10 was affected by installation of wind sensor in contravention to the laid down criteria in CAR. This was aggravated by frequent breakdown due to poor maintenance.

(xii) The Tower Met Officer (TMO) was not available in the ATC tower at the time of the accident. The airfield was under two concurrent weather warnings and it is mandatory for the TMO to be present to update and inform the fast changing weather variations to enhance air safety. During adverse weather conditions the presence of the TMO in the ATC tower was even more critical.

(xiii) The AAI has managed to fulfil ICAO and DGCA certification requirements at Kozhikode aerodrome for certain critical areas like RESA, runway lights and approach lights. Each of these, in isolation fulfils the safety criteria however, when considered in totality, this left the aircrew of AXB 1344 with little or no margin for error. Although not directly contributory to the accident causation, availability of runway centreline lights would have certainly enhanced the spatial orientation of the PIC.

(xiv) The absence of a detailed proactive policy and clear cut guidelines by the Regulator on monitoring of Long Landings at the time of the accident was another contributory factor in such runway overrun accidents. Long Landing has been major factor in various accidents and incidents involving runway excursion since 2010 and has not been addressed in CAR Section 5, Series F, Part II.

(xv) DGCA did not comprehensively revise CAR Section 5, Series F, Part II Issue I, dated 30 Sep 99 (Rev. on 26 Jul 2017) on ‘Monitoring of DFDR/QAR/PMR Data for Accident/Incident Prevention’ to address the recommendations of the COI of 2010 AIXL Managlore Crash regarding the exceedance limits, resulting in the persisting ambiguities in this matter.

(xvi) DFDR data monitoring for prevention of accidents/incidents is done by AIXL. However 100% DFDR monitoring is not being done, in spite of the provisions laid down in the relevant CAR and repeated audit observations by DGCA. DFDR data monitoring is the most effective tool to identify exceedance and provide suitable corrective training in order to prevent runway accidents like the crash of AXB 1344. However, ATR submitted by AIXL on the said findings were accepted by DGCA year after year without ascertaining its implementation or giving due importance to its adverse implications.
Final Report:

Ground fire of a Boeing 777-F60 in Shanghai

Date & Time: Jul 22, 2020 at 1520 LT
Type of aircraft:
Operator:
Registration:
ET-ARH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Shanghai – Addis Ababa – São Paulo – Santiago de Chile
MSN:
42031/1242
YOM:
2014
Flight number:
ET3739
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Parked at position 306 at Shanghai-Pudong Airport, the aircraft was prepared for a cargo service to Santiago de Chile with intermediate stops in Addis Ababa and São Paulo, when a fire erupted in the cargo compartment. The aircraft was partially destroyed by fire and damaged beyond repair. No one was injured.

Crash of a PZL-Mielec AN-2R near Kagarkhay: 6 killed

Date & Time: Jul 19, 2020 at 2026 LT
Type of aircraft:
Operator:
Registration:
RA-71276
Flight Phase:
Survivors:
No
Site:
Schedule:
Kyren - Kyren
MSN:
1G207-47
YOM:
1984
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
4280
Captain / Total hours on type:
4236.00
Copilot / Total flying hours:
8363
Copilot / Total hours on type:
8363
Aircraft flight hours:
7382
Circumstances:
The single engine airplane departed Kyren Airport in the afternoon with four employees of the company and two pilots. The purpose of the flight was to familiarize them with the area of ​​the planned aviation chemical works for the processing of the silkworm. As the airplane failed to return to Kyren in the evening, SAR operations were initiated, but abandoned few days later as no trace of the aircraft was found. More than a year later, on July 24, 2021, a group of tourist discovered the burnt wreckage near the Baikonur Pass, in a rocky area, at an altitude of 2,780 metres. The airplane was destroyed by a post crash fire and all six occupants were killed.
Probable cause:
The accident with the An-2 RA-71276 aircraft occurred as a result of a collision with a mountain at an altitude of 2,780 metres above sea level perpendicular to the direction of the ridge with its minimum height of 2,960 metres conditions of limited visibility and the closure of mountain tops by clouds.
The following contributing factors were identified:
- The crew took the decision to perform a flight over a mountainous area with predicted closure of the mountains by clouds and unfavorable wind conditions,
- The crew took the decision to return to the landing site through the mountain range along an unexplored and previously unused route,
- Operational fatigue of the crew due to the significant duration of working hours on the day of the accident (more than 12 hours),
- The airplane falling under the influence of descending air currents on the leeward side of a mountain slope.
Final Report:

Crash of a Beechcraft 350i Super King Air on Mt Artos: 7 killed

Date & Time: Jul 15, 2020 at 2245 LT
Operator:
Registration:
EM-809
Flight Phase:
Survivors:
No
Site:
Schedule:
Van - Van
MSN:
FL-896
YOM:
2015
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The twin engine aircraft departed Van-Ferit Melen Airport at 1834LT on a survey/reconnaissance mission over the province of Hakkari and Van, carrying five passengers and two pilots. At 2232LT, the crew informed ATC about his position vertical to Başkale on approach to Van-Ferit Melen Airport. Thirteen minutes later, the aircraft struck the slope of Mt Artos located 30 km southwest of runway 03 threshold. The aircraft was destroyed upon impact and all seven occupants were killed.

Crash of a PZL-Mielec AN-2R in Kistenovo: 2 killed

Date & Time: Jul 13, 2020 at 0337 LT
Type of aircraft:
Operator:
Registration:
RA-40851
Flight Phase:
Survivors:
No
Schedule:
Bol’shoye Boldino - Bol’shoye Boldino
MSN:
1G174-47
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5036
Copilot / Total flying hours:
2000
Copilot / Total hours on type:
1400
Circumstances:
The crew was completing a spraying mission near the village of Kistenovo, about six km north of Bol'shoye Boldino Airfield. While flying at a low height against sunrise, the crew failed to see and avoid power cables. The single engine airplane collided with cables and a concrete post before crashing in a cornfield, bursting into flames. The copilot was killed and the captain was seriously injured. He died two days later from his injuries. The aircraft was destroyed by a post crash fire.
Probable cause:
The cause of the accident with the An-2 RA-40851 aircraft was the collision of the aircraft with a reinforced concrete support and power transmission lines in a controlled flight while performing the aerial application at an extremely low altitude.
The contributing factors most likely were:
- Field processing when the sun is less than 15° above the horizon and the sun's heading angle is less than 30°,
- Insufficient prudence of the PIC when performing a VFR flight for aerial application,
- Failure of the pilot to take into account the presence of artificial obstacles in the flight area,
- Lack of marking of power lines.
Final Report:

Crash of a Lockheed C-130H3 Hercules at Al Taji AFB

Date & Time: Jun 8, 2020 at 2205 LT
Type of aircraft:
Operator:
Registration:
94-6706
Flight Type:
Survivors:
Yes
Schedule:
Ali Al Salem AFB - Al Taji AAF
MSN:
5398
YOM:
1995
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
1700.00
Copilot / Total hours on type:
506
Circumstances:
On 8 June 2020, at approximately 2205 hours local time (L), the mishap aircraft (MA), a C-130H (tail number (T/N) 94-6706), was involved in a mishap during a routine mobility airlift mission from Ali Al Salem Air Base, Kuwait, into Al Taji (Camp Taji), Iraq, when it failed to come to a stop during landing, overran the runway, and impacted a concrete barrier. All 26 mishap crew (MC) members and passengers survived the mishap, with relatively minor injuries to two of the individuals. The MA was damaged beyond repair, and was valued at $35,900,000. The MA was from the 165th Airlift Wing (165 AW), Georgia Air National Guard (ANG), was manned with Wyoming ANG crew members deployed from the 153d Airlift Wing (153 AW), in Cheyenne, Wyoming, and assigned to the 386th Air Expeditionary Wing (386 AEW) at Ali Al Salem Air Base, Kuwait. The mishap occurred at the end of the first planned leg of the MC’s mission on 8 June 2020. The MC departed Ali Al Salem Air Base, Kuwait, at approximately 2053L, with an uneventful start, taxi, takeoff, and cruise to Camp Taji. During descent into Camp Taji, the MC prepared the MA for a nighttime landing, using night vision devices. During this time, the MC turned the MA earlier than their planned turn point, did not descend to lower altitudes in accordance with their planned descent, and allowed the airspeed to exceed recommended maximum speeds for the configuration the plane was in. During the landing, the MA continued to be above the planned glideslope and maintained excessive airspeed, with a nose-down attitude until touchdown. The MA proceeded to “porpoise” or oscillate down the runway from the point of touchdown until the MA was slowed sufficiently by use of reverse thrust from the engines to allow the MA to settle onto the wheels, which in turn allowed for the brakes to engage. The MA, despite slowing somewhat, had less than 1,000 feet of runway remaining by that point, and thus overran the runway and did not come to a complete stop until it impacted a 12-foot-high concrete barrier, approximately 600 feet past the runway.
Probable cause:
The Accident Investigation Board (AIB) President found by a preponderance of the evidence that the causes of the mishap were the MA’s excess airspeed above recommended landing velocity, which caused the MA to maintain lift (flight) and did not provide sufficient weight on wheels (WOW) to allow braking action to occur. Additionally, the AIB President found, by a preponderance of the evidence, the MC’s failure to adequately assess risk, failure to follow proper procedures, and their poor communication were all substantially contributing factors to the mishap.
Final Report: