Crash of a De Havilland DHC-2 Beaver I off Lopez Island

Date & Time: Sep 30, 2016 at 0837 LT
Type of aircraft:
Operator:
Registration:
N6781L
Survivors:
Yes
Schedule:
Kenmore – Roche Harbor
MSN:
788
YOM:
1955
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25000
Captain / Total hours on type:
1630.00
Aircraft flight hours:
7395
Circumstances:
While maneuvering at low altitude for a water landing, the commercial pilot of the float equipped airplane encountered low visibility due to ground fog. The pilot initiated a go-around, but the airplane impacted the water, bounced, and impacted the water a second time before coming to rest upright. The airplane subsequently sank, and all four occupants were later rescued. The pilot reported that there were no mechanical anomalies with the airplane that would have precluded normal operation. The operator further reported that other company pilots who were flying on the day of the accident stated that the low visibility conditions were easily avoided by a slight course deviation.
Probable cause:
The pilot's decision to land in an area of low visibility and ground fog, which resulted in collision with water.
Final Report:

Crash of a Beechcraft 1900D in Beni

Date & Time: Sep 28, 2016 at 1230 LT
Type of aircraft:
Operator:
Registration:
ZS-PZE
Survivors:
Yes
Schedule:
Goma - Beni
MSN:
UE-32
YOM:
1992
Flight number:
UNO830
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4728
Captain / Total hours on type:
921.00
Copilot / Total flying hours:
2258
Copilot / Total hours on type:
251
Aircraft flight hours:
21498
Aircraft flight cycles:
30564
Circumstances:
The twin engine aircraft departed Goma on a regular schedule flight (service UNO830) to Beni, carrying eight passengers and two pilots on behalf of the Monusco, the United Nations Organization Stabilization Mission in the Democratic Republic of Congo. On approach to Beni-Mavivi Airport, the crew completed the approach checklist and elected to configure the aircraft but realized that the undercarriage would not extend. After the circuit breaker was reset, the crew was able to lower the landing gear manually and continued the approach with no reporting to ATC. After touchdown on runway 11, the aircraft rolled for about 450 metres when the right main gear collapsed. Out of control the aircraft veered off runway to the right, slid in a grassy area, crossed a ditch and came to rest near the apron. All 10 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The following factors were identified:
- The ovality due to the wear of the junction point of the arm (270) with the actuator (15) over time to the point that it finally broke and released the actuator from the whole undercarriage system.
- Overheating of the time/delay relay caused the circuit breaker to trip.
- The ovality created by the job(65) at the junction of the arm(270) to the actuator(15) eventually thinned and broke off the actuator.
Final Report:

Crash of a Learjet 31A in Jakarta

Date & Time: Sep 25, 2016 at 1946 LT
Type of aircraft:
Operator:
Registration:
PK-JKI
Flight Type:
Survivors:
Yes
Schedule:
Yogyakarta – Jakarta
MSN:
31-213
YOM:
2001
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing an ambulance flight from Yogyakarta-Adisujipto Airport to Jakarta-Halim Perdanakusuma Airport on behalf of the Indonesian Red Cross (Palang Merah Indonesia), carrying one patient, two doctors, two accompanists and three crew members. The approach was completed by night and marginal weather conditions. After touchdown on runway 24, the aircraft skidded on a wet runway. After a course of 1,300 metres, it veered to the right and departed the runway surface. While contacting soft ground, the right main gear was torn off while the left main gear partially collapsed. Then the aircraft bounced and impacted the ground several times, causing the left wing to be bent. Eventually, the right engine partially detached from the pylon. All eight occupants were rescued and the aircraft was damaged beyond repair. There was no fire.

Crash of a BAe 4101 Jetstream 41 in Siddharthanagar

Date & Time: Sep 24, 2016 at 1656 LT
Type of aircraft:
Operator:
Registration:
9N-AIB
Survivors:
Yes
Schedule:
Kathmandu – Siddharthanagar
MSN:
41017
YOM:
1993
Flight number:
YT893
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
29
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach to Siddharthanagar-Gautam Buddha Airport was completed in good weather conditions with a wind from the southeast at 4 knots and a 8 km visibility. After touchdown on runway 28, the twin engine aircraft was unable to stop within the remaining distance. It overran, lost its undercarriage and came to rest in bushes, some 110 metres past the runway end. All 32 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a Beechcraft B100 King Air in Jackson

Date & Time: Sep 21, 2016 at 1620 LT
Type of aircraft:
Registration:
N66804
Flight Type:
Survivors:
Yes
Schedule:
Memphis – Jackson
MSN:
BE-82
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11295
Captain / Total hours on type:
570.00
Aircraft flight hours:
4013
Circumstances:
The commercial pilot reported that he had completed several uneventful flights in the multiengine airplane earlier on the day of the accident. He subsequently took off for a return flight to his home airport. He reported that the en route portion of the flight was uneventful, and on final approach for the traffic pattern for landing, all instruments were indicating normal. He stated that the airplane landed "firmly," that the right wing dropped, and that the right engine propeller blades contacted the runway. He pulled back on the yoke, and the airplane became airborne again momentarily before settling back on the runway. The right main landing gear (MLG) collapsed, and the airplane then veered off the right side of the runway and struck a runway sign and weather antenna. Witness reports corroborated the pilot's report. Postaccident examination revealed that the right MLG actuator was fractured and that the landing gear was inside the wheel well, which likely resulted from the hard landing. The pilot reported that there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. Based on the pilot and witness statements and the wreckage examination, it is likely that the pilot improperly flared the airplane, which resulted in the hard landing and the collapse of the MLG.
Probable cause:
The pilot's improper landing flare, which resulted in a hard landing.
Final Report:

Crash of a Boeing 737-347 in Wamena

Date & Time: Sep 13, 2016 at 0733 LT
Type of aircraft:
Operator:
Registration:
PK-YSY
Flight Type:
Survivors:
Yes
Schedule:
Jayapura – Wamena
MSN:
23597/1287
YOM:
1986
Flight number:
TGN7321
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
23823
Captain / Total hours on type:
9627.00
Copilot / Total flying hours:
650
Copilot / Total hours on type:
480
Aircraft flight hours:
59420
Aircraft flight cycles:
48637
Circumstances:
On 13 September 2016, a Boeing 737-300 Freighter, registered PK-YSY was being operated by PT. Trigana Air Service on a scheduled cargo flight from Sentani Airport, Jayapura (WAJJ) to Wamena Airport, Wamena (WAVV), Papua, Indonesia. Approximately 2130 UTC, during the flight preparation, the pilot received weather information which stated that on the right base runway 15 of Wamena Airport, on the area of Mount Pikei, low cloud was observed with the cloud base was increasing from 200 to 1000 feet and the visibility was 3 km. At 2145 UTC, the aircraft departed Sentani Airport with flight number IL 7321 and cruised at altitude 18,000 feet. On board the aircraft was two pilots and one Flight Operation Officer (FOO) acted as loadmaster. The aircraft carried 14,913 kg of cargo. The Pilot in Command (PIC) acted as Pilot Flying (PF) while the Second in Command (SIC) acted as Pilot Monitoring (PM). There was no reported or recorded aircraft system abnormality during the flight until the time of occurrence. After passing point MALIO, the aircraft started to descend. The pilot observed the weather met the criteria of Visual Meteorological Condition (VMC). The pilots able to identify another Trigana flight from Sentani to Wamena in front of them. While passing altitude 13,500 feet, approximately over PASS VALLEY, the Wamena Tower controller instructed the pilot to report position over JIWIKA. When the aircraft position was over point JIWIKA, the Wamena Tower controller informed to the pilot that the flight was on sequence number three for landing and instructed the pilot to make orbit over point X, which located at 8 Nm from runway 15. The pilot made two orbits over Point X to make adequate separation with the aircraft ahead prior to received approach clearance. About 7,000 feet (about 2,000 feet above airport elevation), the pilot could not identify visual checkpoint mount PIKEI and attempted to identify a church which was a check point of right base runway 15. The pilot felt that the aircraft position was on right side of runway centerline. About 6,200 feet (about 1,000 feet above airport elevation), the PF reduced the rate of descend and continued the approach. The PM informed to the PF that runway was not in sight and advised to go around. The PF was confident that the aircraft could be landed safely as the aircraft ahead had landed. Approximately 5,600 feet altitude (about 500 feet above airport elevation) and about 2 Nm from runway threshold the PF was able to see the runway and increased the rate of descend. The pilot noticed that the Enhanced Ground Proximity Warning System (EGPWS) aural warning “SINK RATE” active and the PF reduced the rate of descend. While the aircraft passing threshold, the pilot felt the aircraft sunk and touched down at approximately 125 meters from the beginning runway 15. The Flight Data Recorder recorded the vertical acceleration was 3.25 g on touchdown at 2230 UTC. Both of main landings gear collapsed. The left main landing gear detached and found on runway. The engine and lower fuselage contacted to the runway surface. The aircraft veer to the right and stopped approximately 1,890 meters from the beginning of the runway 15. No one was injured on this occurrence and the aircraft had substantially damage. Both pilots and the load master evacuated the aircraft via the forward left main cargo door used a rope.
Probable cause:
Refer to the previous aircraft that was landed safely, the pilot confidence that a safe landing could be made and disregarding several conditions required for go around.
Final Report:

Crash of a Beechcraft 200 Super King Air in Orlando

Date & Time: Sep 10, 2016 at 1530 LT
Registration:
N369CD
Flight Type:
Survivors:
Yes
Schedule:
Marathon – Orlando
MSN:
BB-110
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5000
Captain / Total hours on type:
50.00
Aircraft flight hours:
10321
Circumstances:
The pilot of a multi-engine turboprop airplane reported that during the landing flare he encountered a crosswind gust, which pushed the airplane to the right of the runway centerline. The pilot further reported that he applied power to abort the landing, but the airplane touched down in the grass to the right of the runway. After the wheels touched down in the grass, he reported that the power added "caught up with the aircraft," but the airplane was rolling toward trees and hangars. Subsequently, the pilot pulled the power to idle, but the right wing impacted a tree and the right main landing gear and nose wheel collapsed. A post-crash fire ensued after the collision and the right wing sustained substantial damage. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. There was no record of the observed weather at the airport during the accident. An automated weather observing system about 14 nautical miles from the accident airport, near the time of the accident, recorded the wind variable at 5 knots.
Probable cause:
The pilot's failure to maintain directional control during an attempted aborted landing in gusty crosswind conditions, which resulted in a runway excursion and an impact with a tree.
Final Report:

Crash of a Piper PA-31-325 Navajo C/R in Tuscaloosa: 6 killed

Date & Time: Aug 14, 2016 at 1115 LT
Type of aircraft:
Registration:
N447SA
Flight Type:
Survivors:
No
Schedule:
Kissimmee – Oxford
MSN:
31-8312016
YOM:
1983
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
749
Captain / Total hours on type:
48.00
Aircraft flight hours:
3447
Circumstances:
The private pilot and five passengers departed on a day instrument flight rules cross-country flight in the multiengine airplane. Before departure, the airplane was serviced to capacity with fuel, which corresponded to an endurance of about 5 hours. About 1 hour 45 minutes after reaching the flight's cruise altitude of 12,000 ft mean sea level, the pilot reported a failure of the right engine fuel pump and requested to divert to the nearest airport. About 7 minutes later, the pilot reported that he "lost both fuel pumps" and stated that the airplane had no engine power. The pilot continued toward the diversion airport and the airplane descended until it impacted trees about 1,650 ft short of the approach end of the runway; a postimpact fire ensued. Postaccident examination of the airframe and engines revealed no preimpact failures or malfunctions that would have precluded normal operation. The propellers of both engines were found in the unfeathered position. All six of the fuel pumps on the airplane were functionally tested or disassembled, and none exhibited any anomalies that would have precluded normal operation before the accident. Corrosion was noted in the right fuel boost pump, which was likely the result of water contamination during firefighting efforts by first responders. The airplane was equipped with 4 fuel tanks, comprising an outboard and an inboard fuel tank in each wing. The left and right engine fuel selector valves and corresponding fuel selector handles were found in the outboard tank positions. Given the airplane's fuel state upon departure and review of fuel consumption notes in the flight log from the day of the accident, the airplane's outboard tanks contained sufficient fuel for about 1 hour 45 minutes of flight, which corresponds to when the pilot first reported a fuel pump anomaly to air traffic control. The data downloaded from the engine data monitor was consistent with both engines losing fuel pressure due to fuel starvation. According to the pilot's operating handbook, after reaching cruise flight, fuel should be consumed from the outboard tanks before switching to the inboard tanks. Two fuel quantity gauges were located in the cockpit overhead switch panel to help identify when the pilot should return the fuel selectors from the outboard fuel tanks to the inboard fuel tanks. A flight instructor who previously flew with the pilot stated that this was their normal practice. He also stated that the pilot had not received any training in the accident airplane to include single engine operations and emergency procedures. It is likely that the pilot failed to return the fuel selectors from the outboard to the inboard tank positions once the outboard tanks were exhausted of fuel; however, the pilot misdiagnosed the situation as a fuel pump anomaly.
Probable cause:
A total loss of power in both engines due to fuel starvation as a result of the pilot's fuel mismanagement, and his subsequent failure to follow the emergency checklist. Contributing to the pilot's failure to follow the emergency checklist was his lack of emergency procedures training in the accident airplane.
Final Report:

Crash of a Boeing 737-476 in Bergamo

Date & Time: Aug 5, 2016 at 0407 LT
Type of aircraft:
Operator:
Registration:
HA-FAX
Flight Type:
Survivors:
Yes
Schedule:
Paris-Roissy-CDG - Bergamo
MSN:
24437/2162
YOM:
1991
Flight number:
QY7332
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9787
Captain / Total hours on type:
2254.00
Copilot / Total flying hours:
343
Copilot / Total hours on type:
86
Aircraft flight hours:
65332
Circumstances:
The aircraft departed Paris-Roissy-Charles de Gaulle Airport at 0254LT on a cargo flight (service QY7332) to Bergamo on behalf of DHL Airways. Upon arrival at Bergamo-Orio al Serio Airport, the crew encountered poor weather conditions with thunderstorm activity, heavy rain falls and strong wind. The aircraft crossed the runway threshold at a speed of 156 knots and landed 18 seconds later, 2,000 metres pas the runway threshold. Unable to stop within the remaining distance (runway 28 is 2,807 metres long), the aircraft overran, went through the perimeter fence, lost its undercarriage and both engines and eventually stopped in a motorway, some 520 metres pas the runway end. Both crew members evacuated safely and the aircraft was destroyed.
Probable cause:
The causes of the accident are mainly due to the human factor. In particular, the accident was caused by the runway overrun during the landing phase, caused by a loss of situational awareness relating to the position of the aircraft with respect to the runway itself. This loss of situational awareness on the part of the crew caused a delay in contact with the runway, which occurred, at a still high speed, in a position too far to allow the aircraft to stop within the remaining distance.
Contributing to the dynamics of the event:
- The commander's prior decision not to carry out a go-around procedure (this decision is of crucial importance in the chain of events that characterized the accident),
- Inadequate maintenance of flight parameters in the final phase of landing,
- Failure of the crew to disconnect the autothrottle prior to landing,
- Poor lighting conditions with the presence of storm cells and heavy rain falls at the time of the event (environmental factor), which may have contributed to the loss of situation awareness,
- The attention paid by the crew during the final phase of the flight, where both pilots were intent to acquire external visual references and did not realize that the aircraft crossed over the runway at high speed for 18 seconds before touchdown,
- The lack of assertiveness of the first officer in questioning the commander's decisions.
Finally, it cannot be excluded that a condition of tiredness and fatigue may have contributed to the accident, even if not perceived by the crew, which may have influenced the cognitive processes, in particular those of the captain, interfering with his correct decision making process.
Final Report:

Crash of a Boeing 777-31H in Dubai

Date & Time: Aug 3, 2016 at 1238 LT
Type of aircraft:
Operator:
Registration:
A6-EMW
Survivors:
Yes
Schedule:
Thiruvananthapuram - Dubai
MSN:
32700/434
YOM:
2003
Flight number:
EK521
Location:
Region:
Crew on board:
18
Crew fatalities:
Pax on board:
282
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7457
Captain / Total hours on type:
5123.00
Copilot / Total flying hours:
7957
Copilot / Total hours on type:
1292
Aircraft flight hours:
58169
Aircraft flight cycles:
13620
Circumstances:
On 3 August 2016, an Emirates Boeing 777-31H Aircraft, registration A6-EMW, operating a scheduled passenger flight UAE521, departed Trivandrum International Airport (VOTV), India, at 0506 UTC for a 3 hour 30 minute flight to Dubai International Airport (OMDB), the United Arab Emirates, with 282 passengers, 2 flight crew and 16 cabin crew members on board. The Commander attempted to perform a tailwind manual landing during an automatic terminal information service (ATIS) forecasted moderate windshear warning affecting all runways at OMDB. The tailwind was within the operational limitations of the Aircraft. During the landing on runway 12L at OMDB the Commander, who was the pilot flying, decided to fly a go-around, as he was unable to land the Aircraft within the runway touchdown zone. The go-around decision was based on the perception that the Aircraft would not land due to thermals and not due to a windshear encounter. For this reason, the Commander elected to fly a normal go-around and not the windshear escape maneuver. The flight crew initiated the flight crew operations manual (FCOM) Go-around and Missed Approach Procedure and the Commander pushed the TO/GA switch. As designed, because the Aircraft had touched down, the TO/GA switches became inhibited and had no effect on the autothrottle (A/T). The flight crew stated that they were not aware of the touchdown that lasted for six seconds. After becoming airborne during the go-around attempt, the Aircraft climbed to a height of 85 ft radio altitude above the runway surface. The flight crew did not observe that both thrust levers had remained at the idle position and that the engine thrust remained at idle. The Aircraft quickly sank towards the runway as the airspeed was insufficient to support the climb. As the Aircraft lost height and speed, the Commander initiated the windshear escape maneuver procedure and rapidly advanced both thrust levers. This action was too late to avoid the impact with runway 12L. Eighteen seconds after the initiation of the go-around the Aircraft impacted the runway at 0837:38 UTC and slid on its lower fuselage along the runway surface for approximately 32 seconds covering a distance of approximately 800 meters before coming to rest adjacent to taxiway Mike 13. The Aircraft remained intact during its movement along the runway protecting the occupants however, several fuselage mounted components and the No.2 engine/pylon assembly separated from the Aircraft. During the evacuation, several passenger door escape slides became unusable. Many passengers evacuated the Aircraft taking their carry-on baggage with them. Except for the Commander and the senior cabin crew member who evacuated after the center wing tank explosion, all of the other occupants evacuated via the operational escape slides in approximately 6 minutes and 40 seconds. Twenty-one passengers, one flight crewmember, and six cabin crew members sustained minor injuries. Four cabin crew members sustained serious injuries. Approximately 9 minutes and 40 seconds after the Aircraft came to rest, the center wing tank exploded which caused a large section of the right wing upper skin to be liberated. As the panel fell to the ground, it struck and fatally injured a firefighter. The Aircraft was eventually destroyed due to the subsequent fire. Following the Accident, the Operator (Emirates), the General Civil Aviation Authority (GCAA), Dubai Airports and Dubai Air Navigation Services (‘dans’) implemented several safety actions. In this Final Report, the AAIS issues safety recommendations addressed to the Operator, the GCAA, The Boeing Company, the Federal Aviation Administration (FAA), Dubai Airports, ‘dans’, and the International Civil Aviation Organization (ICAO).
Probable cause:
The Air Accident Investigation Sector determines that the causes of the Accident are:
(a) During the attempted go-around, except for the last three seconds prior to impact, both engine thrust levers, and therefore engine thrust, remained at idle. Consequently, the Aircraft’s energy state was insufficient to sustain flight.
(b) The flight crew did not effectively scan and monitor the primary flight instrumentation parameters during the landing and the attempted go-around.
(c) The flight crew were unaware that the autothrottle (A/T) had not responded to move the engine thrust levers to the TO/GA position after the Commander pushed the TO/GA switch at the initiation of the FCOM Go-around and Missed Approach Procedure.
(d) The flight crew did not take corrective action to increase engine thrust because they omitted the engine thrust verification steps of the FCOM Go-around and Missed Approach Procedure.
The Investigation determines that the following were contributory factors to the Accident:
(a) The flight crew were unable to land the Aircraft within the touchdown zone during the attempted tailwind landing because of an early flare initiation, and increased airspeed due to a shift in wind direction, which took place approximately 650 m beyond the runway threshold.
(b) When the Commander decided to fly a go-around, his perception was that the Aircraft was still airborne. In pushing the TO/GA switch, he expected that the autothrottle (A/T) would respond and automatically manage the engine thrust during the go-around.
(c) Based on the flight crew’s inaccurate situation awareness of the Aircraft state, and situational stress related to the increased workload involved in flying the go-around maneuver, they were unaware that the Aircraft’s main gear had touched down which caused the TO/GA switches to become inhibited. Additionally, the flight crew were unaware that the A/T mode had remained at ‘IDLE’ after the TO/GA switch was pushed.
(d) The flight crew reliance on automation and lack of training in flying go-arounds from close to the runway surface and with the TO/GA switches inhibited, significantly affected the flight crew performance in a critical flight situation which was different to that experienced by them during their simulated training flights.
(e) The flight crew did not monitor the flight mode annunciations (FMA) changes after the TO/GA switch was pushed because:
1. According to the Operator’s procedure, as per FCOM Flight Mode Annunciations (FMA), FMA changes are not required to be announced for landing when the aircraft is below 200 ft;
2. Callouts of FMA changes were not included in the Operator’s FCOM Go-Around and Missed Approach Procedures.
3. Callouts of FMA changes were not included in the Operator’s FCTM Go-Around and Missed Approach training.
(f) The Operator’s OM-A policy required the use of the A/T for engine thrust management for all phases of flight. This policy did not consider pilot actions that would be necessary during a go-around initiated while the A/T was armed and active and the TO/GA switches were inhibited.
(g) The FCOM Go-Around and Missed Approach Procedure did not contain steps for verbal verification callouts of engine thrust state.
(h) The Aircraft systems, as designed, did not alert the flight crew that the TO/GA switches were inhibited at the time when the Commander pushed the TO/GA switch with the A/T armed and active.
(i) The Aircraft systems, as designed, did not alert the flight crew to the inconsistency between the Aircraft configuration and the thrust setting necessary to perform a successful go-around.
(j) Air traffic control did not pass essential information about windshear reported by a preceding landing flight crew and that two flights performed go-arounds after passing over the runway threshold. The flight crew decision-making process, during the approach and landing, was deprived of this critical information.
(k) The modification of the go-around procedure by air traffic control four seconds after the Aircraft became airborne coincided with the landing gear selection to the ‘up’ position. This added to the flight crew workload as they attentively listened and the Copilot responded to the air traffic control instruction which required a change of missed approach altitude from 3,000 ft to 4,000 ft to be set. The flight crews’ concentration on their primary task of flying the Aircraft and monitoring was momentarily affected as both the FMA verification and the flight director status were missed.
Final Report: