Raw LLM Responses
Inspect the exact model output for any coded comment.
Look up by comment ID
Random samples — click to inspect
G
And what are they going to do about it? Where is the solution? If Ai curupt the …
ytc_UgwnzzdYE…
G
I can't help but notice that all of the signatories are prime candidates to have…
ytc_Ugy7JuybN…
G
but.. sora is for hyper realistic videos.. how does this impact digital art in a…
ytc_UgwxQZ6Dy…
G
robots don't deserve rights in a million fucking years. research on sentient AI …
ytc_UgiPeApql…
G
The problem with the logic of most AI content stealers (lets call them out for w…
ytc_UgzqDkey3…
G
But the thing is, AI doesn't even need to be intelligent or self aware like huma…
ytc_UgzXvz05H…
G
The last thing I saw was artificial intelligence in an automated cat litter box …
ytc_Ugwui1ekJ…
G
They are all going to lose their job, this strike is only going to push companie…
ytc_UgwccPvZM…
Comment
To understand the global track record of the Boeing 737 MAX 8, one must look at a history divided into two distinct eras: the initial design failure that led to two major tragedies and the subsequent period of intense regulatory overhaul and return to service.
As of April 2026, here is the deep dive into the fatal incidents and safety record of the MAX 8.
1. The Core Fatal Incidents
The 737 MAX 8 was involved in two catastrophic accidents within five months of each other, claiming a total of 346 lives. Both were linked to the same technical and systemic failure.
Flight Date Location Fatalities
Lion Air 610 Oct 29, 2018 Java Sea, Indonesia 189
Ethiopian 302 Mar 10, 2019 Ejere, Ethiopia 157
The Technical Failure: MCAS
The Maneuvering Characteristics Augmentation System (MCAS) was designed to make the MAX 8 feel like the older 737 NG to pilots. Because the larger LEAP-1B engines changed the plane's aerodynamics, MCAS would automatically push the nose down if it sensed the plane was pitching up too steeply (stalling).
The Single Point of Failure: Boeing designed MCAS to rely on data from only one Angle-of-Attack (AOA) sensor. If that sensor failed, the software would repeatedly force the nose down, overpowering the pilots.
The "Hidden" System: At the time of these crashes, MCAS was not included in the pilot flight manuals, meaning crews were unaware the system even existed or how to disable it under pressure.
----------------------------------------------------------------------------------
Lion Air Flight 610 Crash – Key Findings (KNKT Report, Oct 25, 2019)
Indonesia’s Komite Nasional Keselamatan Transportasi (KNKT) concluded the crash was caused by a chain of events, not a single failure.
They identified 9 contributing factors—removing any one of them might have prevented the accident.
9 Key Contributing Factors
MCAS Design Flaw
Relied on a single Angle-of-Attack (AOA) sensor → single point of failure.
Unrealistic Pilot Assumptions
Certification assumed pilots would respond quickly; real-world confusion was underestimated.
Lack of Pilot Awareness
MCAS was not included in manuals → pilots didn’t know it existed.
Faulty Sensor Installation
Replacement AOA sensor was miscalibrated by a U.S. repair facility.
Maintenance Failure
Lion Air crews did not detect the sensor error during testing.
Inactive Warning System
“AOA Disagree” alert was not functioning due to a software issue.
Incomplete Logbook Records
Previous flight issues were not properly documented → no warning for next crew.
Cockpit Overload
Multiple alarms + ATC communication overwhelmed the pilots.
Poor Crew Coordination (CRM)
Captain and First Officer struggled to manage the emergency together.
Bottom Line
The crash resulted from combined failures in aircraft design, regulation, maintenance, and human factors—not a single cause.
---------------------------------------------------------------------------------
The final report for Ethiopian Airlines Flight 302 was released by the Ethiopian Aircraft Accident Investigation Bureau (EAIB) on December 23, 2022.
While the Lion Air investigation (KNKT) focused on a "chain of events" including maintenance and pilot response, the EAIB report was significantly more pointed, placing the primary responsibility almost exclusively on Boeing’s aircraft design and certification.
1. Probable Cause
The EAIB concluded that the most probable cause of the accident was the "repetitive and uncommanded airplane-nose-down inputs from the MCAS."
System Failure: The report stated that the MCAS was triggered by erroneous data from a single Angle-of-Attack (AOA) sensor.
Unrecoverable Dive: The system's design allowed it to activate multiple times, eventually pushing the aircraft into a dive that became physically impossible for the pilots to recover from as the airspeed increased.
Terminal Velocity: The aircraft impacted the ground at nearly 700 mph (610 knots), with a descent rate of over 33,000 feet per minute.
2. Primary Conclusions regarding Boeing & FAA
The EAIB report highlighted several critical failures at the manufacturing and regulatory levels:
Single Point of Failure: The EAIB heavily criticized the design for relying on a single AOA sensor without any redundancy or cross-checking mechanism.
Inadequate Training Materials: The report found that the documentation provided by Boeing was insufficient. Even though a "bulletin" had been issued after the Lion Air crash, the EAIB argued it did not provide pilots with enough technical understanding of how to manage a persistent MCAS failure.
Certification Gaps: The report concluded that the FAA's certification process was flawed because it did not adequately evaluate the "hazard level" of an MCAS malfunction.
youtube
AI Jobs
2026-04-05T16:0…
Coding Result
| Dimension | Value |
|---|---|
| Responsibility | unclear |
| Reasoning | unclear |
| Policy | unclear |
| Emotion | unclear |
| Coded at | 2026-04-26T23:09:12.988011 |
Raw LLM Response
[{"id":"ytc_UgyvU2AQMihY6iTjdhF4AaABAg","responsibility":"none","reasoning":"mixed","policy":"none","emotion":"indifference"},{"id":"ytc_UgzyhkJb6lpSrLOdCD14AaABAg","responsibility":"none","reasoning":"consequentialist","policy":"none","emotion":"indifference"},{"id":"ytc_UgxX4TTMZL6faY_sX6x4AaABAg","responsibility":"none","reasoning":"mixed","policy":"none","emotion":"approval"},{"id":"ytc_UgwNEEmoTUp3du8W9Xx4AaABAg","responsibility":"unclear","reasoning":"unclear","policy":"unclear","emotion":"unclear"},{"id":"ytc_UgxMBCZpj2jnAT55Yr54AaABAg","responsibility":"none","reasoning":"consequentialist","policy":"none","emotion":"fear"},{"id":"ytc_UgzaJcP6c9qL-1ljBCl4AaABAg","responsibility":"none","reasoning":"deontological","policy":"none","emotion":"outrage"},{"id":"ytc_Ugy2Pks_HSm950sBx8d4AaABAg","responsibility":"ai_itself","reasoning":"consequentialist","policy":"ban","emotion":"outrage"},{"id":"ytc_UgzrNPEs1arFg7MgkNN4AaABAg","responsibility":"distributed","reasoning":"deontological","policy":"regulate","emotion":"mixed"},{"id":"ytc_UgyFGfgHVtA_a4TyAUZ4AaABAg","responsibility":"none","reasoning":"mixed","policy":"none","emotion":"resignation"},{"id":"ytc_UgxzmHqc51jqoQGvo6V4AaABAg","responsibility":"none","reasoning":"consequentialist","policy":"none","emotion":"indifference"}]