Final NTSB investigations: Boeing 757-224
7 cases on aircraft the registry lists as Boeing 757-224. 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
| 2006 | 1 |
|---|---|
| 2018 | 1 |
| 2019 | 1 |
| 2021 | 1 |
| 2023 | 1 |
| 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 ('1384958'))
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 ('1384958'))
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 DCA24LA316Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 757-224 · Dunnigan, CAThe abrupt pitch control input by the flight crew in response to a TCAS resolution advisory resulted in two serious passenger injuries.NTSB DCA24LA110Accident · No injuriesClass 4 · LimitedFinal reportBoeing 757-224 · San Francisco, CAThe crew’s over-rotation of the aircraft pitch during takeoff which resulted in a tailstrike.NTSB DCA23LA477Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 757 · Lake Butler, FLAn inadvertent encounter with convectively induced turbulence.NTSB DCA22LA002Accident · No injuriesClass 4 · LimitedFinal reportBoeing 757-224 · Newark, NJThe nose high attitude on landing resulted in a tailstrike.NTSB DCA19CA167Accident · No injuriesClass 4 · Data collectionFinal reportBoeing 757 · Newark, NJan improper landing flare, which resulted in a bounced landing and substantial damage.NTSB DCA18CA299Accident · Serious injuriesData collectionFinal reportBoeing 757 · Newark, NJthe catering cart striking the flight attendant's foot.NTSB NYC07IA015Incident · No injuriesIncident investigationFinal reportBoeing 757-224 · Newark, NJThe flight crew's misidentification of the parallel taxiway as the active runway, resulting in the flight crew executing a landing on the taxiway. Contributing was the night lighting conditions.