Crash of a North American TB-25N Mitchell in Stockton

Date & Time: Sep 19, 2020 at 1925 LT
Registration:
N7946C
Flight Type:
Survivors:
Yes
Schedule:
Vacaville - Stockton
MSN:
108-33263
YOM:
1944
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5100
Captain / Total hours on type:
296.00
Aircraft flight hours:
8099
Circumstances:
While the airplane was in cruise flight and being flown by the copilot, the left engine fuel pressure fluctuated, which was followed by a brief loss of engine power. Concerned that the airplane might have a failed engine-driven fuel pump, the pilot turned the boost pumps to high and asked the passenger (the airplane’s mechanic) to open the fuel cross-feed valve. As the airplane approached its intended destination, both fuel pressure needles began to fluctuate. The pilot assumed that fuel starvation to the engines was occurring and decided to make an off-airport landing to a field behind their airplane’s position due to residential areas located between the airplane’s location and the airport. The pilot stated that he took control of the airplane from the copilot and initiated a right turn toward the field, and that, shortly afterward, both engines lost total power. During the landing roll, the pilot observed a ditch in front of the airplane and was able to get the airplane airborne briefly to avoid the first ditch; however, he was not able to avoid a second, larger ditch. Subsequently, the airplane struck the second ditch, became airborne, and impacted the ground, which resulted in substantial damage to the fuselage. Recovery company personnel reported that, during recovery of the wreckage, about 1 gallon of fuel was removed from the two forward and the two aft wing fuel tanks. Postaccident examination of the airplane revealed no evidence of any pre-existing anomalies that would have precluded normal operation of either engine except that all four main fuel tank fuel gauges displayed erroneous indications after each tank was filled with water. No leaks were observed throughout the fuel system. The airplane was last refueled on the day before the accident with 497.7 gallons. When the airplane was last refueled, the fuel tanks were reportedly filled to about 3 inches below the fuel filler neck. The investigation could not determine, based on the available evidence for this accident, how much of the airplane’s fuel load (maximum capacity was 670 gallons) the airplane had onboard after it was refueled. Additionally, the pilot reported that he commonly used a fuel burn rate of 150 gallons per hour for flight planning purposes; that figure included takeoff fuel burn. Recorded automatic dependent surveillance broadcast data showed that the airplane had flown for 4 hours 1 minute since refueling and included six takeoffs and five landings (but did not include taxi times). As part of the investigation, the pilot estimated that 485.9 gallons of fuel had been used since the last refueling. However, on the basis of the pilot’s initial planned fuel load and recorded flight times, the airplane would have used about 600 gallons of fuel. The pilot later submitted an estimated fuel burn for the flights since refueling of 485.9 gallons. The flight manual did not have fuel burn references for the exact power settings and altitudes flown; thus, the hourly fuel burn could not be determined. The pilot, copilot, and passenger did not visually verify the fuel levels in all four main fuel tanks before the accident flight. The pilot also underestimated the amount of fuel that would be used for the planned flights. As a result, fuel exhaustion occurred, which led to a total loss of engine power.
Probable cause:
A total loss of engine power due to fuel exhaustion. Contributing to the accident was the erroneous fuel gauge indications and inadequate preflight planning and inspection.
Final Report:

Crash of a Fokker 50 in Mogadishu

Date & Time: Sep 19, 2020 at 0755 LT
Type of aircraft:
Operator:
Registration:
5Y-MHT
Flight Type:
Survivors:
Yes
Schedule:
Mogadishu - Beledweyne
MSN:
20171
YOM:
1989
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Mogadishu-Aden Abdulle Airport on a cargo flight to Beledweyne, carrying four crew members and various goods on behalf of the AMISOM, the African Union Mission in Somalia. After takeoff, the crew informed ATC about hydraulic problems and was cleared to return. After touchdown on runway 05, the aircraft went out of control, veered off runway to the right and collided with a concrete wall. Two crew members were slightly injured while both pilots were seriously injured after the cockpit was severely damaged on impact.

Crash of a Piper PA-46-350P Malibu Mirage in Jacksonville

Date & Time: Sep 16, 2020 at 1340 LT
Operator:
Registration:
N972DD
Flight Type:
Survivors:
Yes
Schedule:
Jacksonville - Jacksonville
MSN:
46-36637
YOM:
2014
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
1141.00
Copilot / Total flying hours:
534
Copilot / Total hours on type:
9
Aircraft flight hours:
629
Circumstances:
The instructor pilot reported that while practicing an engine-out landing in the traffic pattern, the pilot-rated student overshot the turn from base leg to final rolling out to the right of the runway centerline. The student pilot attempted to turn back toward the runway and then saw that the airplane’s airspeed was rapidly decreasing. The instructor reported that when he realized the severity of the situation it was too late to do anything. The student attempted to add power for a go-around but was unable to recover. The airplane stalled about 10 ft above the ground, impacted the ground right of the runway, and skidded onto the runway where it came to rest. Both wings and the forward fuselage were substantially damaged. Both pilots stated there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause:
The student pilot’s failure to maintain control of the airplane during the landing approach and the exceedance of the airplane’s critical angle of attack at low altitude resulting in an aerodynamic stall. Contributing was the instructor pilot’s failure to adequately monitor the student pilot’s actions during the approach.
Final Report:

Crash of a Gulfstream G200 in Belo Horizonte

Date & Time: Sep 7, 2020 at 1826 LT
Type of aircraft:
Operator:
Registration:
PR-AUR
Flight Type:
Survivors:
Yes
Schedule:
Belo Horizonte - Belo Horizonte
MSN:
140
YOM:
2006
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training flight at Belo Horizonte-Pampulha Airport, consisting of touch-and-go maneuvers. After landing on runway 13, the pilot-in-command decided to abort the takeoff. Unable to stop within the remaining distance, the aircraft overran, lost its landing gear and came to rest near a concrete block. All three occupants evacuated, among them the captain was slightly injured.

Crash of a Cessna 401A in Arnsberg

Date & Time: Aug 28, 2020 at 1602 LT
Type of aircraft:
Operator:
Registration:
N401JP
Flight Type:
Survivors:
Yes
Schedule:
Marl – Arnsberg
MSN:
401A-0046
YOM:
1969
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6300
Captain / Total hours on type:
500.00
Aircraft flight hours:
4568
Aircraft flight cycles:
5945
Circumstances:
At 1541 hrs, the airplane took off from Marl-Lohmühle Airfield with the pilot and 2 passengers on board to a VFR flight to Arnsberg-Menden Airfield which is located approximately 30 NM to the south-east. One of the passengers was seated in the right-hand seat next to the pilot and the other in the passenger seat behind the pilot. The radar recording of the air navigation service provider showed that the airplane climbed up to 2,200 ft AMSL. Ten minutes after take-off, the pilot established radio contact with Dortmund Tower with the request to cross Dortmund Airport control zone via the reporting point WHISKEY towards reporting point ECHO on his way to Arnsberg. At 1552:14 hrs, the tower controller answered: “[…] melden Sie WHISKEY und dann erwarten Sie Durchflug nach Arnsberg oder ECHO, wie Sie möchten, QNH eins null null eins (report WHISKEY and then expect cross flight to Arnsberg or ECHO, as you like, QNH one zero zero one)“. The pilot confirmed QNH and approach point. At 1555:22 hrs, the pilot reported having reached reporting point WHISKEY at 2,200 ft AMSL. The controller approved the flight through the control zone towards the south. The GPS and radar data showed that at 1556 hrs, the airplane turned tight towards 120° to a direct heading to Arnsberg. At 1559 hrs, as the airplane had left the control zone the controller issued the clearance to leave Tower frequency. At 1600 hrs, about 2.5 NM west of the destination aerodrome, the airplane turned left towards the east. About one minute later the airplane intersected the extended runway centre line of runway 23 at a distance of 0.7 NM from the threshold with an eastern heading. At the time, ground speed was approximately 150 kt. At 1601:39 hrs, the airplane turned left towards the final approach of runway 23. At 1602 hrs, about 1 NM from the threshold of runway 23 at about 1,500 ft AMSL, the airplane reached the extended runway centre line. The Flugleiter (A person required by German regulation at uncontrolled aerodromes to provide aerodrome information service to pilots.) stated that during final approach flaps and landing gear of the airplane had been extended. The approach looked normal. For a short time he had no longer observed the airplane because he had made some entries in the computer. His colleague had then addressed him and drew his attention to the speed of the airplane. The Flugleiter saw that the airplane had an upward large pitch angle, then plunged and disappeared from his sight. The airplane impacted the ground and the 3 occupants suffered severe injuries. The Flugleiter stated he had tried in vain to contact the pilot twice and then raised the alarm. His colleague and other first aiders had driven to the accident site immediately.
Probable cause:
The accident was due to:
• The pilot did not correct the approach by increasing engine power or did not abort the approach.
• The pilot did not monitor the airspeed during the final approach and steered the airplane into an uncontrolled flight attitude during the flare.
To the accident contributed that:
• The approach was not stabilized and not aborted.
• The pilot did not pay attention to the PAPI indication and did not perceive the stall warning.
• The large number of continuously changing approach parameters most likely exceeded the limits of the pilot’s capabilities and subsequently, the airplane was no longer controlled in a goal-oriented manner.
• The runway markings did not comply with the required standards.
Final Report:

Crash of an Antonov AN-26 in Juba: 7 killed

Date & Time: Aug 22, 2020 at 0840 LT
Type of aircraft:
Operator:
Registration:
EX-126
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Juba - Wau - Aweil
MSN:
11508
YOM:
1981
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
Shortly after takeoff from Juba Airport runway 31, while climbing, the aircraft lost height and crashed in a prairie located near Referendom, about 4 km northwest of Juba Airport, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire. A passenger was seriously injured while seven other occupants were killed. The aircraft was on its way to Aweil with an intermediate stop in Wau, carrying a load of foods and money for wages on behalf of the World Food Programme (WFP). It was reported that the aircraft was loaded with 8 tons of cargo while the maximum allowable would be 5,5 tons.

Crash of a Beechcraft 200 Super King Air in Rockford: 1 killed

Date & Time: Aug 20, 2020 at 1542 LT
Operator:
Registration:
N198DM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Rockford - DuPage
MSN:
BB-1198
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3650
Aircraft flight hours:
8018
Circumstances:
On August 20, 2020, about 1542 central daylight time, a Beech B200 airplane (marketed as a King Air 200), N198DM, was destroyed when it was involved in an accident near Rockford, Illinois. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 positioning flight. The purpose of the flight was to relocate the airplane to the pilot's home base at the DuPage Airport (DPA), West Chicago, Illinois. The airplane had been at Chronos Aviation, LLC (a 14 CFR Part 145 repair station), at the Rockford International Airport (RFD), Rockford, Illinois, for maintenance work. Multiple airport-based cameras recorded the accident sequence. The videos showed the airplane taking off from runway 19. Shortly after liftoff, the airplane started turning left, and the airplane developed a large left bank angle as it was turning. The airplane departed the runway to the left and impacted the ground. During the impact sequence, an explosion occurred, and there was a postimpact fire. A video study estimated the airplane’s maximum groundspeed during the takeoff as 105.5 knots (kts). Data recovered from an Appareo Stratus device onboard the airplane showed that about 1538, the airplane began taxing to runway 19. At 1540:34, the airplane crossed the hold short line for runway 19. At 1541:19, the airplane began a takeoff roll on runway 19. At 1541:42, the airplane began to depart the runway centerline to the left of the runway. Subsequent tracklog points showed the airplane gaining some altitude, and the tracklog terminated adjacent to a taxiway in a grassy area. The Appareo Stratus data showed the airplane began to increase groundspeed on a true heading of roughly 185° about 1541. Airplane pitch began to increase at 1541:41 as the groundspeed reached about 104 kts. The groundspeed increased to 107 kts within the next 2 seconds, and the pitch angle reached around 4° nose-up at this time. In the next few seconds, pitch lowered to around 0° as the groundspeed decayed to around 98 kts. The pitch then became 15° nose-up as the groundspeed continued to decay to about 95 kts. A right roll occurred of about 13° and changed to a rapidly increasing left roll over the next 5 seconds. The left roll reached a maximum of about 86° left as the pitch angle increasingly became negative (the airplane nosed down). The pitch angle reached a maximum nose down condition of -73°. The data became invalid after 1541:53.4. An airplane performance study based on the Appareo Stratus data showed that during the takeoff from runway 19, the airplane accelerated to a groundspeed of 98 kts and an airspeed of 105 kts before rotating and lifting off. The airplane pitched up, climbed, and gained height above the ground. Then, 4 seconds after rotation, the airplane began descending and slowing, consistent with a loss of power. A nose-left sideslip, a left side force, and a left roll were recorded, consistent with the loss or reduction in thrust of the left engine. The sideslip was reduced, likely due to opposite rudder input, and the airplane briefly rolled right. The airplane pitched up and was able to begin climbing again; however, it continued to lose speed. The sideslip then reversed, and the airplane rolled left again and impacted the ground. One witness reported that he observed the accident sequence. He did not hear any abnormal engine noises, nor did he see any smoke or flames emit from the airplane before impact. The airplane came to rest on a flat grass field to the east of runway 19 on airport property. The airplane sustained fire damage and was fragmented from impacting terrain.
Probable cause:
The pilot’s failure to maintain airplane control following a reduction of thrust in the left engine during takeoff. The reason for the reduction in thrust could not be determined based on the available evidence.
Final Report:

Crash of a Cessna 208B Grand Caravan in Fangak

Date & Time: Aug 16, 2020
Type of aircraft:
Operator:
Registration:
5Y-SAV
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
208B-0312
YOM:
1992
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft completed a humanitarian flight from Juba to Fangak on behalf of the NGO 'Nile Hope'. On board were five passengers and two pilots. During the takeoff roll on a muddy airstrip, the aircraft went out of control, veered off runway and collided with a tree. The right wing was torn off and the aircraft came to rest upside down. Two passengers were slightly injured.

Crash of a Cessna 340A in Orléans

Date & Time: Aug 10, 2020 at 1355 LT
Type of aircraft:
Operator:
Registration:
N413JF
Flight Type:
Survivors:
Yes
Schedule:
Perpignan – Orléans
MSN:
340A-0746
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2635
Captain / Total hours on type:
41.00
Circumstances:
Then twin engine airplane departed Perpignan-La Llabanère Airport on a private flight to Orléans, carrying one passenger and one pilot. On final approach to Orléans-Loiret Airport (ex Saint-Denis-de-l’Hôtel), the pilot encountered a loss of power on the left engine. He attempted an emergency landing when the airplane impacted trees and crash landed in a wooded area located about 3 km short of runway 23, bursting into flames. Both occupants escaped uninjured while the airplane was totally destroyed by a post crash fire.
Probable cause:
The exact cause of the loss of power on the left engine could not be determined. The pilot, concentrating on monitoring the approach parameters, did not immediately realize the left engine malfunction. He noticed that the aircraft's rate of descent was too high to follow the standard approach slope. The pilot first attempted to go around and reconfigured the aircraft to do so by retracting the landing gear and flaps. In spite of these actions, the pilot noticed that the power delivered by the aircraft's engines did not allow him to recover the plane and understood, by being aware of the action of his right foot on the rudder pedal, that the power delivered by the left engine was abnormally low. Given the low height of the plane at the time of this observation, the pilot decided to land in the country. Contributing to the high rate of descent after the occurrence of the left engine malfunction was the fact that the drags were extended at the time the engine power decreased and the fact that the left propeller probably windmilling until the landing.
Final Report:

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: