Crash of a Socata TBM-850 in Breckenridge

Date & Time: Oct 14, 2019 at 1245 LT
Type of aircraft:
Operator:
Registration:
N850NK
Flight Type:
Survivors:
Yes
Schedule:
San Angelo - Breckenridge
MSN:
432
YOM:
2007
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8195
Captain / Total hours on type:
6.00
Aircraft flight hours:
2878
Circumstances:
The pilot reported that, during the approach and while the airplane was about 500 ft above ground level and 81 knots, he "felt the descent rate increase significantly." The pilot increased engine power, but "the high rate of descent continued," and he then increased the engine power further. A slow left roll developed, and he applied full right aileron and full right rudder to arrest the left roll. He also reduced the engine power, and the left roll stopped. The pilot regained control of the airplane, but the airplane's heading was 45° left of the runway heading, and the airplane impacted trees and then terrain. The airplane caught fire, and the pilot and passenger exited through the emergency exit. The airplane sustained substantial damage to the windscreens and fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause:
The pilot's failure to maintain bank control and adequate altitude during the approach, which resulted in his failure to maintain the runway heading and a subsequent collision with trees and terrain.
Final Report:

Crash of a Piper PA-60-602P in Kokomo: 1 killed

Date & Time: Oct 5, 2019 at 1637 LT
Operator:
Registration:
N326CW
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kokomo - Kokomo
MSN:
60-0869-8165008
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
7500
Aircraft flight hours:
3002
Circumstances:
The airline transport pilot arrived at the departure airport in the reciprocating engine-powered airplane where it was fueled with Jet A jet fuel by an airport employee/line service technician. A witness stated that she saw a "low flying" airplane flying from north to south. The airplane made a "sharp left turn" to the east. The left wing "dipped low" and she then lost sight of the airplane, but when she approached the intersection near the accident site, she saw the airplane on the ground. The airplane impacted a field that had dry, level, and hard features conducive for an off-airport landing, and the airplane was destroyed. The wreckage path length and impact damage to the airplane were consistent with an accelerated stall. Postaccident examination of the airplane found Jet A jet fuel in the airplane fuel system and evidence of detonation in both engines from the use of Jet A and not the required 100 low lead fuel. Use of Jet A rather than 100 low lead fuel in an engine would result in detonation in the cylinders and lead to damage and a catastrophic engine failure. According to the Airplane Flying Handbook, the pilot should witness refueling to ensure that the correct fuel and quantity is dispensed into the airplane and that any caps and cowls are properly secured after refueling.
Probable cause:
The pilot's exceedance of the airplane’s critical angle of attack following a dual engine power loss caused by the line service technician fueling the airplane with the wrong fuel, which resulted in an aerodynamic stall and subsequent loss of control. Contributing was the pilot's inadequate supervision of the fuel servicing.
Final Report:

Crash of a Socata TBM-700 in Lansing: 5 killed

Date & Time: Oct 3, 2019 at 0858 LT
Type of aircraft:
Operator:
Registration:
N700AQ
Flight Type:
Survivors:
Yes
Schedule:
Indianapolis - Lansing
MSN:
252
YOM:
2003
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
1404
Captain / Total hours on type:
76.00
Aircraft flight hours:
3550
Circumstances:
The pilot was conducting an instrument approach at the conclusion of a cross-country flight when the airplane entered a shallow climb and left turn away from the runway heading about 0.5-mile from the intended runway. According to airspeeds calculated from automatic dependent surveillance-broadcast position data, the airplane’s calibrated airspeed was 166 knots when it crossed over the final approach fix inbound toward the runway and was about 84 knots when it was on a 0.5-mile final approach. The airplane continued to decelerate to 74 knots while it was in a shallow climb and left turn away from the runway heading. At no point during the approach did the pilot maintain the airframe manufacturer’s specified approach speed of 85 knots. The airplane impacted the ground in an open grass field located to the left of the extended runway centerline. The airplane was substantially damaged when it impacted terrain in a wings level attitude. The postaccident examination did not reveal any anomalies that would have precluded normal operation of the airplane. The altitude and airspeed trends during the final moments of the flight were consistent with the airplane entering an aerodynamic stall at a low altitude. Based on the configuration of the airplane at the accident site, the pilot likely was retracting the landing gear and flaps for a go around when the airplane entered the aerodynamic stall. The airplane was operating above the maximum landing weight, and past the aft center-of-gravity limit at the time of the accident which can render the airplane unstable and difficult to recover from an aerodynamic stall. Additionally, without a timely corrective rudder input, the airplane tends to roll left after a rapid application of thrust at airspeeds less than 70 knots, including during aerodynamic stalls. Although an increase in thrust is required for a go around, the investigation was unable to determine how rapidly the pilot increased thrust, or if a torque-roll occurred during the aerodynamic stall.
Probable cause:
The pilot’s failure to maintain airspeed during final approach, which resulted in a loss of control and an aerodynamic stall at a low altitude, and his decision to operate the airplane outside of the approved weight and balance envelope.
Final Report:

Crash of a Boeing B-17G-30-BO Flying Fortress in Windsor Locks: 7 killed

Date & Time: Oct 2, 2019 at 0953 LT
Operator:
Registration:
N93012
Flight Type:
Survivors:
Yes
Schedule:
Windsor Locks - Windsor Locks
MSN:
7023
YOM:
1942
Crew on board:
3
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
14500
Captain / Total hours on type:
7300.00
Copilot / Total flying hours:
22000
Copilot / Total hours on type:
23
Aircraft flight hours:
11388
Circumstances:
The vintage, former US military bomber airplane was on a tour that allowed members of the public to purchase an excursion aboard the airplane for an LHFE flight. The accident flight was the airplane’s first flight of the day. During the initial climb, one of the pilots retracted the landing gear, and the crew chief/flight engineer (referred to as the loadmaster) left the cockpit to inform the passengers that they could leave their seats and walk around the airplane. One of the pilots reported to air traffic control that the airplane needed to return to the airport because of a rough magneto. At that time, the airplane was at an altitude of about 600 ft above ground level (agl) on the right crosswind leg of the airport traffic pattern for runway 6. The approach controller asked the pilot if he needed any assistance, to which the pilot replied, “negative.” When the loadmaster returned to the cockpit, he realized that the airplane was no longer climbing, and the pilot, realizing the same, instructed the copilot to extend the landing gear, which he did. The loadmaster left the cockpit to instruct the passengers to return to their seats and fasten their seat belts. When the loadmaster returned again to the cockpit, the pilot stated that the No. 4 engine was losing power; the pilot then shut down that engine and feathered the propeller without any further coordination or discussion. When the airplane was at an altitude of about 400 ft agl, it was on a midfield right downwind leg for runway 6. Witness video showed that the landing gear had already been extended by that time, even though the airplane still had about 2.7 nautical miles to fly in the traffic pattern before reaching the runway 6 threshold. During final approach, the airplane struck the runway 6 approach lights in a right-wing-down attitude about 1,000 ft before the runway and then contacted the ground about 500 ft before the runway. After landing short of the runway, the airplane traveled onto the right edge of the runway threshold and continued to veer to the right. The airplane collided with vehicles and a deicing fluid tank before coming to rest upright about 940 ft to the right of the runway. A postcrash fire ensued. Both pilots and five passengers were killed and all six other occupants as well as one people on the ground were injured, five seriously.
Probable cause:
The pilot’s failure to properly manage the airplane’s configuration and airspeed after he shut down the No. 4 engine following its partial loss of power during the initial climb. Contributing to the accident was the pilot/maintenance director’s inadequate maintenance while the airplane was on tour, which resulted in the partial loss of power to the Nos. 3 and 4 engines; the Collings Foundation’s ineffective safety management system (SMS), which failed to identify and mitigate safety risks; and the Federal Aviation Administration’s inadequate oversight of the Collings Foundation’s SMS.
Final Report:

Crash of a Cessna 421A Golden Eagle I in DeLand: 3 killed

Date & Time: Sep 29, 2019 at 1600 LT
Type of aircraft:
Operator:
Registration:
N731PF
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
DeLand - DeLand
MSN:
421A-0164
YOM:
1968
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
500
Captain / Total hours on type:
0.00
Aircraft flight hours:
858
Circumstances:
The owner of the airplane had purchased the airplane with the intent to resell it after repairs had been made. As part of that process, a mechanic hired by the owner had assessed the airplane’s condition, proposed the necessary repairs to the airplane’s owner, and had identified a pilot who would, once the repairs and required inspection annual inspection had been completed, fly the airplane from where it was located to where the owner resided. While the mechanic had identified a potential pilot for the relocation flight, he had not yet completed the repairs to the airplane, nor had he completed the necessary logbook entries that would have returned the airplane to service. The pilot-rated passenger onboard the airplane for the accident flight, was the pilot who had been identified by the mechanic for the relocation flight. Review of the pilot-rated passenger’s flight experience revealed that he did not possess the necessary pilot certificate rating, nor did he have the flight experience necessary to act as pilot-in-command of the complex, highperformance, pressurized, multi-engine airplane. Additionally, the owner of the airplane had not given the pilot-rated-passenger, or anyone else, permission to fly the airplane. The reason for, and the circumstances under which the pilot-rated passenger and the commercial pilot (who did hold a multi-engine rating) were flying the airplane on the accident flight could not be definitively determined, although because another passenger was onboard the airplane, it is most likely that the accident flight was personal in nature. Given the commercial pilot’s previous flight experience, it is also likely that he was acting as pilot-in-command for the flight. One witness said that he heard the airplane’s engines backfiring as it flew overhead, while another witness located about 1 mile from the accident site heard the accident airplane flying overhead. The second witness said that both engines were running, but they seemed to be running at idle and that the flaps and landing gear were retracted. The witness saw the airplane roll to the left three times before descending below the tree line. As the airplane descended toward the ground, the witness heard the engines make “two pop” sounds. The airplane impacted a wooded area about 4 miles from the departure airport, and the wreckage path through the trees was only about 75-feet long. While the witnesses described the airplane’s engines backfiring or popping before the accident, the postaccident examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Additionally, examination of both propeller blades showed evidence of low rotational energy at impact, and that neither propeller had been feathered in flight. Given the witness statement describing the airplane “rolling three times” before it descended from view toward the ground, it is most likely that the pilot lost control of the airplane and while maneuvering. It is also likely that the pilot’s lack of any documented previous training or flight experience in the accident airplane make and model contributed to his inability to maintain control of the airplane. Toxicology testing was performed on the pilot’s chest cavity blood. The results identified 6.7 ng/ml of delta-9-tetrahydracannabinol (THC, the active compound in marijuana) as well as 2.6 ng/ml of its active metabolite, 11-hydroxy-THC and 41.3 ng/ml of its inactive metabolite delta9-carboxy-THC. Because the measured THC levels were from cavity blood, it was not possible to determine when the pilot last used marijuana or whether he was impaired by it at the time of the flight. As a result, it could not be determined whether effects from the pilot’s use of marijuana contributed to the accident circumstances.
Probable cause:
The pilot’s failure to maintain control of the airplane, which resulted in a collision with terrain. Contributing was the pilot’s lack of training and experience in the accident airplane make and model.
Final Report:

Crash of a Piper PA-46-350P Malibu Mirage off Boothville

Date & Time: Sep 15, 2019 at 1146 LT
Operator:
Registration:
N218MW
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Titusville – Ozona – Santee
MSN:
46-36470
YOM:
2010
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3500
Captain / Total hours on type:
2000.00
Aircraft flight hours:
1116
Circumstances:
On September 15, 2019, at 1146 central daylight time, a Piper PA-46-350P, N218MW, lost engine power while maneuvering over the Gulf of Mexico, and the pilot was forced to ditch. The private pilot was not injured. The airplane was registered to and operated by Mailworks, Inc., Spring Valley, California, under Title 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions existed near the accident site at the time of the accident, and the flight was operated on a visual flight rules flight plan. The flight originated at 0830 eastern daylight time from Space Coast Regional Airport (TIX), Titusville, Florida, and was en route to Ozona Municipal Airport (OZA), Ozona, Texas. His final destination was Gillespie Field Airport (SEE), El Cajon, California. According to the pilot's accident report, he departed TIX with 140 gallons of fuel. After crossing Gulfport (GPT), Mississippi's Terminal Radar Service Area (TRSA) at 10,500 ft, he initiated a slow descent over Boothville, Louisiana, and proceeded southbound towards the mouth of the Mississippi River, descending to 1,500 ft. He then configured the airplane for climb. The engine did not respond to the application of power and the airplane began losing altitude. After going through the emergency checklist, he was unable to restore engine power, and declared an emergency to Houston air route traffic control center (ARTCC) and on frequency 121.5 mHz. He also activated the emergency locator transmitter (ELT) prior to ditching. After ditching, the pilot put on his life jacket, exited the airplane, and remained on its wing until it sank. About an hour later, a U.S. Coast Guard helicopter rescued the pilot and transported him to a hospital in New Orleans, Louisiana. He was discharged a few hours later. The airplane has not been recovered.
Probable cause:
A loss of engine power for undetermined reasons.
Final Report:

Crash of a Cessna 510 Citation Mustang in El Monte

Date & Time: Aug 31, 2019 at 1105 LT
Operator:
Registration:
N551WH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
El Monte - Thermal
MSN:
510-0055
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2217
Captain / Total hours on type:
477.00
Circumstances:
The pilot reported that, while holding short of the runway, he set the parking brake while waiting for his takeoff clearance. Upon receiving takeoff clearance, he reached down to the parking brake handle and, "quickly pushed the parking brakes back in"; however, he did not visually verify that he disengaged the parking brake. During the takeoff roll, he noticed that the airplane was not accelerating beyond about 70 knots and decided to abort the takeoff. The airplane subsequently veered to the left, exited the departure end of the runway, and impacted an airport perimeter fence. The pilot reported that he must have not fully disengaged the parking brake before takeoff and that there were no mechanical issues with the airplane that would have precluded normal operation. Postaccident examination of the airplane revealed that the parking brake handle was partially extended, which likely resulted in the airplane’s decreased acceleration during the takeoff roll.
Probable cause:
The pilot's failure to disengage the parking brake before takeoff, which resulted in decreased acceleration and a subsequent runway overrun following an aborted takeoff.
Final Report:

Crash of a PZL-Mielec AN-2R near Lake Siljan-Kuel: 2 killed

Date & Time: Aug 30, 2019 at 0730 LT
Type of aircraft:
Operator:
Registration:
RA-33061
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Us-Khatyn – Suordakh
MSN:
1G218-48
YOM:
1986
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
12500
Captain / Total hours on type:
3806.00
Aircraft flight hours:
3848
Circumstances:
The single engine airplane departed Us-Khatyn on a flight to Suordakh, carrying five passengers, two pilots and a load consisting of 600 kilos of various goods. While cruising at an altitude of about 1,450 metres, the crew encountered moderate atmospheric turbulences and was unable to maintain the altitude. The aircraft lost height and crashed on the rocky slope of amountain located 15 km southeast from the Lake Siljan-Kuel, some 250 km from the destination. Two passengers were killed while five others occupants were injured. The aircraft was destroyed.
Probable cause:
The accident was caused by the fact that the PIC did not maintain a safe flight altitude in mountainous terrain, which led to the aircraft getting into strong downdrafts while flying over the leeward side of the ridge, uncontrolled descent and collision with the top of the mountain.
The contributing factors of AP, most likely, were:
- insufficient analysis of meteorological conditions and the possibility of the formation of strong ascending and descending air currents in the mountains;
- Failure of the PIC to take safety measures when flying in the mountains and to act in case of falling into downward air currents when crossing a mountain ridge;
- the use of motor gasoline with an octane rating of less than 95, which led to a decrease in engine power;
- performing a mission on the An-2 aircraft without the procedure for restoring skills and admission to flights on this type after a significant break in flights (about 15 years).
Final Report:

Crash of a Cessna T303 Crusader in Lagrangeville: 2 killed

Date & Time: Aug 17, 2019 at 1613 LT
Type of aircraft:
Registration:
N303TL
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Sky Acres - Farmingdale
MSN:
303-00286
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1586
Captain / Total hours on type:
358.00
Aircraft flight hours:
2932
Circumstances:
After flying one flight leg earlier in the day, the pilot flew to an intermediate stop on the way to his home base to purchase fuel. A surveillance video recording from the fueling airport showed the airplane land and taxi to the self-serve fuel pump where the engines were shut down for about 10 minutes while the airplane was fueled. The pilot then had difficulty starting both engines over several minutes. After the engines were running, the airplane taxied to the runway and did not appear to stop for an engine run-up. The pilot performed a rolling takeoff, and the airplane lifted off after a roll of about 2,100 ft, slightly more than half the available runway length. A passenger reported that after liftoff, at an altitude of about 50 to 100 ft above ground level (agl), both engines lost partial power and began “stuttering,” which continued for the remainder of the flight. He further reported that the engines did not stop, but they were “not producing full RPM.” The airplane drifted left of centerline, which a witness described as a left yawing motion. The pilot corrected the drift and flew the runway heading over the grass on the left side of the runway; however, the airplane would not climb. After crossing the end of the runway, the pilot pitched the airplane up to avoid obstacles. Automatic dependent surveillance-broadcast data indicated that the airplane climbed from about 20 to 120 ft agl in a gradual left turn. During this time the groundspeed decreased from about 80 knots to about 69 knots. The altitude then decreased to about 50 ft agl, the groundspeed decreased to about 66 knots, and the left turn decreased in radius until the recorded data ended about 100 ft west of the accident site. The airplane descended and
impacted a house. Witness descriptions of the airplane yawing to the left while over the runway and again during its final left turn suggest that the loss of engine power may not have been symmetric (that is, one engine may have suffered more of a loss than the other).
Probable cause:
A partial loss of engine power in both engines during initial climb for reasons that could not be determined based on the available information.
Final Report:

Crash of a Cessna 680A Citation Latitude in Elizabethton

Date & Time: Aug 15, 2019 at 1537 LT
Operator:
Registration:
N8JR
Flight Type:
Survivors:
Yes
Schedule:
Statesville - Elizabethton
MSN:
680A-0010
YOM:
2015
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5800
Captain / Total hours on type:
765.00
Copilot / Total flying hours:
11000
Copilot / Total hours on type:
1165
Aircraft flight hours:
1165
Circumstances:
The pilots were conducting a visual flight rules cross-country flight with three passengers onboard. The preflight, departure, and cruise portions of the flight were uneventful. During the initial approach to the airport, the flight crew discussed having some difficulty visually acquiring the airport. They also discussed traffic in the area and were maneuvering around clouds, which may have increased the pilots' workload. As the approach continued, the airplane crossed a ridgeline at 710 ft above ground level (agl), which triggered a terrain awareness and warning system (TAWS) alert. Further, the flight crew made several comments about the airplane flying too fast and allowed the airspeed to increase well above the reference speed (Vref) for the approach. At 1535:57 (about 1 minute 52 seconds before landing), the pilot pulled back the throttles to idle, where they stayed for the remainder of the approach. In an attempt to slow the airplane for landing, the pilot partially extended the speedbrakes when the airplane was below 500 ft agl, which is prohibited in the airplane flight manual (AFM). Five seconds before touchdown, the airplane's descent rate was 1,500 ft per minute (fpm), which exceeded the maximum allowed for landing per the AFM of 600 fpm. When the airplane first touched down, it was traveling about 18 knots above Vref. The pilot did not extend the speedbrakes upon touchdown, which the landing checklist required, but instead attempted to deploy the thrust reversers immediately after touchdown, which was a later item on the landing checklist. However, the thrust reversers did not unlock because the airplane bounced and was airborne again before the command could be executed, which was consistent with system design and logic: the thrust reversers will not unlock until all three landing gear are on the ground. The airplane touched down four times total; on the third touchdown (after the second bounce), when all three landing gear contacted the runway, the thrust reversers unlocked as previously commanded during the first touchdown. Although the pilot subsequently advanced the throttles to idle, which would normally stow the thrust reversers, the airplane had bounced a third time and had already become airborne again before the thrust reversers could stow. When the airplane became airborne, the system logic cut hydraulic power to the thrust reverser actuators; thus the reversers would not stow. The thrust reversers were subsequently pulled open due to the aerodynamic forces. The pilot attempted to go around by advancing the throttles when the airplane was airborne. However, the electronic engine controls prevented the increase in engine power because the thrust reversers were not stowed. When the airplane touched down the fourth and final time, the pilot attempted to land straight ahead on the runway; the airplane touched down hard and the right main landing gear then collapsed under the wing. The airplane departed the paved surface and came to rest about 600 ft beyond the runway threshold. The passengers and crew eventually evacuated the airplane through the main cabin door, and the airplane was destroyed in a postaccident fire. A postaccident examination of the airplane systems, structure, powerplants, and landing gear revealed no evidence of mechanical malfunctions or anomalies that would have precluded normal operation. The airplane's approach was unstabilized: its airspeed during the approach and landing well exceeded Vref and its descent rate exceeded the maximum allowed for landing just seconds before touchdown. Both the pilot and copilot commented on the airplane's high speed several times during the approach. During short final, the pilot asked the copilot if he should go around, and the copilot responded, "no." Although the copilot was the director of operations for the flight department and the direct supervisor of the pilot, the pilot stated that the copilot's position did not influence his decisions as pilot-in-command nor did it diminish his command authority. Neither the pilot nor copilot called for a go-around before landing despite awareness that the approach was unstabilized. As the airplane touched down, the pilot failed to follow the AFM guidance and used the thrust reversers before the speedbrakes. According to the airplane manufacturer's calculations, the airplane could have stopped within the length of runway available if the airplane had not bounced and the speedbrakes and wheel brakes were used at the point of the first touchdown. After the third touchdown, when the airplane became airborne again, the pilot attempted a go-around; the AFM prohibits touch-and-go landings after the thrust reversers are deployed. It is critical for pilots to know the point at which they should not attempt a go-around; a committed-to-stop (CTS) point is the point at which a go-around or rejected landing procedure will not be initiated and the only option will be bringing the aircraft to a stop. Establishing a CTS point eliminates the ambiguity for pilots making decisions during time-critical events. The FAA issued Information for Operators 17009, "Committed-toStop Point on Landings," to inform operators and pilots about the importance of establishing a CTS point; however, the director of operations was not aware of the concept of a CTS point during landing.
Probable cause:
The pilot's continuation of an unstabilized approach despite recognizing associated cues and the flight crew's decision not to initiate a go-around before touchdown, which resulted in a bounced landing, a loss of airplane control, a landing gear collapse, and a runway excursion. Contributing to the accident was the pilot's failure to deploy the speedbrakes during the initial touchdown, which may have prevented the runway excursion, and the pilot's attempt to go around after deployment of the thrust reversers.
Final Report: