Boeing 737-322
NTSB investigations · 16
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('138447Y')
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('138447Y')
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 CHI07FA020Accident · No injuriesField investigationFinal reportBoeing 737-300 · Chicago, ILThe pilot-in-command of the other airplane failed to maintain clearance with the parked airplane during taxi for takeoff.NTSB OPS06IA008Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Chicago, ILThe failure of the ORD tower south local controller to monitor Atlas Air flight 6972 on arrival to runway 14R and subsequently clearing United Airlines flight 1015 for takeoff on intersecting runway 27L causing a loss of separation between the two aircraft.NTSB CHI06LA161Accident · No injuriesLimited investigationFinal reportBoeing 737-300 · New York, NYThe foreign object damage to the horizontal stabilizer during taxi as a result of improper airport maintenance by contract maintenance personnel. The aluminum plate was a factor.NTSB OPS06IA007Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Chicago, ILThe probable cause of this incident was the ORD tower local controller's failure to provide sufficient separation between two aircraft departing intersecting runways. Contributing to the incident was the ORD local monitor's failure to monitor the situating…NTSB DEN05IA076Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Denver, COthe improper use of procedure used by the ground personnel resulting in the right wing of the aircraft colliding with the left wing of another aircraft. A factor in this incident was the failure to maintain clearance by the flight crew of the other aircraft.NTSB DEN05IA076Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Denver, COthe improper use of procedure used by the ground personnel resulting in the right wing of the aircraft colliding with the left wing of another aircraft. A factor in this incident was the failure to maintain clearance by the flight crew of the other aircraft.NTSB CHI02IA050Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Chicago, ILReason for occurrence is undetermined.NTSB CHI00LA269Accident · Serious injuriesLimited investigationFinal reportBoeing 737-322 · Chicago, ILthe evasive maneuver performed by the pilot. A factor was the activation of the collision avoidance system.NTSB LAX99LA291Accident · Serious injuriesLimited investigationFinal reportBoeing 737-322 · Santa Barbara, CAThe flight's encounter with wake vortices from a preceding heavy aircraft.NTSB FTW98FA273Accident · Minor injuriesField investigationFinal reportBoeing 737-322 · Denver, COInadequate visual lookout by ground personnel (tug operator). Factors include failure of the airline to provide proper assistance (wing walkers) to the tug operator, and inadequate pushback procedures by the airline; inattention of the catering truck driver,…NTSB CHI97LA162Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Valparaiso, INa delay by the pilot of the other aircraft in turning on his mode C transponder.NTSB LAX96LA222Accident · No injuriesLimited investigationFinal reportBoeing 737-322 · San Francisco, CAinadequate visual lookout by the United Airlines tug driver during the pushback operation. Contributing factors were: the driver's reduced ability to observe the American B-767 due to the nighttime condition, and United Airlines management's failure to ensure…NTSB CHI91IA062Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Kansas City, MOImproper use of the throttles, and failure to maintain directional control by the first officer. Factors related to the incident are: ice on the runway, lack of total experience in the type aircraft and operation by the first officer, and inadequate…NTSB LAX90IA293Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Los Angeles, CAImproper maintenance service by a company employee who allowed a foreign object (flashlight) to remain in the landing gear extend/retract linkage during a night servicing before the flight.NTSB CHI90IA070Incident · No injuriesIncident investigationFinal reportBoeing B737-300 · Cedar Rapids, IAThe failure of all four main landing gear tires on takeoff due to the parking brake being locked.NTSB CHI88IA015Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Chicago, ILThe south rwys (32L, 9R, & 4R) were being ctld by the south LCL ctlr (slc) & the north rwys (9L & 4L) were ctld by the north LCL ctlr (nlc). At 1543:26, slc told united flt 973 (Boeing 737) to hold on 32L & expect a 3 min delay bfr tkof. Air Wisconsin flt 954…
Back to Boeing 737-322