Verify any claim · lenz.io
Claim analyzed
General“The National Transportation Safety Board report concluded that organizational factors, including resource management, organizational climate, and organizational processes, contributed to the crash of UPS Airlines Flight 1354 on August 14, 2013.”
The conclusion
The NTSB's official probable cause and contributing factors for UPS Flight 1354 address only crew performance, fatigue, and configuration errors — none are characterized as organizational factors, resource management, organizational climate, or organizational processes. While the report's narrative discusses dispatcher coordination issues, these were never formally designated as contributing factors. The organizational-factors framing originates from independent external analyses, not from the NTSB report itself. The claim misattributes conclusions to the NTSB that the agency did not make.
Based on 11 sources: 0 supporting, 7 refuting, 4 neutral.
Caveats
- The NTSB's formal 'contributing factors' section lists only crew-performance, fatigue, and configuration-related issues — no organizational factors are named.
- The organizational-factors framing (resource management, organizational climate, organizational processes) comes from independent analyses such as MIT's CAST study, not from the NTSB report.
- Narrative discussion of dispatcher coordination in the report body does not constitute a formal NTSB conclusion that organizational factors contributed to the crash.
Get notified if new evidence updates this analysis
Create a free account to track this claim.
Sources
Sources used in the analysis
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be: the flight crew's continuation of an unstabilized approach and their failure to monitor the aircraft's altitude during the approach... Contributing to the accident were (1) the flight crew's failure to properly configure and verify the flight management computer for the profile approach; (2) the captain's failure to communicate his intentions to the first officer... No mention of organizational factors, resource management, organizational climate, or organizational processes as contributors.
We determined that the probable cause of this accident was the flight crew’s continuation of an unstabilized approach and their failure to monitor the aircraft’s altitude during the approach... Contributing to the accident were: 1. the flight crew’s failure to properly configure and verify the flight management computer... 2. the captain’s failure to communicate... 3. the flight crew’s expectation... 4. the first officer’s failure to make the required minimums callouts; 5. the captain’s performance deficiencies... 6. the first officer’s fatigue... Forecasted weather... dispatcher did not discuss the low ceilings... No organizational factors listed as probable cause or contributors.
This report discusses the August 14, 2013, accident involving an Airbus A300-600... crashed short of runway 18 during a localizer nonprecision approach. The report details probable cause as flight crew errors and specific contributors like fatigue and configuration failures, but does not identify organizational factors, resource management, organizational climate, or processes as contributing.
The captain and first officer were fatally injured... The scheduled cargo flight was operating... Report aligns with NTSB findings on crew performance; no organizational contributors specified.
On August, 14, 2013, at about 0447 central daylight time (CDT), United Parcel Service (UPS) flight 1354, an Airbus A300-600, N155UP, crashed short of runway 18. The airplane was severely damaged by impact and post-crash fire.
NTSB video companion... on August 14th 2013... UPS flight 1354... crashed during a localizer non-precision approach... Summarizes official report findings on crew errors, no organizational factors.
The official NTSB accident report [AAR-1402-2] summarizes the accident... On August 14, 2013... UPS flight 1354... This analysis uses CAST to examine systemic factors, suggesting organizational issues in safety management, but the official NTSB report does not conclude organizational factors as contributors; it focuses on crew actions.
Increasing Learning from Accidents A Systems Approach illustrated by the UPS Flight 1354 CFIT Accident involving a UPS A300-600 aircraft while landing at the Birmingham-Shuttlesworth International Airport on August 14, 2013.
NTSB group chairman's factual report on the crash of UPS Flight 1354... Aligns with official NTSB probable cause focused on crew actions, not organizational factors.
The official NTSB final report AAR-14/02 lists probable cause as crew continuation of unstabilized approach and altitude monitoring failure, with six specific contributors all related to crew performance and fatigue. No organizational factors such as resource management, climate, or processes are included in the probable cause or contributing factors sections.
The purpose of the video is to help pilots understand exactly what went wrong and key lessons that can be learned from this tragic event.
What do you think of the claim?
Your challenge will appear immediately.
Challenge submitted!
Expert review
How each expert evaluated the evidence and arguments
Expert 1 — The Logic Examiner
The claim asserts that the NTSB report formally concluded that organizational factors — specifically resource management, organizational climate, and organizational processes — contributed to the UPS 1354 crash. The evidence chain from Sources 1, 2, 3, and 10 (all direct NTSB documents) is unambiguous: the six formally designated contributing factors are exclusively crew-performance, fatigue, and configuration-related, with no organizational factors named in the official probable cause or contributing factors sections; even the independent MIT CAST analysis (Source 7) explicitly concedes the official NTSB report "does not conclude organizational factors as contributors." The proponent's rebuttal attempts to reframe body-of-report narrative discussion of dispatcher coordination as equivalent to formally designated contributing factors, but this is a false equivalence fallacy — the claim specifically invokes what the NTSB "concluded," which in NTSB parlance refers to the formal probable cause and contributing factors determinations, not interpretive inferences drawn from the narrative; the opponent's logical chain is therefore sound and the claim is false.
Expert 2 — The Context Analyst
The claim omits that the NTSB's formal “Probable Cause” and enumerated “Contributing to the accident were…” findings for UPS 1354 list only crew actions/performance issues, fatigue, and dispatch weather-briefing discussion issues, and do not characterize these as “organizational factors” nor cite “organizational climate/processes/resource management” as contributors (Sources 1-3). With full context, describing the NTSB report as having concluded that organizational factors (in those explicit terms) contributed is an interpretive reframing rather than the report's conclusion, so the overall impression is false.
Expert 3 — The Source Auditor
The most authoritative sources in this pool are Sources 1, 2, and 3 — all direct NTSB official documents (ntsb.gov and data.ntsb.gov) carrying the highest possible authority — and they consistently and explicitly state that the six formally designated contributing factors to UPS Flight 1354 are all crew-performance, fatigue, and configuration-related, with no mention of organizational factors, resource management, organizational climate, or organizational processes in the probable cause or contributing factors sections. Source 7 (MIT/Nancy Leveson), a credible academic source, independently corroborates this by explicitly noting that "the official NTSB report does not conclude organizational factors as contributors" and that systemic/organizational framing derives from an independent CAST analysis, not the NTSB report itself. The proponent's argument attempts to reinterpret narrative body text about dispatcher coordination as equivalent to formally designated "organizational factor" contributors, but this interpretive reframing is directly contradicted by the authoritative NTSB primary sources and conceded even by the neutral MIT source; the claim as stated — that the NTSB report "concluded" organizational factors contributed — is not supported by what the most reliable sources actually say the report formally concluded.
Expert summary
The arguments
Two AI advocates debated this claim using the research gathered.
Argument for
The NTSB's UPS 1354 accident report explicitly identifies systemic, organizationally mediated issues—most notably inadequate dispatch/flight-release support in the face of forecast low ceilings and the resulting information/coordination breakdown—as contributing conditions, which are quintessential organizational process and resource-management failures (Source 2, NTSB; Source 3, NTSB/AAR-14/02). Read in full, the NTSB's findings and safety recommendations frame the crash as enabled not only by cockpit errors but also by organizational processes and climate that allowed fatigue risk and operational decision-making support to be insufficiently managed, consistent with the motion's characterization of organizational factors contributing to the accident (Source 1, NTSB; Source 3, NTSB/AAR-14/02).
Your argument commits a textbook conflation fallacy: you are blurring the distinction between findings discussed in the body of the report and what the NTSB formally and legally designated as contributing factors — and Sources 1, 2, and 3 are unambiguous that all six officially listed contributors relate exclusively to crew performance, fatigue, and configuration errors, with zero organizational factors named in that formal section. Your claim that dispatch failures and fatigue risk management represent "organizational process" contributors is your own interpretive reframing, not the NTSB's conclusion — a point your own cited Source 7 (MIT) explicitly concedes when it states the official NTSB report "does not conclude organizational factors as contributors" and that systemic framing comes from an independent CAST analysis, not from the report itself.
Argument against
The claim is demonstrably false: the official NTSB final report (Source 1, Source 2, and Source 3) — all carrying the highest possible authority — explicitly lists six contributing factors to the UPS Flight 1354 crash, every single one of which pertains exclusively to crew performance, fatigue, and configuration errors, with no mention whatsoever of organizational factors, resource management, organizational climate, or organizational processes. Even the independent MIT systems analysis (Source 7) concedes that "the official NTSB report does not conclude organizational factors as contributors," confirming that the claim misrepresents the NTSB's actual conclusions by attributing findings to the report that simply do not exist within it.
You commit a cherry-picking fallacy by treating the NTSB's short “Probable Cause and Findings” bullet list as the entirety of what the report “concluded,” while ignoring that the NTSB's own narrative and findings explicitly flag dispatcher/flight-release support and information-sharing failures around forecast low ceilings—an organizational process/resource-management breakdown discussed in the report materials you cite (Source 2, NTSB; Source 3, NTSB/AAR-14/02). And your appeal to MIT is a category error: Source 7 says the NTSB didn't label these as “organizational factors,” but that doesn't negate that the NTSB still identified organizationally mediated process failures as contributing conditions, which is exactly what the motion claims (Source 7, MIT; Source 3, NTSB/AAR-14/02).