Final NTSB investigations: Boeing 777-223
18 cases on aircraft the registry lists as Boeing 777-223. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 2000 | 3 |
|---|---|
| 2003 | 1 |
| 2004 | 1 |
| 2006 | 1 |
| 2007 | 1 |
| 2011 | 2 |
| 2014 | 1 |
| 2015 | 1 |
| 2018 | 1 |
| 2019 | 1 |
| 2021 | 1 |
| 2023 | 2 |
| 2024 | 2 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1385213'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1385213'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB DCA25LA047Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 777-223 · Brasilia, BrazilThe airplane’s encounter with unanticipated turbulence during cruise flight, which resulted in serious injury to one passenger who was not seated.NTSB DCA24LA254Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 777-223 · Linneus, MOAn inadvertent encounter with convectively induced turbulence during cruise.NTSB DCA23LA252Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 777-223 · Atlantic Ocean (Atlantic Ocean)An encounter with inadvertent convective turbulence during cruise flight.NTSB DCA23LA125Incident · No injuriesClass 1 · LimitedFinal reportBoeing 737-900ER · Queens, NYThe American Airlines flight 106 (AAL106) crew’s surface navigation error due to distractions caused by their performance of concurrent operational tasks during taxi, which resulted in a loss of situational awareness. Contributing to the incident was the air…NTSB DCA21LA095Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 777-223 · Fort Worth, TXan encounter with clear air turbulence during approachNTSB DCA19CA088Accident · Serious injuriesClass 4 · Data collectionFinal reportBoeing 777 · Honolulu, HIthe airplanes encounter with clear air turbulence.NTSB DCA18CA201Accident · Serious injuriesData collectionFinal reportBoeing 777 223 · Decatur, TXthe passengers failure to comply with the fasten seatbelt sign when the airplane encountered convective turbulence.NTSB DCA16CA050Accident · Serious injuriesData collectionFinal reportBoeing 777 223 · Buenos Aires, Argentinaan inadvertant encounter with convective turbulence.NTSB OPS14IA011Incident · No injuriesIncident investigationFinal reportBoeing 777 - 236 · Shemya, AKThe air traffic controller’s failure to identify a conflict between two aircraft and to issue an adequate clearance, which resulted in a loss of required separation. Contributing to the incident was the Federal Aviation Administration’s failure to provide…NTSB WPR11LA203Accident · Serious injuriesLimited investigationFinal reportBoeing 777-223 · Pacific OceanAn inadvertent encounter with convective-induced turbulence upon entering cumulonimbus clouds.NTSB OPS11IA246Incident · No injuriesIncident investigationFinal reportBoeing 777 · 80 SE of JFK (Atlantic Ocean), NYIncomplete and incorrect coordination between air traffic controllers that resulted in the 777 and the two C17s being cleared to maintain the same altitude. Contributing to the incident was the controllers’ non-adherence to established communications…NTSB CHI07LA078Accident · Serious injuriesLimited investigationFinal reportBoeing 777 · Chicago, ILAn in-flight encounter with turbulence during cruise flight.NTSB DFW06LA115Accident · Serious injuriesLimited investigationFinal reportBoeing 777-233ER · DFW Int'l Apt, TXThe in-flight encounter with turbulence in clouds resulting in a flight attendant being injured.NTSB DCA04MA061Accident · Serious injuriesMajor investigationFinal reportBoeing 777 · Miami, FLthe in-flight encounter with unforecasted clear air turbulence.NTSB MIA03LA067Accident · Serious injuriesLimited investigationFinal reportBoeing 777-223 · Miami, FLThe flight crew's inadvertent encounter with turbulence while attempting to maneuver through an area of convective activity during descent.NTSB MIA00LA271Accident · Serious injuriesLimited investigationFinal reportBoeing 777-223 · Miami, FLan in-flight encounter with turbulence.NTSB CHI00LA268Accident · Serious injuriesLimited investigationFinal reportBoeing 777-223 · Baraboo, WIthe unexpected turbulence encountered by the airplane.NTSB CHI00IA125Incident · No injuriesIncident investigationFinal reportBoeing 777-223ER · Chicago, ILthe flightcrew not detecting the runway closure NOTAM and the Air Traffic Control personnel on the metering, ground, and local positions giving an improper clearance to taxi to a closed runway. Factors were the closed runway, ATIS information not issued by…