Indonesian investigators released their final Lion Air flight 610 crash report this morning, finding that Boeing’s design of the Maneuvering Characteristics Augmentation System (MCAS), the FAA’s certification of the system, the airline’s maintenance of the aircraft, and the pilots’ actions during the flight all contributed to the crash.
Download a copy of the full report
Lion Air 610 ADS-B data
Flightradar24 data, including granular data from the flight may be found here.
JT610 Final Report
The report is divided into 5 sections—Factual information, Analysis, Conclusions, Safety action, and Safety recommendations. You can read the full report at the link above or by clicking on the image below. The Lion Air 610 crash report opens in PDF.
Boeing statement on final Lion Air flight 610 crash report
Boeing issued a statement on the final report saying, in part, ‘We are addressing the KNKT’s safety recommendations, and taking actions to enhance the safety of the 737 MAX to prevent the flight control conditions that occurred in this accident from ever happening again. Safety is an enduring value for everyone at Boeing and the safety of the flying public, our customers, and the crews aboard our airplanes is always our top priority. We value our long-standing partnership with Lion Air and we look forward to continuing to work together in the future.’
Over the past several months Boeing has been making changes to the 737 MAX. Most significantly, Boeing has redesigned the way Angle of Attack (AoA) sensors work with a feature of the flight control software known as Maneuvering Characteristics Augmentation System (MCAS). Going forward, MCAS will compare information from both AoA sensors before activating, adding a new layer of protection.
In addition, MCAS will now only turn on if both AoA sensors agree, will only activate once in response to erroneous AOA, and will always be subject to a maximum limit that can be overridden with the control column.
Featured image © Arvin Lienardi
![An example full flight summary response from the Flightradar24 API: { "data": [ { "fr24_id": "0987654321", "flight": "SK1415", "callsign": "SAS1415", "operated_as": "SAS", "painted_as": "SAS", "type": "A20N", "reg": "SE-DOY", "orig_icao": "ESSA", "orig_iata": "ARN", "datetime_takeoff": "2023-01-27T05:15:22", "runway_takeoff": "12R", "dest_icao": "EKCH", "dest_iata": "CPH", "dest_icao_actual": "EPWA", "dest_iata_actual": "WAW", "datetime_landed": "2023-01-27T06:15:10", "runway_landed": "27L", "flight_time": 3600, "actual_distance": 1007.74, "circle_distance": 6245, "category": "Passenger", "hex": "4A91F9", "first_seen": "2023-01-27T05:06:22", "last_seen": "2023-01-27T06:18:10", "flight_ended": "true" } ] }](https://www.flightradar24.com/blog/wp-content/uploads/2025/04/Flight-summary-API-cover-300x148.jpg)
![An example full flight summary response from the Flightradar24 API: { "data": [ { "fr24_id": "0987654321", "flight": "SK1415", "callsign": "SAS1415", "operated_as": "SAS", "painted_as": "SAS", "type": "A20N", "reg": "SE-DOY", "orig_icao": "ESSA", "orig_iata": "ARN", "datetime_takeoff": "2023-01-27T05:15:22", "runway_takeoff": "12R", "dest_icao": "EKCH", "dest_iata": "CPH", "dest_icao_actual": "EPWA", "dest_iata_actual": "WAW", "datetime_landed": "2023-01-27T06:15:10", "runway_landed": "27L", "flight_time": 3600, "actual_distance": 1007.74, "circle_distance": 6245, "category": "Passenger", "hex": "4A91F9", "first_seen": "2023-01-27T05:06:22", "last_seen": "2023-01-27T06:18:10", "flight_ended": "true" } ] }](https://www.flightradar24.com/blog/wp-content/uploads/2025/04/Flight-summary-API-cover-768x378.jpg)
