NTSB investigations: Embraer EMB-120ER
13 cases on aircraft the registry lists as Embraer EMB-120ER. 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
| 1987 | 1 |
|---|---|
| 1992 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 2000 | 2 |
| 2001 | 1 |
| 2003 | 2 |
| 2005 | 1 |
| 2010 | 1 |
| 2017 | 1 |
| 2018 | 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 ('3260203'))
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 ('3260203'))
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 DCA18CA303Accident · No injuriesClass 4 · Data collectionFinal reportEmbraer EMB120 · 40 nm vicinity south of Lake Jackson, TXan encounter with severe turbulence, which caused the improperly secured cargo to shift and damage the airplane floor structure.NTSB CEN17LA350Accident · No injuriesLimited investigationFinal reportEmbraer EMB 120ER · Greeley, COThe bus driver's failure to maintain clearance from the standing airplane during dark night conditions. Contributing to the accident was the airport's lack of an escort for the bus.NTSB WPR10IA135Incident · No injuriesIncident investigationFinal reportEmbraer EMB-120ER · Los Angeles, CAThe flight crew’s failure to maintain clearance from the jet bridge during taxi. Contributing to the incident was the ramp marshaller's diverted attention and failure to signal the flight crew to stop at the correct position.NTSB DEN06IA020Incident · No injuriesIncident investigationFinal reportEmbraer EMB-120ER · Denver, COthe pilot's failure to maintain clearance from the taxiway light. Factors contributing to the incident were the crew's inadequate visual lookout and the taxiway light.NTSB DEN03LA096Accident · No injuriesLimited investigationFinal reportEmbraer EMB-120ER · Denver, COthe ground personnel's failure to maintain aircraft/ground vehicle clearance, resulting in the collision. Contributing factors include ground communications not coordinated by the ground personnel and the airport vehicle.NTSB DEN03IA054Incident · No injuriesIncident investigationFinal reportEmbraer EMB-120ER · Cedar City, UTthe captain's failure to maintain directional control during takeoff. Factors contributing to the accident were the crew's diverted attention, the snow and slush-covered runway, the fog, and the runway marker.NTSB ANC02LA002Accident · Minor injuriesLimited investigationFinal reportEmbraer 120ER · Bethel, AKThe captain's continued descent below the minimum descent altitude which resulted in impact with terrain during an instrument landing approach. Factors contributing to the accident were the flightcrew's failure to reset the altimeters to the correct altimeter…NTSB NYC01LA054Accident · Serious injuriesLimited investigationFinal reportEmbraer 120RT · Charleston, WVDeer on the runway. Factors included reduced visibility due to nighttime lighting and light snow conditions, breaches in the perimeter fence, increased seasonal deer activity, and the rural location of the airport.NTSB LAX00IA106Incident · No injuriesIncident investigationFinal reportEmbraer 120 · Fresno, CAMoisture contamination of the elevator trim actuator units resulting in their failure to operate at below freezing temperaturesNTSB LAX97IA056Incident · Minor injuriesIncident investigationFinal reportEmbraer EMB-120ER · Los Angeles, CAa laser light source of unknown origin, directed toward the aircraft, as it was approaching to land.NTSB LAX95LA255Accident · No injuriesLimited investigationFinal reportEmbraer EMB-120 RT · Los Angeles, CAthe captain's decision to taxi across a non-movement aircraft parking area instead of using the designated taxi lane to exit the ramp. A factor in the accident was the dark night environmental lighting conditions.NTSB FTW93IA048Incident · No injuriesIncident investigationFinal reportEmbraer EMB-120RT · Houston, TXThe assigned mechanic's failure to reinstall the attachment screws and the quality inspector's inadequate inspection of the completed work. A factor was the complacency of the maintenance personnel.NTSB MKC87IA043Incident · No injuriesIncident investigationFinal reportEmbraer EMB-120 · Springfield, MOThe PIC of this air midwest flt 4408 said that, while on initial climb, power (np) on the left engine decayed to 60% and would not recover. The engine was feathered by condition lever but the torque rose to 140% while returning for a landing, according to the…