NTSB investigations: Boeing 737-7H4, 2010

7 cases on aircraft the registry lists as Boeing 737-7H4. 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

19982026
NTSB investigations: Boeing 737-7H4, 2010 per year, 1998–2026: 67 cases
19981
20043
20053
20062
20082
20091
20107
20115
20122
20132
20146
20154
20163
20173
20184
20191
20201
20211
20224
20231
20244
20256
20261

Latest 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 year(c.\"eventDate\") = 2010
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1384404'))
  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.

NTSB ENG11IA011Incident · No injuriesIncident investigationFinal reportBoeing 737 · San Francisco, CAThe probable cause of the undercowl in-flight engine fire was the insufficient installation torque of the bolts that secure the fuel manifold cover to the fuel manifold. Engine vibrations and fuel pressure cycles caused the bolts to gradually loosen further…Dec 25, 2010 · N248WN · No damageNTSB DCA11CA014Accident · No injuriesData collectionFinal reportBoeing 737-7H4 · Philadelphia, PAthe failure of the ground operations personnel to maintain awareness of the relative position of the two airplanes.Dec 18, 2010 · N913WN · 2 aircraft · Substantial damageNTSB OPS10IA538Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Los Angeles, CAFailure of the air traffic controller to exercise positive control of the situation by issuing clear and timely control instructions to the helicopter pilot. Contributing to the incident was delay by the helicopter pilot in responding to instructions issued…Sep 4, 2010 · N907WN · 2 aircraft · No damageNTSB OPS10IA132Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Houston, TXThe failure of the local controller to issue control instructions necessary to ensure positive control/standard separation of traffic operating within the Class B airspace.Apr 28, 2010 · N242WN · 2 aircraft · No damageNTSB OPS10IA090Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Burbank, CAThe improper separation procedures by air traffic control.Apr 19, 2010 · N473WN · 2 aircraft · No damageNTSB OPS10IA015Incident · No injuriesIncident investigationFinal reportCessna 208B · Phoenix, AZThe Cessna 208 pilot’s failure to identify the correct landing runway.Mar 20, 2010 · N992FE · 2 aircraft · No damageNTSB WPR10LA134Accident · Serious injuriesLimited investigationFinal reportBoeing 737-7H4 · Santa Clarita, CAThe pilot’s abrupt airplane pitch change maneuver. Contributing to the accident was the flight crew’s failure to maintain the heading specified by the air traffic controller, which would have avoided the near collision course with an unidentified airplane…Feb 13, 2010 · N221WN · No damage