NTSB investigations: Boeing 737-3B7
14 cases on aircraft the registry lists as Boeing 737-3B7. 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
| 1991 | 1 |
|---|---|
| 1992 | 1 |
| 1993 | 1 |
| 1995 | 4 |
| 1996 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2005 | 1 |
| 2006 | 1 |
| 2008 | 1 |
| 2009 | 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 ('138447F'))
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 ('138447F'))
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 ENG09IA009Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Charlotte (CLT), NCThe failure of the left hand main landing gear was caused by heat induced cracks resulting from abusive grinding/polishing of the chrome plate that was applied during the last overhaul.NTSB ENG08IA051Incident · No injuriesIncident investigationFinal reportBoeing 737 · Phoenix (PHX), AZThe failure of the MLG was due to cracking in the cylinder wall resulting from a fatigue mechanism which initiated at, and near the inner diameter (ID) surface, with propagation through the wall toward the outer diameter(OD) surface. Crack initiation was due…NTSB NYC06FA184Accident · Minor injuriesField investigationFinal reportBoeing 737-300 · Pittsburgh, PAThe airplane tug driver's inadvertent movement of the tug gear shift lever from forward to reverse, which resulted in the nose landing gear collapse. Contributing to the accident was the defective gear shift lever.NTSB NYC05IA095Incident · No injuriesIncident investigationFinal reportAirbus Industrie A330-301 · Boston, MAThe local east controller's failure to follow FAA Order 7110.65, para 3-9-8 and Boston Tower Order 7110.11, Standard Operating Procedures, which resulted in a runway incursion during takeoff involving two transport category airplanes.NTSB NYC00LA097Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Boston, MAIn flight encounter with turbulence.NTSB NYC98IA165Incident · Minor injuriesIncident investigationFinal reportBoeing 737-300 · Mcconnellsburg, PAA high altitude encounter with wake vortices.NTSB MIA96LA220Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Chattanooga, TNclear air turbulence, which was encountered during cruise flight and resulted in injuries to passengers.NTSB NYC96IA022Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Portland, MEa bird strike during takeoff, which resulted in failure of several fan blades in the right engine and a partial loss of engine power.NTSB MIA95IA214Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Fort Lauderdale, FLLow electrical resistance of the autopilot aileron actuator for unspecified reasons which resulted in an uncommanded roll to the right.NTSB MIA95IA194Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Charlotte, NCImproper installation of the 'a' system flight control computer by company maintenance personnel, which resulted in pin connector(s) being pushed loose and subsequent malfunction of the autopilot.NTSB MIA95IA187Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Orlando, FLContamination of the wiring harness and electrical connectors to the E-1-2 and E-1-3 shelf disconnect brackets in the electronics compartment, which resulted in an electrical fault and an uncommanded roll malfunction of the autopilot. A factor relating to the…NTSB CHI93IA372Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Indianapolis, INan undetermined problem which resulted in the physical impairment of flight attendants, passengers and the first officer.NTSB NYC93LA040Accident · 1 fatalLimited investigationFinal reportBoeing 737-300LR · Flushing, NYA lack of adequate clearance between the walker and tug which resulted in the walker being struck by the tug when he fell for unknown reason(s). A factor related to the accident was the lack of a policy to stay clear of the tug, towbar, and nosewheel of the…NTSB DCA91MA018Accident · 34 fatalClass 1 · MajorFinal reportBoeing 737-300 · Los Angeles, CAThe failure of the Los Angeles air traffic facility management to implement procedures that provided redundancy comparable to the requirements contained in the national operational position standards and the failure of the FAA air traffic service to provide…