Loading
Aviation
10 min read
Areas of Expertise :
Aviation, Pilot, Human Factors, Accident Reconstruction, Aircraft
Published Date:
Last Modified Date:
Jurisdiction:
Federal. Fifth Circuit
On February 23, 2019, Atlas Air Flight 3591, a Boeing 767-375BCF, crashed into Trinity Bay near Anahuac, Texas, while approaching George Bush Intercontinental Airport in Houston. The flight had departed Miami International Airport and was operated by Atlas Air as a Part 121 domestic cargo flight for Amazon.com Services LLC. NTSB press releases also stated that the aircraft carried cargo for the U.S. Postal Service. The captain, the first officer, and a nonrevenue pilot riding in the jumpseat died in the crash.
The National Transportation Safety Board investigated the flight crew’s actions, the aircraft’s automation, the first officer’s training history, Atlas Air’s pilot-record review process, and the captain’s monitoring of the flightpath. The NTSB’s findings addressed probable cause and safety issues, not civil liability or damages.
The NTSB found that the airplane’s go-around mode was inadvertently activated while the first officer was flying. After the inadvertent activation, the airplane’s automation advanced the thrust levers and increased pitch, consistent with go-around mode. Neither crewmember called out the mode change before the first officer made nose-down control inputs that matched an incorrect response to a perceived stall, even though the aircraft was not actually stalled.
The NTSB determined that the first officer’s incorrect response led to spatial disorientation and a steep descent from which the crew did not recover. The Board also found that the captain’s failure to adequately monitor the aircraft’s flightpath and assume positive control contributed to the accident.
Atlas Air Flight 3591 departed Miami International Airport for George Bush Intercontinental Airport in Houston as a domestic cargo flight operated by Atlas Air for Amazon.com Services LLC. During approach, the Boeing 767-375BCF rapidly descended from about 6,000 feet and crashed into a shallow marsh area of Trinity Bay near Anahuac, Texas. The captain, first officer, and nonrevenue jumpseat pilot were killed.
The crash led to an NTSB investigation into the aircraft’s final flightpath, cockpit recordings, weather conditions, crew actions, aircraft systems, and operating records. Although the final moments of flight became central to the investigation, the record later expanded to include the first officer’s training history, prior performance concerns, employment-history disclosures, and Atlas Air’s review of pilot qualification information.
Early NTSB updates confirmed that the cockpit voice recorder and flight data recorder were central to reconstructing the accident sequence. The agency reported that crew communications consistent with a loss of control began shortly before the end of the cockpit voice recording. Those early findings directed attention to the aircraft’s rapid descent and the crew’s actions immediately before impact.
The full explanation came later. In its final report, the NTSB tied the accident sequence to inadvertent go-around mode activation, the aircraft’s expected automation response, and the first officer’s incorrect nose-down control inputs.
Public docket records show that Archuleta v. Atlas Air Worldwide Holdings, Inc. was filed in the Southern District of Texas on May 20, 2019. The case was later terminated on May 12, 2020. That docket history confirms that at least one federal civil action followed the crash, but it does not prove that every related claim reached a final public resolution.
Any detailed description of the complaint’s allegations should be tied to the complaint itself, a court filing, or reliable public reporting. Without that support, the allegations should be described carefully as civil claims rather than established findings.
Public reporting described a wrongful-death lawsuit filed by Elliott Aska, the brother of First Officer Conrad Aska, in Florida state court. The reported defendants included Atlas Air entities, Amazon-related entities, Flightstar Aircraft Services, LLC, and F & E Aircraft Maintenance (Miami) L.L.C. Federal docket records show that the case was removed to the U.S. District Court for the Southern District of Florida on September 23, 2019, and remanded to state court on October 7, 2019.
It was described that the Aska lawsuit as alleging negligence by Atlas, Amazon-related entities, and maintenance suppliers. The reported allegations addressed aircraft airworthiness, maintenance, operational use, foreseeable safety risks, pilot training, and pilot overwork or fatigue-related concerns. These were civil allegations, not NTSB findings.
The NTSB later stated that there was insufficient information to determine whether the flight crewmembers were fatigued at the time of the accident. The NTSB’s final report gave a more specific account of the training and operational issues found in the accident record. The Board focused mainly on First Officer Conrad Aska’s prior training-performance difficulties, his response to unexpected training scenarios, and his incomplete or inaccurate employment-history disclosures. The NTSB also addressed Atlas Air’s pilot-record review process, finding that the company’s reliance on human resources personnel and designated agents contributed to a failure to evaluate a prior unsuccessful captain-upgrade attempt at another employer.
The captain’s role was analyzed separately. The NTSB found that while the captain was setting up the approach and communicating with air traffic control, his attention was diverted from monitoring the airplane’s state. The Board also found that his failure to command a positive transfer of control allowed the first officer to continue forcing the airplane into a steepening descent.
The NTSB opened a public docket containing factual materials collected during the investigation. The docket included factual reports covering operations, survival factors, human performance, air traffic control, aircraft performance, cockpit voice recorder information, sound studies, flight data recorder information, interview transcripts, photographs, and other investigative materials.
The NTSB cautioned that the docket contained factual information only. It did not include final analysis, findings, recommendations, or probable cause determinations. The final report later discussed pilot training history, hiring review, prior performance issues, and Atlas Air’s evaluation of the first officer.
At its public board meeting on July 14, 2020, the NTSB adopted its final accident report and probable cause findings. The Board concluded that the first officer’s inappropriate response to the inadvertent activation of go-around mode caused the crash. That response led to spatial disorientation and nose-down control inputs that placed the aircraft in a steep descent from which the crew did not recover.
The NTSB also found that the captain’s failure to adequately monitor the aircraft’s flightpath and assume positive control contributed to the accident. These findings made automation awareness, instrument discipline, callouts, monitoring duties, and command intervention central to the operational-error analysis.
The final report examined the first officer’s earlier training-performance difficulties, simulator evaluations, prior proficiency concerns, and failure to disclose certain training history. The Board also discussed broader industry issues involving pilot selection, performance measurement, and access to complete pilot records across employers.
Those findings support closer review of negligent training, negligent hiring or retention theories, pilot qualification records, and crew resource management in related aviation claims. The accident record involved both the final cockpit sequence and earlier decisions about pilot screening, records review, and training oversight.
Court:
United States District Court for the Southern District of Texas
Case Name:
Archuleta v. Atlas Air Worldwide Holdings, Inc. et al.
Aviation Accidents
Aircraft Accidents
Pilot Training
Commercial Air Transportation
Airline management
Accident Investigation and Reconstruction
Transportation Safety
Autopilot
Safety Management
On February 23, 2019, Atlas Air Flight 3591, a Boeing 767-375BCF, crashed into Trinity Bay near Anahuac, Texas, while approaching George Bush Intercontinental Airport in Houston. The flight had departed Miami International Airport and was operated by Atlas Air as a Part 121 domestic cargo flight for Amazon.com Services LLC. NTSB press releases also stated that the aircraft carried cargo for the U.S. Postal Service. The captain, the first officer, and a nonrevenue pilot riding in the jumpseat died in the crash.
The National Transportation Safety Board investigated the flight crew’s actions, the aircraft’s automation, the first officer’s training history, Atlas Air’s pilot-record review process, and the captain’s monitoring of the flightpath. The NTSB’s findings addressed probable cause and safety issues, not civil liability or damages.
The NTSB found that the airplane’s go-around mode was inadvertently activated while the first officer was flying. After the inadvertent activation, the airplane’s automation advanced the thrust levers and increased pitch, consistent with go-around mode. Neither crewmember called out the mode change before the first officer made nose-down control inputs that matched an incorrect response to a perceived stall, even though the aircraft was not actually stalled.
The NTSB determined that the first officer’s incorrect response led to spatial disorientation and a steep descent from which the crew did not recover. The Board also found that the captain’s failure to adequately monitor the aircraft’s flightpath and assume positive control contributed to the accident.
Atlas Air Flight 3591 departed Miami International Airport for George Bush Intercontinental Airport in Houston as a domestic cargo flight operated by Atlas Air for Amazon.com Services LLC. During approach, the Boeing 767-375BCF rapidly descended from about 6,000 feet and crashed into a shallow marsh area of Trinity Bay near Anahuac, Texas. The captain, first officer, and nonrevenue jumpseat pilot were killed.
The crash led to an NTSB investigation into the aircraft’s final flightpath, cockpit recordings, weather conditions, crew actions, aircraft systems, and operating records. Although the final moments of flight became central to the investigation, the record later expanded to include the first officer’s training history, prior performance concerns, employment-history disclosures, and Atlas Air’s review of pilot qualification information.
Early NTSB updates confirmed that the cockpit voice recorder and flight data recorder were central to reconstructing the accident sequence. The agency reported that crew communications consistent with a loss of control began shortly before the end of the cockpit voice recording. Those early findings directed attention to the aircraft’s rapid descent and the crew’s actions immediately before impact.
The full explanation came later. In its final report, the NTSB tied the accident sequence to inadvertent go-around mode activation, the aircraft’s expected automation response, and the first officer’s incorrect nose-down control inputs.
Public docket records show that Archuleta v. Atlas Air Worldwide Holdings, Inc. was filed in the Southern District of Texas on May 20, 2019. The case was later terminated on May 12, 2020. That docket history confirms that at least one federal civil action followed the crash, but it does not prove that every related claim reached a final public resolution.
Any detailed description of the complaint’s allegations should be tied to the complaint itself, a court filing, or reliable public reporting. Without that support, the allegations should be described carefully as civil claims rather than established findings.
Public reporting described a wrongful-death lawsuit filed by Elliott Aska, the brother of First Officer Conrad Aska, in Florida state court. The reported defendants included Atlas Air entities, Amazon-related entities, Flightstar Aircraft Services, LLC, and F & E Aircraft Maintenance (Miami) L.L.C. Federal docket records show that the case was removed to the U.S. District Court for the Southern District of Florida on September 23, 2019, and remanded to state court on October 7, 2019.
It was described that the Aska lawsuit as alleging negligence by Atlas, Amazon-related entities, and maintenance suppliers. The reported allegations addressed aircraft airworthiness, maintenance, operational use, foreseeable safety risks, pilot training, and pilot overwork or fatigue-related concerns. These were civil allegations, not NTSB findings.
The NTSB later stated that there was insufficient information to determine whether the flight crewmembers were fatigued at the time of the accident. The NTSB’s final report gave a more specific account of the training and operational issues found in the accident record. The Board focused mainly on First Officer Conrad Aska’s prior training-performance difficulties, his response to unexpected training scenarios, and his incomplete or inaccurate employment-history disclosures. The NTSB also addressed Atlas Air’s pilot-record review process, finding that the company’s reliance on human resources personnel and designated agents contributed to a failure to evaluate a prior unsuccessful captain-upgrade attempt at another employer.
The captain’s role was analyzed separately. The NTSB found that while the captain was setting up the approach and communicating with air traffic control, his attention was diverted from monitoring the airplane’s state. The Board also found that his failure to command a positive transfer of control allowed the first officer to continue forcing the airplane into a steepening descent.
The NTSB opened a public docket containing factual materials collected during the investigation. The docket included factual reports covering operations, survival factors, human performance, air traffic control, aircraft performance, cockpit voice recorder information, sound studies, flight data recorder information, interview transcripts, photographs, and other investigative materials.
The NTSB cautioned that the docket contained factual information only. It did not include final analysis, findings, recommendations, or probable cause determinations. The final report later discussed pilot training history, hiring review, prior performance issues, and Atlas Air’s evaluation of the first officer.
At its public board meeting on July 14, 2020, the NTSB adopted its final accident report and probable cause findings. The Board concluded that the first officer’s inappropriate response to the inadvertent activation of go-around mode caused the crash. That response led to spatial disorientation and nose-down control inputs that placed the aircraft in a steep descent from which the crew did not recover.
The NTSB also found that the captain’s failure to adequately monitor the aircraft’s flightpath and assume positive control contributed to the accident. These findings made automation awareness, instrument discipline, callouts, monitoring duties, and command intervention central to the operational-error analysis.
The final report examined the first officer’s earlier training-performance difficulties, simulator evaluations, prior proficiency concerns, and failure to disclose certain training history. The Board also discussed broader industry issues involving pilot selection, performance measurement, and access to complete pilot records across employers.
Those findings support closer review of negligent training, negligent hiring or retention theories, pilot qualification records, and crew resource management in related aviation claims. The accident record involved both the final cockpit sequence and earlier decisions about pilot screening, records review, and training oversight.
In a case involving this type of flight sequence, aviation accident reconstruction experts may analyze the aircraft’s descent profile, flightpath, impact sequence, and cockpit events. Their review may include flight data recorder information, cockpit voice recorder timing, radar data, weather conditions, aircraft performance, and NTSB factual materials.
Pilot training experts may evaluate training programs, recurrent training, simulator scenarios, remediation practices, and proficiency checks. In a case like Atlas Air Flight 3591, their review may focus on how pilots are trained to recognize automation mode changes, respond to go-around activation, manage upset recovery, distinguish stall cues from non-stall conditions, and recover using instruments in limited-visibility conditions.
Human factors experts may explain how pilots process motion, acceleration, workload, startle, automation changes, and instrument cues under stress. In loss-of-control cases, they may address spatial disorientation, attention narrowing, surprise response, and breakdowns in instrument scan.
Crew resource management experts may assess cockpit communication, monitoring duties, task sharing, command intervention, and transfer-of-control procedures. In the Atlas Air Flight 3591 fact pattern, those issues connect to the absence of a clear mode-change callout and the captain’s failure to intervene before the aircraft entered an unrecoverable descent.
Aircraft systems experts may explain flight automation, autopilot functions, autothrottle behavior, flight-director cues, cockpit indications, and related Boeing 767 systems. Their review can help distinguish between a system malfunction, normal automation response, system design, and pilot interpretation of cockpit cues.
Atlas Air Flight 3591 is not only a case about the first officer’s final control inputs. The NTSB record also raised issues involving hiring review, training-history disclosure, simulator remediation, crew monitoring, and organizational safety oversight. Attorneys evaluating similar cases should review both the accident sequence and any pre-accident information showing pilot performance concerns.
The case shows why prior checkride failures, simulator deficiencies, remediation, crew resource management concerns, and undisclosed training history may matter in aviation litigation. Discovery may include training records from current and former employers, FAA records, application materials, check-airman notes, simulator evaluations, remedial training files, and internal proficiency-watch records where available.
The inadvertent activation of go-around mode was central to the accident sequence. In cases involving modern transport aircraft, attorneys should examine whether the crew recognized mode changes, understood flight-director cues, monitored automation behavior, and followed required callout procedures. Automation confusion may affect claims or defenses involving training adequacy, cockpit discipline, and reasonable pilot response.
NTSB factual reports, docket materials, flight data, and cockpit voice recorder transcripts can assist civil litigation preparation. However, lawyers should distinguish between factual materials and formal probable-cause conclusions, which may face admissibility limits depending on the court and purpose.
A careful litigation strategy should rely on admissible evidence, independent expert analysis, and case-specific causation opinions rather than simply repeating the Board’s final conclusion.
Public records confirm that at least one federal wrongful-death action was filed after the crash, and public reporting described additional claims. However, the available public record does not clearly establish that all related civil claims were publicly resolved through one final settlement or judgment.
Blog language should avoid stating that the litigation was fully closed unless that statement is supported by docket materials, settlement filings, or reliable reporting.
Atlas Air Flight 3591 began as a scheduled cargo flight from Miami to Houston and ended during approach when the Boeing 767 rapidly descended into Trinity Bay. The NTSB traced the accident sequence to the inadvertent activation of go-around mode, the first officer’s incorrect nose-down control inputs, spatial disorientation, and the captain’s failure to adequately monitor the aircraft’s flightpath and intervene.
The post-crash record also addressed events that occurred before the final descent. The NTSB examined the first officer’s earlier training-performance difficulties, simulator evaluations, prior proficiency concerns, incomplete or inaccurate employment-history disclosures, and Atlas Air’s pilot-record review process.
Public litigation records and reporting show that wrongful-death claims followed the crash, with allegations tied to pilot training, aircraft maintenance, operational safety, corporate oversight, and fatigue-related concerns. Those allegations should be treated separately from the NTSB’s safety findings.
What caused the Atlas Air Flight 3591 crash near Houston?
The NTSB determined that the crash was caused by the first officer’s incorrect response to the inadvertent activation of the airplane’s go-around mode. That response led to spatial disorientation and nose-down control inputs that placed the aircraft in a steep descent from which the crew did not recover.
What pilot training issues did the NTSB examine in Atlas Air Flight 3591?
The NTSB examined the first officer’s earlier training-performance difficulties, simulator evaluations, prior proficiency concerns, training-history disclosures, automation response, and crew resource management. These issues became part of the accident record because investigators reviewed both the final cockpit sequence and earlier pilot-performance information.
Was Atlas Air Flight 3591 operating for Amazon?
Yes. The NTSB final report identified the Boeing 767-375BCF as a domestic cargo flight operated by Atlas Air for Amazon.com Services LLC. NTSB press releases also stated that the aircraft carried cargo for the U.S. Postal Service. Later wrongful-death claims reportedly named Atlas Air and Amazon-related entities among the defendants.
What role did aircraft automation play in the accident?
The airplane’s go-around mode was inadvertently activated during approach. The automated flight functions advanced the thrust levers and increased pitch, consistent with go-around mode. The crew did not call out or appear to recognize the mode change before the first officer made incorrect nose-down control inputs.
What pilot training and screening issues appeared in the Atlas Air Flight 3591 record?
The NTSB record connected the final cockpit sequence with earlier concerns about training performance, simulator evaluations, pilot records, hiring review, and crew resource management. Those facts became part of the post-crash legal and safety discussion involving pilot screening, operational error, and airline training oversight.
In a case involving this type of flight sequence, aviation accident reconstruction experts may analyze the aircraft’s descent profile, flightpath, impact sequence, and cockpit events. Their review may include flight data recorder information, cockpit voice recorder timing, radar data, weather conditions, aircraft performance, and NTSB factual materials.
Pilot training experts may evaluate training programs, recurrent training, simulator scenarios, remediation practices, and proficiency checks. In a case like Atlas Air Flight 3591, their review may focus on how pilots are trained to recognize automation mode changes, respond to go-around activation, manage upset recovery, distinguish stall cues from non-stall conditions, and recover using instruments in limited-visibility conditions.
Human factors experts may explain how pilots process motion, acceleration, workload, startle, automation changes, and instrument cues under stress. In loss-of-control cases, they may address spatial disorientation, attention narrowing, surprise response, and breakdowns in instrument scan.
Crew resource management experts may assess cockpit communication, monitoring duties, task sharing, command intervention, and transfer-of-control procedures. In the Atlas Air Flight 3591 fact pattern, those issues connect to the absence of a clear mode-change callout and the captain’s failure to intervene before the aircraft entered an unrecoverable descent.
Aircraft systems experts may explain flight automation, autopilot functions, autothrottle behavior, flight-director cues, cockpit indications, and related Boeing 767 systems. Their review can help distinguish between a system malfunction, normal automation response, system design, and pilot interpretation of cockpit cues.
Atlas Air Flight 3591 is not only a case about the first officer’s final control inputs. The NTSB record also raised issues involving hiring review, training-history disclosure, simulator remediation, crew monitoring, and organizational safety oversight. Attorneys evaluating similar cases should review both the accident sequence and any pre-accident information showing pilot performance concerns.
The case shows why prior checkride failures, simulator deficiencies, remediation, crew resource management concerns, and undisclosed training history may matter in aviation litigation. Discovery may include training records from current and former employers, FAA records, application materials, check-airman notes, simulator evaluations, remedial training files, and internal proficiency-watch records where available.
The inadvertent activation of go-around mode was central to the accident sequence. In cases involving modern transport aircraft, attorneys should examine whether the crew recognized mode changes, understood flight-director cues, monitored automation behavior, and followed required callout procedures. Automation confusion may affect claims or defenses involving training adequacy, cockpit discipline, and reasonable pilot response.
NTSB factual reports, docket materials, flight data, and cockpit voice recorder transcripts can assist civil litigation preparation. However, lawyers should distinguish between factual materials and formal probable-cause conclusions, which may face admissibility limits depending on the court and purpose.
A careful litigation strategy should rely on admissible evidence, independent expert analysis, and case-specific causation opinions rather than simply repeating the Board’s final conclusion.
Public records confirm that at least one federal wrongful-death action was filed after the crash, and public reporting described additional claims. However, the available public record does not clearly establish that all related civil claims were publicly resolved through one final settlement or judgment.
Blog language should avoid stating that the litigation was fully closed unless that statement is supported by docket materials, settlement filings, or reliable reporting.
Atlas Air Flight 3591 began as a scheduled cargo flight from Miami to Houston and ended during approach when the Boeing 767 rapidly descended into Trinity Bay. The NTSB traced the accident sequence to the inadvertent activation of go-around mode, the first officer’s incorrect nose-down control inputs, spatial disorientation, and the captain’s failure to adequately monitor the aircraft’s flightpath and intervene.
The post-crash record also addressed events that occurred before the final descent. The NTSB examined the first officer’s earlier training-performance difficulties, simulator evaluations, prior proficiency concerns, incomplete or inaccurate employment-history disclosures, and Atlas Air’s pilot-record review process.
Public litigation records and reporting show that wrongful-death claims followed the crash, with allegations tied to pilot training, aircraft maintenance, operational safety, corporate oversight, and fatigue-related concerns. Those allegations should be treated separately from the NTSB’s safety findings.
What caused the Atlas Air Flight 3591 crash near Houston?
The NTSB determined that the crash was caused by the first officer’s incorrect response to the inadvertent activation of the airplane’s go-around mode. That response led to spatial disorientation and nose-down control inputs that placed the aircraft in a steep descent from which the crew did not recover.
What pilot training issues did the NTSB examine in Atlas Air Flight 3591?
The NTSB examined the first officer’s earlier training-performance difficulties, simulator evaluations, prior proficiency concerns, training-history disclosures, automation response, and crew resource management. These issues became part of the accident record because investigators reviewed both the final cockpit sequence and earlier pilot-performance information.
Was Atlas Air Flight 3591 operating for Amazon?
Yes. The NTSB final report identified the Boeing 767-375BCF as a domestic cargo flight operated by Atlas Air for Amazon.com Services LLC. NTSB press releases also stated that the aircraft carried cargo for the U.S. Postal Service. Later wrongful-death claims reportedly named Atlas Air and Amazon-related entities among the defendants.
What role did aircraft automation play in the accident?
The airplane’s go-around mode was inadvertently activated during approach. The automated flight functions advanced the thrust levers and increased pitch, consistent with go-around mode. The crew did not call out or appear to recognize the mode change before the first officer made incorrect nose-down control inputs.
What pilot training and screening issues appeared in the Atlas Air Flight 3591 record?
The NTSB record connected the final cockpit sequence with earlier concerns about training performance, simulator evaluations, pilot records, hiring review, and crew resource management. Those facts became part of the post-crash legal and safety discussion involving pilot screening, operational error, and airline training oversight.
Aviation Accidents
Aircraft Accidents
Pilot Training
Commercial Air Transportation
Airline management
Accident Investigation and Reconstruction
Transportation Safety
Autopilot
Safety Management
Aviation, +4
Aviation
Aviation, +4
Aviation