Thomson, GA, USA
N283SA
DASSAULT Falcon 20
The captain and first officer were assigned a two-leg overnight on-demand cargo flight. The flight crew were accustomed to flying night cargo flights, had regularly flown together, and were experienced pilots. The first leg of the trip was uneventful and was flown by the captain; however, their trip was delayed 2 hours and 20 minutes at the intermediate stop due to a delay in the freight arriving. The flight subsequently departed with the first officer as the pilot flying. While enroute, about forty minutes from the destination, the flight crew asked the air traffic controller about the NOTAMs for the instrument landing system (ILS) instrument approach procedure at the destination. The controller informed the flight crew of two NOTAMs: the first pertained to the ILS glidepath being unserviceable and the second applied to the localizer being unserviceable. When the controller read the first NOTAM, he stated he did not know what “GP” meant, which was the abbreviation for the glideslope/glidepath on the approach. The controller also informed the flight crew that the localizer NOTAM was not in effect until later in the morning after their expected arrival, which was consistent with the published NOTAM. The flight crew subsequently requested the ILS approach and when the flight was about 15 miles from the final approach fix, the controller cleared the flight for the ILS or localizer approach, to which the captain read back that they were cleared for the ILS approach. As the flight neared the final approach fix, the captain reported that they had the airport in sight; he cancelled the instrument flight rules flight plan, and the flight continued flying towards the runway. The airplane crossed the final approach fix off course, high, and fast. The cockpit voice recorder (CVR) transcript revealed that the captain repeatedly instructed the first officer to correct for the approach path deviations. Furthermore, the majority of the approach was conducted with a flight-idle power setting and no standard altitude callouts were made during the final approach. Instead of performing a go-around and acknowledging the unstable approach conditions, the captain instructed the first officer to use the air brakes on final approach to reduce the altitude and airspeed. Shortly after this comment was made, the captain announced that they were low on the approach and a few seconds later the captain announced that trees were observed in their flight path. The CVR captured sounds consistent with power increasing; however, the audible stall warning tone was also heard. Subsequently, the airplane continued its descent and impacted terrain about .70 nautical mile from the runway. Airport surveillance video captured the final 2 minutes of flight. Although low clouds and visibility were reported in the area of the airport, it is unlikely that the airplane entered instrument meteorological conditions in the flight’s final 2 minutes given that the airplane’s landing light was continuously in view until the airplane’s impact with trees and terrain. Furthermore, the video revealed that about the time the air brake comment was made by the captain, the airplane’s descent rate was observed to increase. Examination of the airplane revealed no evidence of preimpact mechanical malfunctions or failures with the airplane or its engines. The air brakes and their actuators were found in an extended position, the landing gear were down, and the flaps were stated by the captain to be set to full. The airplane flight manual (AFM) prohibited the use of air brakes during the approach unless anti-ice was used; however, there was no indication that anti-ice was used. It is likely that after the captain instructed the first officer to use the air brakes, the flight entered a descent that could not be recovered from, despite the rapid increase in power in the final moments of the flight. The flight profile of idle power, air brakes deployed, landing gear down, and full flaps was not a configuration that the airplane manufacturer possessed data for given that it was not an AFM approved approach configuration. The captain advised the first officer to fly the ILS approach and to follow the glideslope, despite the glideslope being out of service per the NOTAM. It was not possible to determine whether the high and low comments from the flight crew were in reference to precision approach path indicator lights, cockpit instrumentation, or a visual glidepath assessment based upon the crew’s perception of the lighted but dark night runway environment. The glideslope portion of the ILS was not broadcasting a signal due to the equipment being removed for maintenance. The investigation was unable to determine what the glideslope indications displayed in the cockpit were due to impact-related damage to the instrumentation. The approach was being conducted during dark night conditions, which likely further exacerbated the flight crew’s inability to establish a proper glide path and see the approaching trees and terrain. The controller did not state that the glideslope was out of service when he cleared the airplane for the ILS localizer approach procedure, nor was there a requirement to do so when an ILS or localizer approach was to be flown. Furthermore, when the airplane was near the final approach fix, the captain reported that they had the airport in sight, and he cancelled the instrument flight rules flight plan. The decision by the flight crew to continue straight in to land, rather than flying the procedure turn, contributed to the airplane being high for the majority of the final approach. The CVR revealed that throughout the enroute descent and approach, the captain repeatedly instructed the first officer on how to fly the airplane, reprimanding and yelling at him about basic airmanship tasks such as heading and altitude control. The captain also took control of the airplane multiple times before the final approach. The captain had ample indications that the first officer was not performing adequately to continue the flight as the pilot flying. The captain could have demonstrated leadership and positive crew resource management by relieving the first officer of flying duties well before the final approach commenced, given the challenging nature of the dark night approach that was ahead. The operator reported the first officer had not received an upgrade to captain, even after multiple years of experience on the accident airplane, due to his lack of aeronautical decision making and airmanship necessary to become a captain. This assessment was consistent with his performance during the accident flight. Furthermore, the captain’s training record showed multiple deficiencies during training. Had the operator had a flight data monitoring program (FDM) and safety management system (SMS), they could have had additional methods of identifying and monitoring the poor performing flight crew and made proactive decisions, rather than waiting for an accident to occur to discover the flight crew’s procedural non-compliance. The National Transportation Safety Board has standing recommendations to Part 135 operators to implement SMS and FDM, and for the Federal Aviation Administration to require SMS and FDM in Part 135 operations. Both pilots had cardiovascular disease that placed them at increased risk of a sudden impairing or incapacitating medical event such as heart attack or abnormal heartbeat; however, based upon the totality of the investigation’s findings, it is unlikely that the captain’s or first officer’s cardiovascular disease contributed to the accident. Furthermore, the toxicology reports for the flight crew revealed no conditions or findings that would have contributed to the accident.
HISTORY OF FLIGHTOn October 5, 2021, at 0544 eastern daylight time, a Dassault Falcon 20C airplane, N283SA, was destroyed when it impacted terrain near the Thomson-McDuffie County Airport (HQU), Thomson, Georgia. The captain and first officer were fatally injured. The airplane was operated as Pak West Airlines Flight 887 dba Sierra West Airlines, as an on-demand cargo flight under the provisions of Title 14 Code of Federal Regulations (CFR) Part 135. The flight crew initiated the first flight of the night which was about 1 hour in duration at 2132 mountain daylight time from their home base of El Paso International Airport (ELP), El Paso, Texas, to Lubbock Preston Smith International Airport (LBB), Lubbock, Texas. After about a 2 hour and 20-minute delay waiting for the freight on the ground, the accident flight was initiated from LBB to HQU. Review of air traffic control communications provided by the Federal Aviation Administration (FAA) revealed that the flight was in contact with Atlanta Air Route Traffic Control Center (ATL Center) for about the final 40 minutes of flight. At 0503 eastern daylight time, Pak West Flight 887 (PKW887) requested information about the NOTAM for the ILS localizer runway 10 instrument approach procedure at HQU. ATL Center informed the flight crew of two NOTAMs; the first pertained to the ILS runway 10 glidepath being unserviceable. When the controller advised the pilot of the glidepath NOTAM, the controller stated that he did not know what “GP” meant, which was the abbreviation for the glideslope/glidepath on the approach. The second NOTAM applied to the localizer being unserviceable. The controller informed the flight crew that the localizer NOTAM was not in effect until later in the morning after their expected arrival, which was consistent with the published NOTAM. About 0525, ATL Center asked PKW887 which approach they would like, to which they responded with the “ILS runway one zero approach.” The controller responded, “roger, standby for that.” (Note: the glidepath/glideslope was out of service at the time of the accident). At 0526, ATL Center cleared PKW887 to CEDAR intersection, which was the initial approach fix for the ILS or localizer/non-directional beacon (NDB) runway 10 approach. About 0537, ATL Center informed PKW887 that they were 15 miles southwest from CEDAR and to “cross CEDAR at or above 3,000 cleared ILS localizer one zero into Thomson McDuffie.” PKW887 read back the clearance and the controller stated it was a “good readback” and to report when established on the “procedure.” About 1 minute later, the controller advised PKW887 of a telephone number to call to cancel their instrument flight rules (IFR) clearance once on the ground; however, about 0543, PKW887 was near CEDAR and requested to cancel their IFR clearance. The controller advised PKW887 to squawk “vfr” and no further communications were received. Surveillance video located at HQU airport showed that about 0539 the airport and runway lights were activated from off to on. About 0542 the airplane’s landing lights came into view in the pitch-black horizon and were subsequently steadily visible for about 2 minutes. The video showed the airplane approaching runway 10 in a relatively constant descent and heading. About 25 seconds before the airplane’s landing lights disappeared, a momentary right turn, followed by a left turn and increased descent rate was observed. No explosion was observed when the landing lights disappeared about 0544. About 0518, the CVR revealed that during the enroute descent while the airplane was flying through an area of storms, the captain repeatedly made comments related to the first officer’s performance as the pilot flying. He sternly stated to the first officer to “fly the airplane” multiple times and the captain subsequently stated, “I’ve got the airplane.” About 1 minute later, the captain issued raised-voice instructions to the first officer on appropriate headings to fly. About 0521, the captain read back a heading clearance from ATC, and the captain stated, “you fly the damn airplane.” A few minutes later, the captain made comments consistent with reading portions of the ILS or Localizer Runway 10 approach chart; however, the comments were interrupted when the captain again made more heading instructions to the first officer. About 0527, as the airplane was approaching an assigned altitude during the descent, the captain exclaimed “altitude” and then shouted, “I’ll get that, you fly the damn airplane. I don’t want you to kill me.” About 0532, the flight crew was attempting to load and navigate to the CEDAR intersection and the captain said that he would fly the airplane while the first officer loaded the waypoint. About 1 minute later, the captain stated to the first officer “you got the airplane.” For the next 3 minutes the captain made repeated comments on what headings, speed, and altitudes the first officer needed to fly, and instructed him to adjust the trim wheel. At 0539:28, as the flight was nearing the final approach fix and attempting to activate the pilot-controlled lighting, the captain stated in a frustrated tone, “would you fly the airplane- man-uhh man- I’ve been doing everything else.” A few seconds later, the captain stated, “here it is right over.” The captain subsequently stated, “fly the ILS approach.” The captain also noted that air brakes were stowed, flaps were set to 40°, and the before landing checklist was complete. At 0541:15, the captain stated, “follow the glideslope without that” and about 30 seconds later stated that the localizer was alive. At 0542:20, the captain stated, “I want you to- I want you to fly the airplane.” A few seconds later, the captain stated that landing flaps were selected, and he reported to ATC that they had joined the localizer, had a “visual” on the runway, and canceled the IFR clearance. At 0543:22, the captain made repeated comments that they were high and fast and that they needed to lose 20 kts. A few seconds later, the captain stated, “let’s use your air brakes again.” At 0543:51, the captain stated, “you’re way high,” and the first officer responded, “no I’m not.” The captain responded with “look” and “you’re fifteen knots fast we got a short runway.” About 0544, the captain again stated, “use your air brake” and about 4 seconds later, the captain stated, “now you’re low.” About 6 seconds later, the captain stated in an elevated voice, “you got trees.” Power was heard to increase rapidly, the audible electronic pulsating stall warning activated, and at 0544:07, the sound of impact was heard. An automatic dependent surveillance – broadcast (ADS-B) performance study conducted by the National Transportation Safety Board’s (NTSB) Vehicle Performance Division found that the airplane crossed CEDAR (the final approach fix) at 2,600 ft mean sea level (msl) and 500 ft to the left of the extended runway centerline. After CEDAR, the flight track continued toward the runway and continued to be about 600 ft above the 3° visual glide path and further deviated to the left of the runway heading until about 3 nautical miles from the threshold, when the descent rate increased. The airplane’s airspeed at that time was about 150 kts. ADS-B coverage ended at 05:43:54, about 3,000 ft short of the first recorded tree strike. The final recorded altitude was 900 ft msl (400 ft above ground level [agl]) and the calculated airspeed was 137 kts. Figures 1 and 2 provide an overview of the flight track data, expected approach path, and summary CVR comments related to the approach. Figure 1: Altitude compared to 3° visual glide slope, flight path compared to runway heading, and calculated ground and airspeeds for final 6 NM of the approach. Figure 2: Altitude, calibrated airspeed, and groundspeed with selected end of flight CVR events. “CRT” is “Comment related to –”. Red dotted line shows estimated altitude trend. ADS-B data ended at 05:43:54. The recorded CVR audio from the cockpit area microphone channel was evaluated in an attempt to determine the engines’ N1 operating speeds during the final approach phase of the accident flight. The sound spectrum study found that for about the last minute of the flight the engine N1 speeds were near flight idle, and further decreased to flight idle for the final 30 seconds before the initial impact with trees. After the initial impact was heard, both N1 speeds were observed to rise rapidly before the recording ended. PERSONNEL INFORMATIONCaptain According to the operator’s training and employment records, in September 2019 the captain satisfactorily completed indoctrination training and ground training and was subsequently assigned to the DA20 as a pilot in command. The captain completed multiple airman competency/proficiency checks from 2019 through 2021. Each check was ultimately completed satisfactorily; however, multiple line checks required retraining and testing due to unsatisfactory performance of required task items. Some example areas that were required to be retrained and tested were circling approaches and steep turns. According to the captain’s resumé and records from his former employer Ameristar Jetcharter Inc. (Ameristar), he was employed by the operator as a pilot from June 2017 through August 2019. On December 22, 2017, an airman competency/proficiency check (14 CFR 135.293 and 135.297 checks) in a DA20 simulator was marked as disapproved. The remarks from the check airman stated in part that during instrument procedures the captain was “cleared for right turn by ATC, mis-set hdg bug resulting in left turn. Distraction resulted in loss of airspeed to full stall condition.” A few days later, the pilot satisfactorily completed the check. He served as SIC through mid-January 2018 and was subsequently upgraded to PIC. First Officer According to operator training and employment records, on August 20, 2009, the first officer was hired and assigned to the DA20 as an SIC after satisfactorily completing indoctrination training and ground and flight training. The pilot left the operator for 5 years, returned in 2019, and was reassigned again as an SIC DA20 flight crewmember. On December 30, 2020, an airman competency/proficiency check (14 CFR 135.293) was completed satisfactorily with remarks that stated, “SIC Only.” The operator reported that the first officer was designated as a SIC only due to pilot performance and a lack of aeronautical decision making and airmanship necessary to become a PIC/captain. AIRCRAFT INFORMATIONApproach Speed The airplane’s landing reference speed, Vref, for flaps 40° (which was indicated in the CVR transcript), 20,000 lbs, and no airbrakes was 113 kts. This speed was consistent with what was found set with the speed bugs on both the pilot and co-pilot airspeed indicators (115, 110 knots, respectively). Air Brakes According to the DA20 maintenance manual and operating manual, the air brakes are electro-hydraulic devices on both wings situated on the upper surface that permits aerodynamic braking of the airplane in flight. The maximum deflection is 70° and they are held in place by hydraulic pressure. The airbrakes are deployed through the use of a handle located on the center console of the cockpit closer to the left seat pilot. The air brakes operate in a deployed or stowed configuration. The time to extend the air brakes is 2 to 3 seconds and retraction is 3 to 4 seconds. There were two annunciator lights associated with the deployment of the airbrakes. The DA20 AFM stated in part that the airbrakes were to be checked IN during the approach. The manual further states that, “In approach with flaps extended, the airbrakes must be retracted. If the approach is made with the anti-ice on, the airbrakes may be extended down to 500 ft above the ground.” Furthermore, the approach speed must be increased by 10 kts as long as the air brakes are out. Based upon a review of the CVR transcript, an engine sound spectrum study, and review of meteorological information, there was no evidence that the anti-ice system was on during the approach. Aerodynamic Stall Speed and Systems Information Based upon an expected landing weight of 20,280 lbs and the airplane’s equipped instrumentation, the aerodynamic stall speed was likely about 91 KIAS (Flaps 40°) and 95 KIAS (Flaps 25°). The AFM airspeed limitations stated: CAUTION: DO NOT INTENTIONALLY FLY THE AIRPLANE SLOWER THAN INITIAL STALL WARNING ONSET According to Dassault Aviation representatives, there was no data that existed as to what flight characteristics the airplane would demonstrate in an idle power, full landing flaps, landing gear down, and air brakes deployed configuration. The airplane was equipped with a multi-faceted stall warning system. According to the operations manual, the stall warning system was designed to inform the pilot of a forthcoming stall by sounding an aural warning. When the airplane is approaching stalling conditions a modulated medium pitch will sound 2/3 seconds on, 1/3 seconds off. Operator Information The operator, Pak West Airlines, dba Sierra West Airlines (SWA), held a Title 14 CFR Part 135 air operator certificate with the FAA. According to SWA records, the accident flight crew flew together routinely and commonly performed overnight flights. The flight crew schedules, and duty day were consistent with Part 135 regulations. The SWA DA20 standard operating procedures stated that during visual approaches the PNF (pilot not flying) was to announce 1,000 ft, 500 ft, 100 ft, and 50 ft agl altitude callouts. The CVR transcript revealed that none of these altitude callouts were made by the captain, who was the pilot not flying. The SWA General Operations Manual (GOM) defined “stabilizing approach concept” as the procedure by which the crew maintains a stable speed, configuration, descent rate, vertical flight path, and engines spooled. The GOM further outlined that both pilots were responsible for ensuring the approach was stabilized before continuing below minimum altitudes that varied dependent upon the type of approach being flown. The minimum altitude for visual approaches was 500 ft agl. The GOM further provided a warning that that the flight crew was responsible for taking “immediate action” of a go-around or missed approach if “stabilized conditions” are not met. The GOM stated that it was critical to flight safety that either pilot had the ability to call for a go-around if they believe an unsafe condition exists. The go-around action was required to be associated with immediate action of executing a missed approach, without question, because of the immediacy of the situation. METEOROLOGICAL INFORMATIONAn NTSB weather study found that low clouds, drizzle and rain, and low visibility likely persisted along the approach path. Dark nighttime conditions existed at the time of the accident with both the sun and the moon below the horizon. Review of a surveillance video at the airport revealed that the airplane’s landing light came into view about 2 minutes before disappearing into the trees. The view of the landing light was steady and continuous, and there was no indication that the airplane entered clouds in the viewable 2 minutes. There were inflight advisories current for the area for thunderstorms west and north of the destination, and for IFR conditions over the region. AIRPORT INFORMATIONApproach Speed The airplane’s landing reference speed, Vref, for flaps 40° (which was indicated in the CVR transcript), 20,000 lbs, and no airbrakes was 113 kts. This speed was consistent with what was found set with the speed bugs on both the pilot and co-pilot airspeed indicators (115, 110 knots, respectively). Air Brakes According to the DA20 maintenance manual and operating manual, the air brakes are electro-hydraulic devices on both wings situated on the upper surface that permits aerodynamic braking of the airplane in flight. The maximum deflection is 70° and they are held in place by hydraulic pressure. The airbrakes are deployed through the use of a handle located on the center console of the cockpit closer
The flight crew’s continuation of an unstable dark night visual approach and the captain’s instruction to use air brakes during the approach contrary to airplane operating limitations, which resulted in a descent below the glide path, and a collision with terrain. Contributing to the accident was the captain’s poor crew resource management and failure to take over pilot flying responsibilities after the first officer repeatedly demonstrated deficiencies in flying the airplane, and the operator’s lack of safety management system and flight data monitoring program to proactively identify procedural non-compliance and unstable approaches.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
