NTSB investigations: Boeing 737-524
8 cases on aircraft the registry lists as Boeing 737-524. 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
| 1995 | 1 |
|---|---|
| 1997 | 1 |
| 1998 | 1 |
| 2005 | 1 |
| 2006 | 2 |
| 2008 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1384721'))
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 ('1384721'))
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 DCA09MA021Accident · Serious injuriesClass 1 · MajorFinal reportBoeing 737-524 · Denver, COThe captain’s cessation of right rudder input, which was needed to maintain directional control of the airplane, about 4 seconds before the excursion, when the airplane encountered a strong and gusty crosswind that exceeded the captain’s training and…NTSB DFW08IA087Incident · No injuriesIncident investigationFinal reportBoeing 737-524 · Houston, TXThe flight crew's improper landing technique for an inoperative anti-skid system resulting in locked brakes and four blown main landing gear tires.NTSB NYC06IA207Incident · No injuriesIncident investigationFinal reportBoeing 737-524 · Newark, NJAn overload failure of the airplane's nose landing gear while being towed for repositioning.NTSB DFW06FA056Accident · 1 fatalField investigationFinal reportBoeing 737-524 · El Paso, TXthe mechanic's failure to maintain proper clearance with the engine intake during a jet engine run, and the failure of contract maintenance personnel to follow written procedures and directives contained in the airline's general maintenance manual. Factors…NTSB DEN05IA098Incident · No injuriesIncident investigationFinal reportBoeing 737-524 · Salt Lake City, UTthe left wing walker's failure to maintain an adequate visual lookout. Contributing factors were his inadequate initial training, and the failure of other ground personnel to follow company procedures/directives.NTSB FTW98RA401Accident · No injuriesForeign investigationBoeing 737-524 · Guadalajara, MexicoNTSB FTW97IA187Incident · No injuriesIncident investigationFinal reportBoeing 737-524 · Corpus Christi, TXThe flightcrew's inadequate in-flight planning and decision, and their failure to refer to the navaids needed for the instrument approach procedure. A factor was the lack of a minimum safe altitude warning from approach control.NTSB NYC95IA114Incident · No injuriesIncident investigationFinal reportBoeing 767-383ER · Newark, NJthe pilot of the B-767, LNRCK, misjudged clearance between his airplane and the B-737, N13624, resulting in an on-ground collision.