Final NTSB investigations: Boeing 777-222
15 cases on aircraft the registry lists as Boeing 777-222. 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
| 1999 | 1 |
|---|---|
| 2003 | 2 |
| 2006 | 1 |
| 2007 | 2 |
| 2009 | 1 |
| 2010 | 2 |
| 2018 | 1 |
| 2021 | 1 |
| 2022 | 1 |
| 2023 | 2 |
| 2024 | 1 |
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 ('1385219'))
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 ('1385219'))
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 DCA24LA097Accident · Serious injuriesClass 3 · LimitedFinal reportBoeing 777-222ER · Kelsey, NYThe airplane’s encounter with an unanticipated localized region of moderate-to-severe turbulence while in instrument meteorological conditions (IMC) associated with strong upper-level wind shear and convective cells. Contributing to the severity of the…NTSB DCA23LA421Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 777-222 · Over the (Atlantic Ocean)An inadvertent encounter with clear air turbulence during cruise flight.NTSB DCA23LA133Incident · No injuriesClass 3 · LimitedFinal reportBoeing 777-222 · Honolulu, HIThe airport’s continued use of taxiway Kilo, despite an identified risk of pilots repeatedly failing to stop at a hold short line prior to two intersecting runways. Contributing were 1) the operator’s moving map display, which omitted a published restriction…NTSB DCA23LA172Incident · No injuriesClass 4 · LimitedFinal reportBoeing 777 · Kahului, HIThe flight crew’s failure to manage the airplane’s vertical flightpath, airspeed, and pitch attitude following a miscommunication about the captain’s desired flap setting during the initial climb.NTSB DCA21FA085Incident · No injuriesClass 3 · FieldFinal reportBoeing 777-222 · Broomfield, COThe fatigue failure of the right engine fan blade. Contributing to the fan blade failure was the inadequate inspection of the blades, which failed to identify low-level indications of cracking, and the insufficient frequency of the manufacturer’s inspection…NTSB DCA18IA092Incident · No injuriesIncident investigationFinal reportBoeing 777 222 · Honolulu, HIthe fracture of a fan blade due to P&W's continued classification of the TAI inspection process as a new and emerging technology that permitted them to continue accomplishing the inspection without having to develop a formal, defined initial and recurrent…NTSB DCA10FA064Accident · Serious injuriesField investigationFinal reportBoeing 777 · Southern Tip of Greenland, DenmarkAn inadvertent encounter with unforecast turbulence in cruise flight.NTSB OPS10IA020Incident · No injuriesIncident investigationFinal reportBoeing 777-222 · San Francisco, CAThe local controller's issuance of a takeoff clearance to the Boeing 777 without ensuring that approved separation would exist with the Cessna 182. Contributing to the incident were tower procedures that permitted transitioning aircraft to cross the runway 28…NTSB DCA10FA012Accident · Serious injuriesField investigationFinal reportBoeing 777-200 · New Market, VAThe flight crew’s inadvertent encounter with a small area of cumulous clouds at night that resulted in moderate to severe convectively induced turbulence.NTSB CHI08FA050Accident · Serious injuriesField investigationFinal reportBoeing 777-222 · Chicago, ILEmergency evacuation due to dense smoke in the cabin and the possibility of an on-board fire, which resulted in a serious injury to one of the 264 passengers and crew. An additional cause was the failure of an engine bearing, allowing oil to migrate into the…NTSB CHI07FA184Accident · No injuriesField investigationFinal reportBoeing 777-222 · Chicago, ILThe 777-222's flight crew not maintaining clearance from the parked/standing MD 83 and the airport not coordinating the taxi chart instructions with air traffic control. Contributing to the accident was the MD 83's flight crew not following the taxi chart…NTSB DEN06IA034Incident · No injuriesIncident investigationFinal reportBoeing B777-200B · Denver, COthe truck driver's failure to maintain clearance from the airplane and the boom operator's failure to adequately clear the boom from the airplane. Contributing to the accident was the low visibility due to snow and mist.NTSB LAX04LA007Accident · No injuriesLimited investigationFinal reportBoeing 777-22B · San Francisco, CAthe failure of the taxiing Boeing 777's flight crew to maintain clearance from a Boeing 777 that was being pushed back from the gate. Contributing to the accident was the failure of the local ramp controller to caution either aircrew of a possible movement…NTSB CHI03LA237Accident · Serious injuriesLimited investigationFinal reportBoeing B777-222 · Chicago, ILThe turbulence encountered during the descent which seriously injured a passenger returning to her seat after the seat belt sign was activated. A factor was that it was not possible for the returning passenger to comply with the lit seat belt sign.NTSB CHI99LA184Accident · Serious injuriesLimited investigationFinal reportBoeing 777-222 · Madison, WIthe pilot-in-command's inadequate evaluation of the weather conditions. Factors associated with the accident were the turbulence encountered and the seat belt sign was not illuminated.