Atlas Air Flight 3591

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Atlas Air Flight 3591
Prime Air (47137434372).jpg
N1217A, the Boeing 767 involved, seen nine days before the accident
DateFebruary 23, 2019 (2019-02-23)
SummaryCrashed during approach due to pilot error and spatial disorientation
SiteTrinity Bay; near Anahuac, Texas
29°45′50″N 94°42′53″W / 29.76389°N 94.71472°W / 29.76389; -94.71472Coordinates: 29°45′50″N 94°42′53″W / 29.76389°N 94.71472°W / 29.76389; -94.71472
Aircraft typeBoeing 767-375(ER)(BCF)
Aircraft nameCustomAir Obsession[1]
OperatorAtlas Air (for Amazon Air)
IATA flight No.5Y3591
ICAO flight No.GTI3591
Call signGiant 3591
Flight originMiami International Airport, Miami, Florida, United States
DestinationGeorge Bush Intercontinental Airport, Houston, Texas, United States

Atlas Air Flight 3591 was a scheduled domestic cargo flight operating for Amazon Air between Miami International Airport and George Bush Intercontinental Airport in Houston. On February 23, 2019, the Boeing 767-375ER(BCF) used for this flight crashed into Trinity Bay during approach into Houston, killing the two crew members and one passenger on board. The accident occurred near Anahuac, Texas, east of Houston, shortly before 12:45 CST (18:45 UTC).[2][3][4] This was the first fatal crash of a Boeing 767 freighter.[5]

Investigators attributed the accident to pilot error, finding that the first officer experienced spatial disorientation and inadvertently placed the aircraft in an unrecoverable dive, while the captain failed to adequately monitor the first officer's actions and the flight path of the aircraft. Flight crew training issues at Atlas Air and across the U.S. commercial aviation industry were also implicated.



The Boeing 767-375ER(BCF) (MSN 25865/430) aircraft was registered N1217A and was nearly 27 years old at the time of the accident, having been built in 1992. It was originally ordered by Canadian Airlines, but first placed into service by China Southern Airlines through GPA, an aircraft leasing company.[6] In 1997, it was transferred to LAN Airlines and flew for 19 years before being stored in January 2016. It was converted into a freighter in April 2017, and placed into service for Amazon Prime Air by Atlas Air.[7] In August 2018, Amazon named two aircraft in its fleet, including N1217A as CustomAir Obsession. The name, painted on the aircraft just aft of the cockpit windows,[8] was a near homonym of "customer obsession," an Amazon leadership principle.[9] The aircraft had accumulated more than 91,000 hours over 23,300 flights[10][11][12] and was powered by two GE CF6-80 turbofan engines.[12]:8–9[13]

Crew and passenger[edit]

There were three people onboard the aircraft.[14] Captain Ricky Blakely of Indiana (60), First Officer Conrad Jules Aska of Antigua (44), and Mesa Airlines Captain Sean Archuleta of Houston (36; a jumpseater aboard the flight), who was in his final week of employment at Mesa Airlines, and was traveling home before beginning new-hire pilot training with United Airlines, scheduled for the following week.[15]

Captain Blakely joined Atlas Air in 2015 and became a Boeing 767 captain in 2018. Before being hired by Atlas Air Blakely had previously been an Embraer ERJ-145 captain for ExpressJet. He had also been a Beechcraft 1900 first officer for CommutAir, and a flight instructor for FlightSafety International.[12]:5 Blakely logged a total of 11,172 flight hours, including 1,252 hours on the Boeing 767.[12]:3–4

First officer Aska joined Atlas Air on July 3, 2017 and received his type rating on the Boeing 767 two months later. He had logged 5,073 flight hours with 520 of them on the 767. Aska had previously been an Embraer E175 first officer with Mesa Airlines (and served with five other airlines prior to that) and also had experience on Embraer's EMB 120 Brasilia and ERJ aircraft families.[12]:5[16]

Both pilots had previous experience in landing at George Bush Intercontinental Airport.[16]


Atlas Air 3591 departed Miami at 10:33 CST (11:33 EST), with first officer Aska as the pilot flying and captain Blakely monitoring the controls. At 12:36, Aska transferred control of the aircraft to Blakely, telling him that the electronic flight instrument (EFI) switch on his side had malfunctioned. This issue was resolved a minute later, with the following being recorded on the cockpit voice recorder (CVR):

Aska: "I press the EFI button, it fixes everything."
Blakely: "Oh ya ya."

Flight 3591 was on approach towards Houston when it flew through the forward edge of a cold front, which produced an area of instrument meteorological conditions (IMC) with clouds and turbulence, with cloud tops varying from approximately 19,500 feet (5,900 m) to 27,300 feet (8,300 m) of altitude and cloud bases varying from 2,000 feet (610 m) to 3,000 feet (910 m) above ground level. The pilot of another nearby airliner reported IMC, and a video taken by a ground witness showed a shelf cloud passing over the area at the time.[12]:14–15

First officer Aska then requested radar vectors to the West side of the airport to avoid the inclement weather. The controller accepted though advised the crew to expedite their descent to 3,000 feet (910 m) and said, "I'm gunna get ya west of this weather and northbound for a baseleg." Blakely then transferred control of the aircraft back to Aska:

Aska: "Ok. Two seven zero."
Blakely: "Your controls."
Aska: "My Controls."

The flight crew then started to configure the aircraft for landing and set up the flight management system (FMS). At 12:38:02.2 CST first officer Aska called out "flaps one," and the slats were extended. 29 seconds later, the aircraft's go-around mode was activated. At 12:38:40.3, the following was heard on the CVR:

Cockpit area microphone (CAM): [Sound of master caution aural warning]
Blakely (radio transmission): "sounds good uh Giant thirty-five ninety-one."
Approach controller: "It is severe clear on the other side of this stuff so you'll have no problem gettin' the airport [unintelligible word] (either)."
Aska: "Oh. Woah! (Where's) my speed my speed? [Spoken in elevated voice]
CAM: [Sound similar to a mechanical click]
Blakely (radio transmission): "Okay."
Aska: "We're stalling! Stall!" [Exclaimed]
Voice unidentified: "[Expletive]"

The accident aircraft made a sharp turn south before going into a rapid descent. Witnesses to the crash described the plane entering a nosedive; some also recalled hearing "what sounded like lightning" before the Boeing 767 hit the ground.[17][18]

At 12:36 CST (18:36 UTC) radar and radio contact was lost. There was no distress call.[19] At 12:39:03.9 CST (18:39:03.9 UTC), the time the CVR recorded ended, Flight 3591 crashed into the north end of Trinity Bay at Jack's Pocket.[3] The area of water is within Chambers County, Texas, and is in proximity to Anahuac.[20]

The Federal Aviation Administration (FAA) issued an alert after radar and radio contact was lost around 30 miles (50 km) southeast of its destination.[21] Air traffic controllers tried at least twice to contact the flight, with no response. Controllers asked pilots aboard two nearby flights if they saw a crash site, both of whom said they did not; the crash site was located after ground witnesses called local police to report having seen the aircraft dive into the bay. The United States Coast Guard dispatched a helicopter and several boats to search for survivors; other agencies responded as well. The crash site was mostly mud marsh, with water varying in depth from zero to five feet (1.5 m) deep, and airboats were needed to access the area. Searchers found human remains and many small fragments of the aircraft and its cargo; the largest recovered piece of the aircraft was 50 ft (15 m) in length. The local sheriff described the scene as "total devastation" and surmised that the crash had not been survivable.[22][23]

Map of crash site


On February 24, Atlas Air confirmed that all three people on board died.[4][24] The victims were first identified on social media by friends and family. By February 26 the bodies of all three had been recovered, and by March 4 all had been positively identified.[25]


NTSB investigators examine debris at the edge of Trinity Bay
NTSB investigators recover the flight data recorder from Trinity Bay

Investigators from the FAA, Federal Bureau of Investigation (FBI), and National Transportation Safety Board (NTSB) were dispatched to the accident site with the NTSB leading the accident investigation.[26] A dive team from the Texas Department of Public Safety (DPS) was tasked with locating the aircraft's flight recorders and dive teams from the Houston and Baytown police departments were also on-scene assisting in the search.[27] The CVR and flight data recorder (FDR) were located and transported to an NTSB lab for analysis.[28][29] It was thought that crews would likely remain at the accident site for weeks for recovery.[30]

As of March 2019, the cause of the accident had not been determined.[31] It was noted that storm cells were nearby at the time of the accident, but this is not unusual for Bush Intercontinental.[32] CCTV cameras at the Chambers County jail show the airplane in a steep, nose-low descent just prior to impact.[33][34]

The FAA, Boeing, Atlas Air, National Air Traffic Controllers Association (NATCA), International Brotherhood of Teamsters (the pilots' labor union), Air Line Pilots Association,[35] and engine maker General Electric assisted or offered their assistance to the NTSB inquiry.[36]

After listening to the cockpit voice recorder the NTSB stated that "Crew communications consistent with a loss of control of the aircraft began approximately 18 seconds prior to the end of the recording."[31] On March 12 the NTSB stated that the airplane "pitched nose down over the next 18 seconds to about 49° in response to column input." Later that same day the statement was changed to " response to nose-down elevator deflection."[11][37]

On December 19, 2019, the NTSB released a public docket containing over 3,000 pages of factual information it had collected during the investigation, with a final report to follow at an unspecified later date. The docket contains information on "operations, survival factors, human performance, air traffic control, aircraft performance, and includes the cockpit voice recorder transcript, sound spectrum study, and the flight data recorder information."[38]

On June 11, 2020, the NTSB announced that the next board meeting would determine the cause of the accident;[39] the NTSB determined during a public board meeting held on July 14, that the flight crashed because of the first officer’s inappropriate response to an inadvertent activation of the airplane's go-around mode, resulting in his spatial disorientation that led him to place the airplane in a steep descent from which the crew did not recover.[40] The NTSB released an animation of the mishap sequence of events from the selection of Go-Around thrust to the fatal crash 31 seconds later.[41]


On August 6, 2020, the NTSB posted the final accident report to their website, which stated:

The NTSB determines that the probable cause of this accident was the inappropriate response by the first officer as the pilot flying to an inadvertent activation of the go-around mode, which led to his spatial disorientation and nose-down control inputs that placed the airplane in a steep descent from which the crew did not recover. Contributing to the accident was the captain's failure to adequately monitor the airplane's flightpath and assume positive control of the airplane to effectively intervene. Also contributing were systemic deficiencies in the aviation industry's selection and performance measurement practices, which failed to address the first officer's aptitude-related deficiencies and maladaptive stress response. Also contributing to the accident was the Federal Aviation Administration's failure to implement the pilot records database in a sufficiently robust and timely manner.[12]

The NTSB found that the descent had proceeded normally until the go-around mode was actuated and the aircraft's autopilot and autothrottle increased engine thrust and nose-up pitch as designed. Neither pilot verbally acknowledged that go-around mode had been actuated nor took any apparent action to deactivate it. Moments later, the first officer made nose-down flight control inputs for stall recovery, but the aircraft's stall warning systems had not actuated and FDR data was inconsistent with an aircraft in a stalled condition.[12]:2 The NTSB concluded that the first officer most likely struck the go-around switch accidentally with his left wrist or his wristwatch while manipulating the nearby speedbrake lever and that neither pilot realized that the aircraft's automated flight mode had been changed.[12]:ix Established procedures called for the pilot monitoring (the captain) to immediately disengage the autopilot and autothrottle and call out changes in altitude and airspeed in a suspected stall, but neither pilot did so;[12]:vii,27 while the first officer's flight control inputs were aggressive enough to override the autopilot,[12]:20 investigators concluded that the captain was distracted performing other tasks and had failed to monitor the aircraft's performance.[12]:42–43

The NTSB concluded that the aircraft was likely flying in IMC without the ground visible when the go-around mode was actuated,[12]:41 and the first officer most likely experienced a pitch-up or head-up somatogravic illusion, the false sensation that one is tilting backwards during unexpected forward acceleration in the absence of visible landmarks. Pilots with limited instrument flight proficiency have a well-documented tendency to disregard flight instruments and act instinctively in reaction to this illusion.[12]:ix, 40–41 Investigators concluded that the pilots were unable to see the ground until the aircraft exited the clouds approximately 3,000 feet (910 m) above the bay, at which point safe recovery from the steep descent would have been impossible.[12]:44–45

The NTSB was unable to determine why the first officer cycled the EFI switch prior to the accident; however, cycling the EFI switch in the 767 is generally done to solve intermittent display blanking and does not change the source of the data shown on the display, and the NTSB concluded that "whatever EFIS display anomaly the FO [first officer] experienced was resolved to both crewmembers’ satisfaction (by the FO’s cycling of the EFI switch) before the events related to the accident sequence occurred."[12]:37

Flight crew training issues[edit]

The NTSB noted that both pilots had difficulties in their training. Captain Blakely experienced difficulties during training for his type rating on the 767. On October 31, 2015, he was declared unfit for a checkride due to unsatisfactory remarks on his training which included the following:[12]:4

  • Allowing airspeed to exceed flap limits during stall recovery training
  • Forgetting to set the missed approach altitude
  • Difficulties in performing missed approaches

Blakely underwent remedial training the next day on November 1, this time with satisfactory results. The day after, he had his 767 checkride, and received his type rating on the aircraft two days later.[12][16] Despite Blakely's improvements, Atlas Air placed him in the pilot proficiency watch program (PWP) due to his training issues.[12]

First officer Aska had also experienced training difficulties with Atlas Air, more so than Blakely. He had also recorded training failures with previous employers. Another Atlas Air 767 captain who had flown with Aska described him as a "nice guy" and "definitely in the top half of the people I've flown with," though he did not state any issues regarding training.[42] Aska's first issues were reported in July 2017, the same month he joined Atlas Air, when he was declined an oral exam for his type rating on the 767 as he needed remediation training. Following the training, he passed the oral exam. Aska then went through five fixed-base (non-moving) flight simulator sessions, experiencing difficulties with normal procedures, and underwent more remediation training. In August, following two full-flight simulator training sessions, Aska's simulator partner complained that he was being "held back." Atlas Air ultimately had to restart full-flight simulator training for Aska because no other pilots remained in his training class to partner with him.[12]:5–6

Aska's first checkride on the aircraft ended in failure due to poor crew resource management (CRM) and improper aircraft control. His examiner described him as stressed and lacking situational awareness.[12]:6 Aska underwent remedial training on September 25 and the next day, he reattempted his checkride successfully, receiving his type rating on the aircraft.[12]

Investigators concluded that Aska had deliberately concealed his spotty training record when he interviewed with Atlas Air, taking advantage of shortcomings in the FAA pilot records database, which was criticized by the NTSB. A 2010 amendment to the Pilot Record Improvement Act (PRIA) passed after the 2009 crash of Colgan Air Flight 3407 required the FAA to record training failures in the database; however, this provision had not been fully implemented due to privacy concerns and industry opposition, particularly from business aviation operators who objected to the program's stringent record-keeping requirements. Atlas Air was also criticized for its reliance on agents rather than flight operations specialists to check the training backgrounds of pilots it hired.[43]

Another Atlas Air 767 captain noted that Aska had "no real interaction with Ricky Blakely," indicating that Flight 3591 may have been the first flight in which Blakely and Aska flew together.[44]

The NTSB recommended that pilots of the 767 and the similar Boeing 757 be trained to recognize and recover from inadvertent go-around mode actuation, but also concluded that available data suggested that such an actuation was a "rare and typically benign event."[12]:viii

See also[edit]


 This article incorporates public domain material from websites or documents of the National Transportation Safety Board.

  1. ^ "Taking flight". August 21, 2018.
  2. ^ "Cargo jet with three reported aboard crashes in water near Houston". NBC News.
  3. ^ a b Josephs, Leslie (February 23, 2019). "Atlas Air Flight 3591: Cargo jet crashes near Houston with 3 aboard".
  4. ^ a b "Atlas Air Confirms Family Assistance Established in Flight 3591 Accident". Atlas Air Worldwide. February 24, 2019. Retrieved February 25, 2019.
  5. ^ Ranter, Harro. "ASN Aircraft accident Boeing 767-375ER (BCF) (WL) N1217A Trinity Bay, near Anahuac, TX". Aviation Safety Network. Retrieved November 30, 2019.
  6. ^ "Amazon Cargo Aircraft Crashes on Flight 3591". February 25, 2019. Retrieved February 25, 2019.
  7. ^ Mollenhauer, Alec (October 21, 2017). "Tracking Amazon Prime Air's fleet: aircraft from six continents and 35 airlines". Retrieved February 26, 2019.
  8. ^ Sales, Luis (November 22, 2018). "Optimus' cousin, N1217A, CustomAir Obsession". Retrieved February 26, 2019 – via Facebook.
  9. ^ "Leadership Principles". Retrieved February 26, 2019.
  10. ^ "[UPDATE 8] Atlas Air Boeing 767 Operating for Amazon Prime Air Crashes". Aviation Tribune. February 24, 2019. Retrieved February 26, 2019.
  11. ^ a b "Atlas Air #3591 crashed into Trinity Bay DCA19MA086". National Transportation Safety Board. DCA19MA086. Retrieved March 13, 2019.
  12. ^ a b c d e f g h i j k l m n o p q r s t u v w "Rapid Descent and Crash into Water, Atlas Air Inc. Flight 3591, Boeing 767-375BCF, N1217A, Trinity Bay, Texas, February 23, 2019" (PDF). National Transportation Safety Board. July 14, 2020. NTSB/AAR-20/02. Retrieved August 6, 2020.
  13. ^ "FAA Registry, N1217A". Federal Aviation Administration. Retrieved February 25, 2019.
  14. ^ Collman, Ashley. "Breaking news: Boeing 767 cargo plane crashes in Texas, reportedly killing all three on board". INSIDER.
  15. ^ Schuetz, R. A. (February 24, 2019). "3 confirmed dead after Boeing 767 cargo plane's nose dive into Trinity Bay". Houston Chronicle. Retrieved February 25, 2019.
  16. ^ a b c "Operations Group Chairman's Factual Report" (PDF). National Transportation Safety Board. November 19, 2019. Retrieved December 20, 2019.
  17. ^ Kennedy, Megan; Taylor, Brittany; Aufdenspring, Matt (February 23, 2019). "3 presumed dead after cargo jet nose-dived into Trinity Bay, sheriff says". KPRC.
  18. ^ Wrigley, Deborah (February 24, 2019). "Witnesses recall moments before Atlas Air cargo plane crash in Chambers Co". ABC13 Houston. Retrieved March 6, 2019.
  19. ^ "One victim identified in deadly cargo jet crash in Chambers County". Retrieved February 25, 2019.
  20. ^ "Human remains found after Atlas Air cargo plane crashes in Chambers Co". KTRK-TV. February 23, 2019. Retrieved February 28, 2019.
  21. ^ Law, Tara. "Cargo Boeing 767 Plane, Carrying 3, Crashes Into Texas Bay". Time. Retrieved February 24, 2019.
  22. ^ Warren, David; Bleiberg, Jake (February 24, 2019). "Sheriff: No likely survivors in jetliner crash near Houston". Associated Press. Retrieved February 8, 2021. Witnesses told emergency personnel that the twin-engine plane "went in nose first," leaving a debris field three-quarters of a mile long in Trinity Bay, Chambers County Sheriff Brian Hawthorne said. "It's probably a crash that nobody would survive," he said, referring to the scene as "total devastation."
  23. ^ "Human remains found cargo plane crash in Chambers Co". ABC13 Houston. February 23, 2019. Retrieved February 8, 2021.
  24. ^ Hughes, Trevor. "Three confirmed dead after Amazon Prime Air cargo plane crash in Texas". USA Today. Retrieved February 25, 2019.
  25. ^ Jordan, Jay R. (March 4, 2019). "Pilot's remains positively identified in deadly Atlas Air cargo plane crash". CBS News. Houston Chronicle. Retrieved April 30, 2019.
  26. ^ Almasy, Steve; Silverman, Hollie. "Cargo jet with 3 aboard crashes in Texas". CNN.
  27. ^ "Two bodies recovered after a cargo plane crashes in water near Houston". CNN. Retrieved February 27, 2019.
  28. ^ "Black box recovered at Amazon plane crash site in Anahuac". Houston Chronicle. Retrieved March 1, 2019.
  29. ^ Vera, Amir (March 3, 2019). "NTSB recovers flight data recorder from cargo plane crash near Houston". CNN. Retrieved March 4, 2019.
  30. ^ "Sheriff: No likely survivors in jetliner crash near Houston". WHEC News10NBC. February 23, 2019. Retrieved February 24, 2019.
  31. ^ a b "NTSB Laboratory Completes Initial Review of Cockpit Voice Recorder, Recovers Flight Data Recorder". National Transportation Safety Board. March 5, 2019. Retrieved March 6, 2019.
  32. ^ Scherer, Jasper; Despart, Zach (February 23, 2019). "Sheriff: 'I don't believe anyone could survive' cargo plane's nose dive into Trinity Bay". Houston Chronicle. Retrieved February 24, 2019.
  33. ^ Josephs, Leslie (February 24, 2019). "Atlas Air Flight 3591: NTSB starts investigation into cargo jet crash". CNBC.
  34. ^ "Air disaster Boeing 767-375ER crash in Trinity Bay, near Anahuac, USA". YouTube. February 27, 2019.
  35. ^ "ALPA Statement on Atlas Air Flight 3591 Accident". ALPA. Air Line Pilots Association. Retrieved March 4, 2019.
  36. ^ Hemmerdinger, Jon. "Video shows Atlas 767F in 'steep' dive prior to crash: NTSB". Retrieved February 25, 2019.
  37. ^ "NTSB update on Atlas Air B767 crash: nose pitched down to about 49° 'in response to elevator deflection'". ASN News. Aviation Safety Network. March 12, 2019. Retrieved April 3, 2019.
  38. ^ "NTSB Opens Public Docket for Investigation of Atlas Air Flight 3591 Cargo Plane Crash". National Transportation Safety Board. Retrieved December 19, 2019.
  39. ^ "MEDIA ADVISORY: Fatal Atlas Air Flight 3591 Cargo Plane Crash Subject of Board Meeting". National Transportation Safety Board. June 11, 2020. Retrieved June 12, 2020.
  40. ^ "First Officer, Captain Actions, Aviation Industry Practices, Led to Fatal Atlas Air Crash". NTSB. National Transportation Safety Board. Retrieved July 15, 2020.
  41. ^ "NTSB Animation - Rapid Descent and Crash into Water Atlas Air Inc. Flight 3591". Youtube. National Transportation Safety Board. Retrieved July 14, 2020.
  42. ^ "Operations Attachment 1 - Atlas Air Interview Transcripts" (PDF). National Transportation Safety Board. Retrieved August 31, 2020.
  43. ^ Kaminski-Morrow, David (October 29, 2020). "How Atlas freighter crash revived scrutiny of pilot performance tracking". FlightGlobal. Retrieved January 13, 2021.
  44. ^ "Operations Attachment 2 - Records of Conversation" (PDF). National Transportation Safety Board. Retrieved August 31, 2020.

External links[edit]

National Transportation Safety Board

Other media