Crash of a Boeing 737-81Q at Jacksonville NAS

Date & Time: May 3, 2019 at 2142 LT
Type of aircraft:
Operator:
Registration:
N732MA
Survivors:
Yes
Schedule:
Guantánamo Bay - Jacksonville
MSN:
30618/830
YOM:
2001
Flight number:
LL293
Crew on board:
7
Crew fatalities:
Pax on board:
136
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7500
Captain / Total hours on type:
2204.00
Copilot / Total flying hours:
7500
Copilot / Total hours on type:
18
Aircraft flight hours:
38928
Aircraft flight cycles:
15610
Circumstances:
According to both pilots, the takeoff, climb, and cruise portions of the flight were uneventful. The No. 1 (left) thrust reverser was not operational and deferred for the flight in accordance with the airplane’s minimum equipment list. The captain was the pilot flying for the accident flight, and the first officer was the pilot monitoring. The captain was also performing check airman duties for the first officer who was in the process of completing operating experience training. During the approach to Jacksonville Naval Air Station (NIP), the flight crew had two runway change discussions with air traffic controllers due to reported weather conditions (moderate to heavy precipitation) near the field; the pilots ultimately executed the area navigation GPS approach to runway 10, which was ungrooved and had a displaced threshold 997 ft from the threshold, leaving an available landing distance of 8,006 ft. As the airplane descended through 1,390 ft mean sea level (msl), the pilots configured it for landing with the flaps set at 30º and the landing gear extended; however, the speedbrake handle was not placed in the armed position as specified in the Landing checklist. At an altitude of about 1,100 ft msl and 2.8 nm from the runway, the airplane was slightly above the glidepath, and its airspeed was on target. Over the next minute, the indicated airspeed increased to 170 knots (17 knots above the target approach speed), and groundspeed reached 180 knots, including an estimated 7-knot tailwind. At an altitude of about 680 ft msl and 1.6 nm from the threshold, the airplane deviated further above the 3° glidepath such that the precision approach path indicator (PAPI) lights would have appeared to the flight crew as four white lights and would retain that appearance throughout the rest of the approach. Eight seconds before touchdown, multiple enhanced ground proximity warning system alerts announced “sink rate” as the airplane’s descent rate peaked at 1,580 fpm. The airplane crossed the displaced threshold 120 ft above the runway (the PAPI glidepath crosses the displaced threshold about 54 ft above the runway) and 17 knots above the target approach speed, with a groundspeed of 180 knots and a rate of descent about 1,450 ft per minute (fpm). The airplane touched down about 1,580 ft beyond the displaced threshold, which was 80 ft beyond the designated touchdown zone as specified in the operator’s standard operating procedures (SOP). After touchdown, the captain deployed the No. 2 engine thrust reverser and began braking; he later reported, however, that he did not feel the aircraft decelerate and increased the brake pressure. The speedbrakes deployed about 4 seconds after touchdown, most likely triggered by the movement of the right throttle into the idle reverse thrust detent after main gear tire spinup. The automatic deployment of the speedbrakes was likely delayed by about 3 seconds compared to the automatic deployment that could have been obtained by arming the speedbrakes before landing. The airplane crossed the end of the runway about 55 ft right of the centerline and impacted a seawall 90 ft to the right of the centerline, 9,170 ft beyond the displaced threshold, and 1,164 ft beyond the departure end of runway 10. After the airplane came to rest in St. Johns River, the flight crew began an emergency evacuation.
Probable cause:
An extreme loss of braking friction due to heavy rain and the water depth on the ungrooved runway, which resulted in viscous hydroplaning. Contributing to the accident was the operator’s inadequate guidance for evaluating runway braking conditions and conducting en route landing distance assessments.
Contributing to the continuation of an unstabilized approach were
1) the captain’s plan continuation bias and increased workload due to the weather and performing check airman duties and
2) the first officer’s lack of experience.
Final Report:

Crash of a Piper PA-46-350P Malibu near Makkovik: 1 killed

Date & Time: May 1, 2019 at 0816 LT
Operator:
Registration:
N757NY
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Goose Bay - Narsarsuaq
MSN:
46-36657
YOM:
2015
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3500
Captain / Total hours on type:
20.00
Copilot / Total flying hours:
1300
Copilot / Total hours on type:
0
Circumstances:
On 01 May 2019 at 0723, the aircraft departed CYYR on a VFR flight plan direct to BGBW. The ferry pilot, who was the pilot-in-command, occupied the left seat while the co-owner occupied the right seat. The aircraft climbed to 2000 feet ASL and proceeded on a direct track to destination. The altitude and heading did not change significantly along the route, therefore it is likely that the autopilot was engaged. At 0816, the aircraft collided with a snow-covered hill 2250 feet in elevation, located 35 nautical miles (NM) southeast of Makkovik Airport (CYFT), Newfoundland and Labrador. The impact happened approximately 200 feet below the top of the hill. The aircraft came to rest in deep snow on steep sloping terrain. The aircraft sustained significant damage to the propeller, nose gear, both wings, and fuselage. Although the cabin was crush-damaged, occupiable space remained. There was no post-impact fire. The ferry pilot was seriously injured and the co-owner was fatally injured. The Joint Rescue Coordination Centre (JRCC) in Halifax received an emergency locator transmitter (ELT) signal from the aircraft at 0823. The ferry pilot carried a personal satellite tracking device, a personal locator beacon (PLB) and a handheld very high frequency (VHF) radio, which allowed communication with search and rescue (SAR). Air SAR were dispatched to the area; however, by that time, the weather had deteriorated to blizzard conditions and aerial rescue was not possible. Ground SAR then deployed from the coastal community of Makkovik and arrived at the accident site approximately 4 hours later because of poor weather conditions and near zero visibility. The ferry pilot and the body of the co-owner were transported to Makkovik by snowmobile. The following day, they were airlifted to CYYR.
Probable cause:
Controlled flight into terrain.
Final Report:

Crash of a Beechcraft B200 Super King Air in Gillam

Date & Time: Apr 24, 2019 at 1823 LT
Operator:
Registration:
C-FRMV
Flight Type:
Survivors:
Yes
Schedule:
Winnipeg – Churchill – Rankin Inlet
MSN:
BB-979
YOM:
1982
Flight number:
KEW202
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1350
Captain / Total hours on type:
1100.00
Copilot / Total flying hours:
3500
Copilot / Total hours on type:
1350
Circumstances:
On 24 April 2019, the Keewatin Air LP Beechcraft B200 aircraft (registration C‑FRMV, serial number BB979), equipped to perform medical evacuation flights, was conducting an instrument flight rules positioning flight (flight KEW202), with 2 flight crew members and 2 flight nurses on board, from Winnipeg/James Armstrong Richardson International Airport, Manitoba, to Rankin Inlet Airport, Nunavut, with a stop at Churchill Airport, Manitoba. At 1814 Central Daylight Time, when the aircraft was cruising at flight level 250, the flight crew declared an emergency due to a fuel issue. The flight crew diverted to Gillam Airport, Manitoba, and initiated an emergency descent. During the descent, both engines flamed out. The flight crew attempted a forced landing on Runway 23, but the aircraft touched down on the frozen surface of Stephens Lake, 750 feet before the threshold of Runway 23. The landing gear was fully extended. The aircraft struck the rocky lake shore and travelled up the bank toward the runway area. It came to rest 190 feet before the threshold of Runway 23 at 1823:45 Central Daylight Time. None of the occupants was injured. The aircraft sustained substantial damage. The 406 MHz emergency locator transmitter activated. Emergency services responded. There was no fire.
Probable cause:
Findings as to causes and contributing factors:
These are conditions, acts or safety deficiencies that were found to have caused or contributed to this occurrence.
1. When the captain asked if the aircraft was ready for the flight, the first officer replied that it was, not recalling that the aircraft required fuel.
2. While performing the FUEL QUANTITY item on the AFTER START checklist, the captain responded to the first officer’s prompt with the rote response that the fuel was sufficient, without looking at the fuel gauges.
3. The aircraft departed Winnipeg/James Armstrong Richardson International Airport with insufficient fuel on board to complete the planned flight.
4. The flight crew did not detect that there was insufficient fuel because the gauges had not been included in the periodic cockpit scans.
5. When the flight crew performed the progressive fuel calculation, they did not confirm the results against the fuel gauges, and therefore their attention was not drawn to the low-fuel state at a point that would have allowed for a safe landing.
6. Still feeling the effect of the startle response to the fuel emergency, the captain quickly became task saturated, which led to an uncoordinated response by the flight crew, delaying the turn toward Gillam Airport, and extending the approach.
7. The right engine lost power due to fuel exhaustion when the aircraft was 1 nautical mile from Runway 23. From that position, a successful forced landing on the intended runway was no longer possible and, as a result, the aircraft touched down on the ice surface of Stephens Lake, short of the runway.

Findings as to risk:
These are conditions, unsafe acts or safety deficiencies that were found not to be a factor in this occurrence but could have adverse consequences in future occurrences.
1. If procedures are not developed to instruct pilots on their roles and responsibilities during line indoctrination flights, there is a risk that flight crew members may not participate when expected, or may work independently towards different goals.

Other findings:
These items could enhance safety, resolve an issue of controversy, or provide a data point for future safety studies.
1. Because emergency medical services and the fire department were not notified immediately about the declared emergency, they were not on site before the aircraft arrived at Gillam Airport.
Final Report:

Crash of a Cessna 208 Caravan I in the Dry Tortugas National Park

Date & Time: Apr 23, 2019 at 1200 LT
Type of aircraft:
Operator:
Registration:
N366TA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Dry Tortugas - Key West
MSN:
208-0249
YOM:
1996
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2407
Captain / Total hours on type:
27.00
Aircraft flight hours:
9506
Circumstances:
The pilot landed the seaplane into an easterly wind, then noticed that the surface wind was greater than forecast. Unable to taxi to the beaching location, he elected to return to his destination. He maneuvered the airplane into the wind and applied takeoff power. He described the takeoff run as "bumpy" and the water conditions as "rough." The pilot reported that the left float departed the airplane at rotation speed, and the airplane subsequently nosed into the water. The pilot and passengers were assisted by a nearby vessel and the airplane subsequently sank into 50 ft of water. Inclement sea and wind conditions prevented recovery of the wreckage for 52 days, and the wreckage was stored outside for an additional 13 days before recovery by the salvage company. Extensive saltwater corrosion prevented metallurgical examination of the landing gear components; however, no indication of a preexisting mechanical malfunction or failure was found.
Probable cause:
The pilot's decision to attempt a takeoff in rough sea conditions, resulting in damage to the floats and the sinking of the seaplane.
Final Report:

Crash of a Beechcraft B60 Duke in Fullerton: 1 killed

Date & Time: Apr 18, 2019 at 1951 LT
Type of aircraft:
Registration:
N65MY
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Fullerton - Heber City
MSN:
P-314
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
380
Captain / Total hours on type:
87.00
Aircraft flight hours:
5419
Circumstances:
The pilot began the takeoff roll in visual meteorological conditions. The airplane was airborne about 1,300 ft down the runway, which was about 75% of the normal ground roll distance for the airplane’s weight and the takeoff environment. About 2 seconds after rotation, the airplane rolled left. Three seconds later, the airplane had reached an altitude of about 80 ft above ground level and was in a 90° left bank. The nose then dropped as the airplane rolled inverted and struck the ground in a right-wing-low, nose-down attitude. The airplane was destroyed. Postaccident examination did not reveal any anomalies with the airframe or engines that would have precluded normal operation. The landing gear, flap, and trim positions were appropriate for takeoff and flight control continuity was confirmed. The symmetry of damage between both propeller assemblies indicated that both engines were producing equal and high amounts of power at impact. The autopsy revealed no natural disease was present that could pose a significant hazard to flight safety. Review of surveillance video footage from before the accident revealed that the elevator was in the almost full nose-up (or trailing edge up) position during the taxi and the beginning of the takeoff roll. Surveillance footage also showed that the pilot did not perform a preflight inspection of the airplane or control check before the accident flight. According to the pilot’s friend who was also in the hangar, as the accident pilot was pushing the airplane back into his hangar on the night before the accident, he manipulated and locked the elevator in the trailing edge up position to clear an obstacle in the hangar. However, no evidence of an installed elevator control lock was found in the cabin after the accident. The loss of control during takeoff was likely due to the pilot’s use of an unapproved elevator control lock device. Despite video evidence of the elevator locked in the trailing edge up position before the accident, an examination revealed no evidence of an installed control lock in the cabin. Therefore, during the night before the accident, the pilot likely placed an unapproved object between the elevator balance weight and the trailing edge of the horizontal stabilizer to lock the elevator in the trailing edge up position. The loss of control was also due to the pilot’s failure to correctly position the elevator before takeoff. The pilot’s friend at the hangar also reported that the pilot was running about one hour late; the night before, he was trying to troubleshoot an electrical issue in the airplane that caused a circuit breaker to keep tripping, which may have become a distraction to the pilot. The pilot had the opportunity to detect his error in not freeing the elevator both before boarding the airplane and again while in the airplane, either via a control check or detecting an anomalous aft position of the yoke. The pilot directed his attention to the arrival of a motorbike in the hangar alley shortly after he pulled the airplane out of the hangar, which likely distracted the pilot and further delayed his departure. He did not conduct a preflight inspection of the airplane or control check before the accident flight, due either to distraction or time pressure.
Probable cause:
The pilot’s use of an unapproved elevator control lock device, and his failure to remove that device and correctly position the elevator before flight, which resulted in a loss of control during takeoff. Contributing to the accident was his failure to perform a preflight inspection and control check, likely in part because of distractions before boarding and his late departure time.
Final Report:

Crash of a Rockwell Sabreliner 65 near New Albany: 3 killed

Date & Time: Apr 13, 2019 at 1514 LT
Type of aircraft:
Registration:
N265DS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Broomfield - Oxford - Hamilton
MSN:
465-45
YOM:
1980
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
22200
Copilot / Total flying hours:
2250
Aircraft flight hours:
10754
Circumstances:
Two instrument-rated commercial pilots and one passenger were conducting a cross-country flight in instrument meteorological conditions when they began discussing an electrical malfunction; they then reported the electrical problem to air traffic control. The airplane subsequently made a descending right turn and impacted wooded terrain at a high speed. Most components of the airplane were highly fragmented, impact damaged, and unidentifiable. Based on the limited discussion of the electrical problem on the cockpit voice recorder and the damage to the airplane, it was not possible to determine the specific nature of the electrical malfunction the airplane may have experienced. While it was not possible to determine which systems were impacted by the electrical malfunction, it is possible the flight instruments were affected. The airplane's descending, turning, flight path before impact is consistent with a system malfunction that either directly or indirectly (through a diversion of attention) led to the pilot's loss of awareness of the airplane's performance in instrument meteorological conditions and subsequent loss of control of the airplane.
Probable cause:
An unidentified electrical system malfunction that led to the pilots losing awareness of the airplane's performance in instrument meteorological conditions and resulted in a loss of control of the airplane.
Final Report:

Crash of an IAI 1124 Westwind in Sundance: 2 killed

Date & Time: Mar 18, 2019 at 1531 LT
Type of aircraft:
Registration:
N4MH
Flight Type:
Survivors:
No
Schedule:
Panama City - Sundance
MSN:
232
YOM:
1978
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5872
Copilot / Total flying hours:
5259
Aircraft flight hours:
11030
Circumstances:
The two commercial pilots were conducting a personal, cross-country flight. A video surveillance camera at the airport captured their airplane’s approach. Review of the video revealed that, as the airplane approached the approach end of the landing runway, it began to climb, rolled left, became inverted, and then impacted terrain. The left thrust reverser (T/R) was found open and unlatched at the accident site. An asymmetric deployment of the left T/R would have resulted in a left roll/yaw. The lack of an airworthy and operable cockpit voice recorder, which was required for the flight, precluded identifying which pilot was performing pilot flying duties, as well as other crew actions and background noises, that would have facilitated the investigation. Postaccident examination of the airplane revealed that it was not equipped, nor was required to be equipped, with a nose landing gear (NLG) ground contact switch intended to preclude inflight operation of the thrust reverser (T/R). The left T/R door was found unlatched and open, and the right T/R door was found closed and latched. Further, electrical testing of the T/R left and right stow microswitches within the cockpit throttle quadrant revealed that the left stow microswitch did not operate within design specifications. Disassembly of the left and right stow microswitches revealed evidence of arc wear due to aging. Based on this information, it is likely that the airplane’s lack of an NLG ground contact switch and the age-related failure of the stow microswitches resulted in an asymmetric T/R deployment while on approach and a subsequent loss of airplane control. Also, there were additional T/R system components that were found to unairworthy that would have affected the control of the T/R system. Operational testing of the T/R system could not be performed due to the damage the airplane incurred during the accident. Toxicology testing results of the pilot’s specimens indicated that the pilot had taken diazepam, which is considered impairing at certain levels. However, the detected amounts of both diazepam and its metabolite nordiazepam were at subtherapeutic levels, and given the long half-life of these compounds, it appears that the medication was taken several days before the accident; therefore, it is unlikely that the pilot was impaired at the time of the accident and thus that his use of diazepam was a not factor in the accident.
Probable cause:
The airplane’s unairworthy thrust reverser (T/R) system due to inadequate maintenance that resulted in an asymmetric T/R deployment during an approach to the airport and the subsequent loss of airplane control.
Final Report:

Crash of a Cessna 421B Golden Eagle II in Delaware: 1 killed

Date & Time: Mar 17, 2019 at 1745 LT
Registration:
N424TW
Flight Type:
Survivors:
No
Schedule:
Dayton - Delaware
MSN:
421B-0816
YOM:
1974
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3000
Captain / Total hours on type:
48.00
Aircraft flight hours:
8339
Circumstances:
The pilot departed on a short cross-country flight in the twin-engine airplane. Instrument meteorological conditions (IMC) were present at the time. While en route at an altitude of 3,000 ft mean sea level, the pilot reported that the airplane was "picking up icing" and that he needed to "pick up speed." The controller then cleared the pilot to descend, then to climb, in order to exit the icing conditions; shortly thereafter, the controller issued a low altitude alert. The pilot indicated that he was climbing; radar and radio contact with the airplane were lost shortly thereafter. The airplane impacted a field about 7 miles short of the destination airport. Examination of the airplane was limited due to the fragmentation of the wreckage; however, no pre-impact anomalies were noted during the airframe and engine examinations. Extensive damage to the pitot static and deicing systems precluded functional testing of the two systems. A review of data recorded from onboard avionics units indicated that, about the time the pilot reported to the controller that the airplane was accumulating ice, the airplane's indicated airspeed had begun to diverge from its ground speed as calculated by position data. However, several minutes later, the indicated airspeed was zero while the ground speed remained fairly constant. It is likely that this airspeed indication was the result of icing of the airplane's pitot probe. During the final 2 minutes of flight, the airplane was in a left turn and the pilot received several "SINK RATE" and "PULL UP PULL UP" annunciations as the airplane conducted a series of climbs and descents during which its ground speed (and likely, airspeed) reached and/or exceeded the airplane's maneuvering and maximum structural cruising speeds. It is likely that the pilot became distracted by the erroneous airspeed indication due to icing of the pitot probe and subsequently lost control while maneuvering.
Probable cause:
A loss of airspeed indication due to icing of the airplane's pitot probe, and the pilot's loss of control while maneuvering.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Madeira: 1 killed

Date & Time: Mar 12, 2019 at 1516 LT
Operator:
Registration:
N400JM
Flight Phase:
Survivors:
No
Site:
Schedule:
Cincinnati - Cincinnati
MSN:
31-8152002
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6421
Captain / Total hours on type:
1364.00
Aircraft flight hours:
19094
Circumstances:
The commercial pilot was conducting an aerial observation (surveying) flight in a piston engineequipped multiengine airplane. Several hours into the flight, the pilot advised air traffic control (ATC) that the airplane had a fuel problem and that he needed to return to the departure airport. When the airplane was 8 miles from the airport, and after passing several other airports, the pilot informed ATC that he was unsure if the airplane could reach the airport. The final minutes of radar data depicted the airplane in a descent and tracking toward a golf fairway as the airplane's groundspeed decreased to a speed near the single engine minimum control airspeed. According to witnesses, they heard an engine sputter before making two loud "back-fire" sounds. One witness reported that, after the engine sputtered, the airplane "was on its left side flying crooked." Additional witnesses reported that the airplane turned to the left before it "nose-dived" into a neighborhood, impacting a tree and private residence before coming to rest in the backyard of the residence. A witness approached the wreckage immediately after the accident and observed a small flame rising from the area of the left engine. Video recorded on the witness' mobile phone several minutes later showed the airplane engulfed in flames. Examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures of either engine. The fuel systems feeding both engines were damaged by impact forces but the examined components generally displayed that only trace amounts of fuel remained; with the exception of the left engine nacelle fuel tank. Given the extent of the fire damage to this area of the wreckage, and the witness report that the post impact fire originated in this area, it is likely that this tank contained fuel. By design, this fuel in this tank was not able to supply fuel directly to either engine, but instead relied on an electric pump to transfer fuel into the left main fuel tank. Fire damage precluded a detailed postaccident examination or functional testing of the left nacelle fuel transfer pump. Other pilots who flew similar airplanes for the operator, along with a review of maintenance records for those airplanes, revealed at least three instances of these pumps failing in the months surrounding the accident. The other pilots also reported varying methods of utilizing fuel and monitoring fuel transfers of fuel from the nacelle fuel tanks, since there was no direct indication of the quantity of fuel available in the tank. These methods were not standardized between pilots within the company and relied on their monitoring the quantity of fuel in the main fuel tanks in order to ensure that the fuel transfer was occurring. Had the pilot not activated this pump, or had this pump failed during the flight, it would have rendered the fuel in the tank inaccessible. Given this information it is likely that the fuel supply available to the airplane's left engine was exhausted, and that the engine subsequently lost power due to fuel starvation. The accident pilot, along with another company pilot, identified fuel leaking from the airplane's left wing, about a week before the accident. Maintenance records showed no actions had been completed to the address the fuel leak. Due to damage sustained during the accident, the origin of the fuel leak could not be determined, nor could it be determined whether the fuel leak contributed to the fuel starvation and eventual inflight loss of power to the left engine. Because the left engine stopped producing power, the pilot would have needed to configure the airplane for single-engine flight; however, examination of the left engine's propeller found that it was not feathered. With the propeller in this state, the pilot's ability to maintain control the airplane would have been reduced, and it is likely that the pilot allowed the airplane's airspeed to decrease below the singleengine minimum controllable airspeed, which resulted in a loss of control and led to the airplane's roll to the left and rapid descent toward the terrain. Toxicology results revealed that the pilot had taken doxylamine, an over-the-counter antihistamine that can decrease alertness and impair performance of potentially hazardous tasks. Although the toxicology results indicated that the amount of doxylamine in the pilot's cavity blood was within the lower therapeutic range, review of ATC records revealed that the pilot was alert and that he was making necessary decisions and following instructions. Thus, the pilot's use of doxylamine was not likely a factor in the accident.
Probable cause:
Fuel starvation to the left engine and the resulting loss of engine power to that engine, and a loss of airplane control due to the pilot's failure to maintain the minimum controllable airspeed.
Final Report:

Crash of an Embraer ERJ-145XR in Presque Isle

Date & Time: Mar 4, 2019 at 1129 LT
Type of aircraft:
Operator:
Registration:
N14171
Survivors:
Yes
Schedule:
Newark - Presque Isle
MSN:
145-859
YOM:
2004
Flight number:
UA4933
Crew on board:
3
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5655
Captain / Total hours on type:
1044.00
Copilot / Total flying hours:
4909
Copilot / Total hours on type:
470
Circumstances:
The first instrument landing system (ILS) approach to runway 1 appeared to be proceeding normally until the first officer (the pilot flying) transitioned from instrument references inside the flight deck to outside references. During a postaccident interview, the first officer stated that he expected to see the runway at that time but instead saw “white on white” and a structure with an antenna that was part of the runway environment but not the runway itself. The captain (the pilot monitoring) stated that she saw a tower and called for a go-around. (Both flight crewmembers were most likely seeing the automated weather observing system wind sensor pole, which was located about 325 ft to the right of the runway 1 centerline and about 870 ft beyond the runway threshold, and the damage to the lightning arrester at the top of the wind sensor pole was likely due to contact with the accident airplane as it flew over the pole.) According to the cockpit voice recorder (CVR), after the go-around, the first officer asked the captain if she saw the runway lights during the approach. The captain responded that she saw the lights but that “it’s really white down there that’s the problem.” Airport personnel stated that snow plowing operations on the runway had finished about 10 minutes before the first approach. The CVR recorded the flight crew’s discussion about turning on the pilot-controlled runway lights and sounds similar to microphone clicks before and after the discussion. However, the PQI maintenance foreman stated that, after the first approach, the runway lights were not on. Thus, the investigation could not determine, based on the available evidence, whether the flight crew had turned on the runway lights during the first approach. The captain thought that the airplane had drifted off course when the first officer transitioned from flight instruments to the outside, so she instructed the first officer to remain on the instruments during the second approach until the decision altitude (200 ft above ground level [agl]). The second approach proceeded normally with no problems capturing or maintaining the localizer and glideslope. During this approach, the captain asked airport maintenance personnel to ensure that the runway lighting was on, and the PQI maintenance foreman replied that the lights were on “bright”(the high-intensity setting). Thus, the flight crew had a means to identify the runway surface even with the reported snow cover at the time. As the airplane approached the decision altitude, the captain instructed the first officer to disconnect the autopilot, which he did. About nine seconds later, the airplane reached the decision altitude, and the captain called, “runway in sight twelve o’clock.” This callout was followed by the first officer’s statement, “I’m stayin’ on the flight director ‘cause I don’t see it yet.” A few seconds later, while the airplane was below 100 ft agl, the captain and the first officer expressed confusion, stating “what the [expletive]” and “I don’t know what I'm see in’,” respectively, but neither called for a go-around. The airplane subsequently impacted the snow-covered grassy area between runway 1 and a parallel taxiway. During a postaccident interview, the first officer stated that, when he transitioned from flight instruments to the outside during the second approach, he again saw “white on white” as well as blowing snow and that the airplane touched down before he could determine what he was seeing. The maintenance foreman estimated that, at the time of the accident, the runway had about 1/8 inch of snow with about 20% to 25% of the runway visible.
Probable cause:
The flight crew’s decision, due to confirmation bias, to continue the descent below the decision altitude when the runway had not been positively identified. Contributing to the accident were:
1) the first officer’s fatigue, which exacerbated his confirmation bias, and
2) the failure of CommutAir pilots who had observed the localizer misalignment to report it to the company and air traffic before the accident.
Final Report: