NTSB investigations: Boeing 737-522
11 cases on aircraft the registry lists as Boeing 737-522. 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
| 1993 | 1 |
|---|---|
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 3 |
| 2001 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2007 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('138449F'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('138449F'))
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 DEN07IA058Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Denver, COThe snowplow driver's failure to follow procedures/directives by crossing an active runway without clearance, resulting in a runway incursion and near collision with an airplane during its landing roll.NTSB DEN04IA124Incident · No injuriesIncident investigationFinal reportBoeing 737-500 · Denver, COthe inaccurate radar information due to the failure of the Airport Movement Area Surveillance radar resulting in the tower calling for the airplane to abort the takeoff, subsequently causing tire and brake damage to the airplane.NTSB DEN04LA019Accident · Serious injuriesLimited investigationFinal reportBoeing 737-500 · Denver, COthe in-flight encounter with heavy to moderate turbulence.NTSB CHI02IA058Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Chicago, ILThe wake turbulence encounter.NTSB SEA98IA027Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Eugene, ORA checklist procedure was not followed. The initiation of an evacuation was a factor.NTSB LAX97IA243Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Ontario, CAa laser light source of undetermined origin directed toward the cockpit window of an aircraft in-flight by a person or persons unknown.NTSB LAX97IA161Incident · Minor injuriesIncident investigationFinal reportBoeing 737-500 · Rialto, CAa laser light source of undetermined origin, directed by unknown person(s) toward the cockpit window of the aircraft, while the aircraft was on an approach to land.NTSB LAX97LA051Accident · Serious injuriesLimited investigationFinal reportBoeing 737-500 · Bishop, CAa clear air turbulence encounter.NTSB SEA96LA026Accident · Serious injuriesLimited investigationFinal reportBoeing 737-522 · Portland, ORAn unexpected encounter with unforecast moderate high level windshear and turbulence as the flight attendant was performing his duties during descent.NTSB DCA96IA005Incident · No injuriesIncident investigationFinal reportBoeing B-737-500 · San Francisco, CAThe inadvertant stall for undertermined reasons.NTSB DEN93IA044Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Denver, COThe pilot-in-command's failure to maintain adequate separation from the Boeing 757, and his failure to stay above the probable path of the Boeing's wake vortices, which resulted in the vortex encounter. Factors related to the accident were: the crosswind, and…