NTSB investigations: Allison 250 SER 400HP
18 cases on aircraft whose registry engine model is Allison 250 SER 400HP, where the first occurrence was “In flight collision with object”. 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
| 1982 | 2 |
|---|---|
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 2 |
| 1986 | 1 |
| 1989 | 1 |
| 1990 | 3 |
| 1991 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 2002 | 1 |
| 2005 | 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.engine_model_code IN ('03013', '03012')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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.engine_model_code IN ('03013', '03012')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 NYC05FA099Accident · Serious injuriesField investigationFinal reportBell 206L · New York, NYThe pilot's inadequate preflight planning, which resulted in an attempted takeoff with an overweight helicopter, and subsequent impact with a pier and water. Factors were a high ambient temperature and unfavorable winds.NTSB ANC03LA015Accident · 1 fatalLimited investigationFinal reportBell 206B · Kingman, AZThe pilot's failure to maintain altitude/clearance from obstacles during cruise flight, which resulted in the helicopter striking a transmission line, and subsequently the ground.NTSB ANC98LA003Accident · No injuriesLimited investigationFinal reportBell 206-B2 · Sutton, AKThe pilot's failure to maintain clearance between the tail rotor and the external long line cable, and the subsequent entanglement of the tail rotor with the long line.NTSB ANC96LA097Accident · No injuriesLimited investigationFinal reportBell 206B · Juneau, AKThe pilot's failure to maintain proper alignment while lifting the helicopter to a hover and inducing a dynamic roll to avoid striking a passenger.NTSB ANC95LA112Accident · No injuriesLimited investigationFinal reportBell 206B-3 · Bettles, AKFailure of the pilot to ensuring the sling cable was free of the skid before lifting off into a hover, which allowed the cable to become wrapped (entangled) around the skid.NTSB CHI94LA161Accident · No injuriesLimited investigationFinal reportBell 206B · Winnebago, ILa wire strike due to failure to maintain proper altitude, and improper visual lookout by the pilot-in-command.NTSB BFO91LA036Accident · No injuriesLimited investigationFinal reportHughes 369HS · Columbia, MDThe pilot's inadequate visual lookout, which resulted in his failure to see-and-avoid the obstruction (fence post).NTSB NYC90LA189Accident · Serious injuriesLimited investigationFinal reportBell 206 · Athens, OHThe pilot's failure to visually acquire and maintain clearance from the powerline(s). Contributing to the accident was the adverse weather conditions.NTSB SEA90LA081Accident · 1 fatalLimited investigationFinal reportHughes 369D · Kelso, WAFailure of the pilot to keep the external load clear of obstacles (trees). Factors related to the accident were: failure of the pilot and ground crewman to follow safety procedures, and the proximity of the trees.NTSB LAX90LA162Accident · No injuriesLimited investigationFinal reportHughes 369C · Kahului, HIThe pilots failure to ensure that adequate room existed to position the helicopter on the landing platform. Contributing to the accident was the failure of ground personnel to ensure that hazards to the landing helicopter were clear of the landing area.NTSB NYC89LA171Accident · No injuriesLimited investigationFinal reportHughes 369HS · Niagara Falls, NYFailure of the pilot to see and avoid the cables.NTSB DEN86LA151Accident · Minor injuriesLimited investigationFinal reportBell 206B · Portal, NDThe plt reported that the acft hit wires at the end of a swath run. The pitch change link broke when the main rotor contacted the wires and the plt attempted to land. After touchdown, the helicopter rolled onto its side.NTSB CHI85LA303Accident · No injuriesLimited investigationFinal reportBell 206BII · Farmington, MNDuring maneuvering to ld in an uncultivated fld the tail rotor struck a fence post,from a dismantled fence,that was concealed by high weeds. One tail rotor blade was separated,the pilot lost control,and on touchdown the helicopter rolled over.NTSB ATL85FA170Accident · 2 fatalField investigationFinal reportBell 206L · Duluth, GAAfter loading a seriously burned patient in the helicopter, the plt started the eng & lifted off from the hospital parking lot. Immediately after lift-off, he started forward translational flt. About 65 ft from the lift-off point, an advancing main rotor…NTSB LAX84LA488Accident · Serious injuriesLimited investigationFinal reportBell 206B · Paso Robles, CAPlt stated that after receiving a special VFR clearence he took off to spray a nearby field. He continued to state that he 'made a couple of circuits over the field, observed the telephone wires and began spraying. After performing 2 or 3 passes I hit some…NTSB ANC84LA012Accident · Serious injuriesLimited investigationFinal reportBell 206-B · Kodiak, AKWhile inspecting a transmission wire tower, the left skid became entangled with the power line guide. This pulled the helicopter out of CG. While the plt was trying to correct the problem, the m/r blade contacted the tower & struck the tail boom separating…NTSB ATL82DA257Accident · No injuriesFinal reportBell 206L · Greenville, SCThe pilot reported that he was making an approach to a new helipad that was still under construction when he felt a severe vibration. After landing and shutdown, he discovered that the tail rotor had struck the glass cover of a heliport perimeter light.NTSB LAX82DA140Accident · 3 fatalFinal reportHughes 369HS · 8 S. Of Page, AZThe aircraft was number two in a trail of three helicopters flying up the Colorado river at marble canyon to page, AZ when it struck an aerial cableway stretching across the river, 22 ft above the water. Witnesses stated that after the collision the…