NTSB Investigation Findings – What Went Wrong?
The National Transportation Safety Board (NTSB) launched a thorough investigation to determine how a routine flight could lead to such a massive structural failure. Very quickly, evidence pointed to metal fatigue in the aircraft’s aluminum skin as the culprit, aggravated by years of operation in a corrosive, coastal environment (Hawaii’s salt air and humidity). The Boeing 737 involved was 19 years old and had accumulated 89,680 flight cycles (takeoff and landing pressurization cycles) – at the time, the second-highest number of cycles on any 737 in the world. This was over twice the number of flights the airframe was originally designed for. The NTSB determined that the structural failure initiated at a critical fuselage lap joint (identified as stringer S-10L) along the upper row of rivets. The skin panels in this area were joined with a longitudinal riveted splice that, in early 737 models, had been cold-bonded with epoxy and then riveted – a design meant to be “fail-safe” with built-in crack-arresting features called tear straps. However, over time the bond between the lap joint layers disbonded due to moisture ingress and corrosion, and multiple small fatigue cracks (so-called multiple-site fatigue cracking) had been propagating unseen around the rivet holes.
According to the NTSB, these numerous tiny cracks linked up and overcame the remaining strength of the joint, causing a sudden, explosive fracture of the fuselage skin. The tear straps that should have halted a crack were rendered ineffective because the bonding had failed – essentially negating the intended fail-safe design. Laboratory analysis of the torn metal showed the classic telltale signs of fatigue: striations indicating crack growth over time with each pressurization cycle, and evidence of crevice corrosion in the joint which accelerated the crack growth. The official NTSB probable cause explicitly stated that “the failure of the Aloha Airlines maintenance program to detect the presence of significant disbonding and fatigue damage” in the lap joint led to the accident. In other words, the cracks and corrosion were there, but went unnoticed until it was too late.
Equally significant were the contributing factors identified. The NTSB faulted Aloha Airlines’ management for inadequate oversight of maintenance personnel, and also pointed to regulatory and manufacturer issues. Specifically, a Boeing Alert Service Bulletin (SB 737-53A1039) had been issued prior to the accident to inspect certain lap joints for cracks, and the FAA had released an Airworthiness Directive (AD 87-21-08) requiring inspections – but due to a narrow scope, not all the joints (including the one that failed) were mandated to be inspected. Aloha Airlines’ maintenance team did not conduct a thorough inspection of the accident joint, and the FAA’s oversight did not catch this gap. Furthermore, it was revealed that inspection procedures and training were inadequate. Routine structural inspections (such as detailed visual checks of the fuselage skin) were often scheduled at night in poorly lit conditions, making it difficult to spot fine cracks. The NTSB found that across Aloha’s heavy maintenance checks, no significant structural issues were ever reported, which strained credulity given what was later found in the fleet. In fact, when investigators examined Aloha’s other 737s after the accident, they found “considerable evidence of corrosion… [and] bulging of the skin (pillowing)” on multiple aircraft. It appeared that the airline’s maintenance culture had accepted a deteriorated condition as normal. Many of Aloha’s inspectors had minimal formal training (sometimes as little as 2 hours) and no training in non-destructive inspection techniques to find fatigue cracks. This lack of expertise meant that even dedicated workers could not recognize the impending danger; as one analysis noted, “there was no one at the company capable of understanding the general condition of the airplanes… the deterioration’s very ubiquity made it seem normal.”
The NTSB ultimately concluded that Flight 243’s accident resulted from a systemic breakdown in safety oversight: aging aircraft issues that were known but not adequately addressed by the airline, insufficient regulatory enforcement to ensure the known issues were fixed, and a maintenance program that did not evolve to catch age-related fatigue damage. One NTSB board member dissented only to emphasize that this was not just a single airline’s failure but an industry wake-up call – indeed, the accident spurred industry-wide changes. In the immediate aftermath, the U.S. Congress passed the Aviation Safety Research Act of 1988, which strengthened the FAA’s oversight of aging aircraft and mandated research into better inspection techniques. The FAA launched the National Aging Aircraft Program, and both Boeing and the FAA issued new directives to inspect and modify aircraft that had high usage. Aloha 243 thus became a watershed event, exposing the hidden dangers of metal fatigue in pressurized aircraft, and forcing regulators and airlines worldwide to re-examine maintenance practices for older planes.
Human Factors Lessons Learned: Communication, Compliance, Culture, and Fatigue
Beyond the metallurgical causes, the Aloha Flight 243 accident underscored vital human factors lessons that resonate in aviation maintenance and operations:
Communication Breakdowns: Both in-flight and on the ground, communication proved critical. In the air, the cockpit crew and flight attendants struggled to communicate due to physical noise barriers, yet their persistence and use of non-verbal cues allowed them to coordinate the emergency landingOn the maintenance side, there were communication lapses in conveying known issues – for instance, Boeing had communicated potential lap joint problems via service bulletins, but those warnings were not fully acted upon by the maintenance organization. Effective communication means not only clear radio calls in a crisis, but also a culture where vital safety information (like inspection findings or manufacturer’s advisories) is passed on and acted upon promptly. After the accident, it became clear that better communication channels were needed between manufacturers, regulators, and airlines to ensure safety critical information (like signs of widespread fatigue) never gets lost in the shuffle.
Procedural Compliance & Training: Flight 243 highlighted what can happen when standard procedures and training do not keep pace with operational reality. The maintenance staff, in hindsight, did not follow rigorous procedures for detailed inspections – possibly because they were not trained or the airline didn’t enforce them. For example, the airline’s policy did not even require visual inspections between short island hops on the same day. The NTSB found that many concerned mechanics and inspectors lacked formal training in detecting fatigue cracks and corrosion. This is a stark reminder that training programs must be thorough and ongoing, especially as an aircraft ages. Every technician and inspector should understand and comply with inspection protocols, and know how to use advanced tools (like eddy current or ultrasonic testers) when visual exams aren’t enough. Strict adherence to maintenance manuals, service bulletins, and airworthiness directives is non-negotiable – and management must support a culture where doing things “by the book” is the norm. In short, procedural compliance saves lives, and that compliance is only possible when personnel are properly trained and regularly refreshed on the latest standards.
Organizational Safety Culture: The corporate culture prior to the accident was scrutinized heavily. The picture that emerged was an airline trying to maximize aircraft utilization (quick turnarounds between island hops) while not fully investing in the long-term upkeep of its aging fleet. There was a sense of complacency – the aircraft had never had a serious issue before, so critical structural inspections may have been treated as a formality. The fact that no significant findings ever came out of their heavy maintenance checks, and that even obvious signs of skin deformation (like pillowing) went unaddressed, indicates a weak safety culture. Safety culture refers to the mindset that safety is everyone’s responsibility and that no concern is too minor to report. In a strong safety culture, if a mechanic is unsure about a possible crack, they will feel empowered to ask for a second look or a more sensitive inspection, rather than sweeping it under the rug. After Flight 243, many airlines implemented safety culture improvements – encouraging open reporting of potential problems (via programs like Aviation Safety Action Programs) and ensuring management listens to engineers’ concerns. Organizational leadership must set the tone that safety comes first, even if it means extra costs or downtime. As an industry, this accident reinforced the idea that a proactive safety culture could have caught the fatigue damage early and prevented the accident.
Fatigue Detection (Metal & Human): The term “fatigue” played a dual role in this accident – referring to both metal fatigue in the aircraft and potentially human fatigue in those tasked with finding it. The maintenance inspections were often done on night shifts after long days, which likely meant inspectors were tired and working in suboptimal lighting. Human fatigue can lead to oversight and errors – a drowsy mechanic is far less likely to notice a tiny hairline crack in a dimly lit hangar at 2 AM. This is a human factors issue that airlines must address by managing work/rest schedules, providing adequate lighting and time for inspections, and perhaps rotating critical inspection tasks to ensure a “fresh pair of eyes” is always looking. As for fatigue detection in metals, the lesson is that relying on basic visual inspection alone is not enough – especially as aircraft age. The use of Non-Destructive Testing (NDT) techniques (discussed later) and the development of better inspection programs for aging aircraft became a direct outcome of this event. Essentially, the industry learned that it needed to detect metal fatigue before it propagated – which means investing in technology and training to find those invisible cracks, as well as recognizing the limits of human visual inspection. By also caring for the human factor of inspector fatigue, the likelihood of catching problems increases. Post-accident, many operators began scheduling critical structural inspections during day shifts or with additional time/resources, and regulators increased requirements for periodic “aging aircraft” structural checks that involve enhanced inspection methods.
Each of these human factors lessons – communication, compliance, culture, and fatigue management – are deeply interrelated. The Aloha 243 incident became a case study in how latent human factors issues (like complacency or poor communication of safety information) can accumulate and contribute to a disaster. Modern safety management systems (SMS) in aviation explicitly address these by promoting reporting, ensuring training and procedural adherence, monitoring human performance, and building a strong safety culture. The legacy of Flight 243 is not only in the engineering fixes that followed, but in the improved awareness of human factors at all organizational levels.
Related Articles:
- Article 1: Aloha Flight 243 – A Mid-Air Crisis and Heroic Response
- Article 3: The Science of Metal Fatigue – Aircraft Structures and Maintenance Best Practices
- Article 4: Evolution of Aircraft Maintenance Programs Post-Aloha: WFD, DTE, and Regulatory Changes
- Article 5: Aloha Flight 243 From Lessons to Actions - Training, Inspection, and Aviation Safety Evolution
Aviathrust's Safety, Human Factors and Aircraft Structure Maintenance Training
Our training courses below are intended to support an aviation organization get a grasp of how to build, strengthen and implement a healthy SMS in compliance with ICAO's Annex 19 Appendix 2 and EASA Regulations. Do not hesitate to contact us for further information.
