NTSB investigations: Lycoming IO-360-L2A, 2014

16 cases on aircraft whose registry engine model is Lycoming IO-360-L2A. 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

20012026
NTSB investigations: Lycoming IO-360-L2A, 2014 per year, 2001–2026: 404 cases
20012
20021
20037
200418
200513
200615
200722
200824
200920
201020
201121
201222
201314
201416
201512
201621
201724
201811
201914
202014
202120
202210
202315
202419
202513
202616

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\") = 2014
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41597'))
  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 ERA15CA056Accident · No injuriesData collectionFinal reportCessna 172S · Sarasota, FLThe student pilot's failure to maintain airplane control during the initial climb, resulting in a runway excursion and substantial damage to the engine firewall. The student pilot's lack of overall flying experience was a factor.Nov 12, 2014 · N60155 · Substantial damageNTSB ERA15FA046Accident · 1 fatalField investigationFinal reportCessna 172 · Hinton, VAThe flight instructor’s decision to conduct a night training flight in mountainous terrain without conducting or allowing the student to conduct appropriate preflight planning and his lack of situational awareness of the surrounding terrain altitude, which…Nov 8, 2014 · N2152T · Substantial damageNTSB WPR15LA025Accident · No injuriesLimited investigationFinal reportCessna 172S · Santa Monica, CAThe separation of a section of a propeller blade due to fatigue cracking. Contributing to the accident was the operator’s failure to comply with the manufacturer’s maintenance and inspection instructions.Oct 26, 2014 · N353MV · Substantial damageNTSB WPR15CA028Accident · No injuriesData collectionFinal reportCessna 172 - S · Hawthorne, CAThe pilot's improper flare which resulted in a loss of aircraft control and subsequent hard landing.Oct 23, 2014 · N564AT · Substantial damageNTSB WPR15CA018Accident · No injuriesData collectionFinal reportCessna 172 - R · Lake Havasu, AZThe pilot's failure to maintain directional control during the landing roll, which resulted in a runway excursion and impact with terrain.Oct 23, 2014 · N1590W · Substantial damageNTSB WPR15CA004Accident · Minor injuriesData collectionFinal reportCessna 172S · Sedona, AZThe pilot's failure to maintain airplane control during the landing roll out.Oct 5, 2014 · N2179L · Substantial damageNTSB CEN14FA506Accident · 1 fatalField investigationFinal reportCessna 172R · Okmulgee, OKThe pilot's continued visual flight into instrument meteorological conditions, which resulted in his failure to maintain clearance with trees and terrain.Sep 19, 2014 · N2435R · Substantial damageNTSB ERA14CA452Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe student pilot's improper landing flare, which resulted in a hard landing. Contributing to the accident was the pilot's self-induced pressure to land due to the deteriorating weather conditions.Sep 14, 2014 · N21670 · Substantial damageNTSB WPR14CA351Accident · No injuriesData collectionFinal reportCessna 172S · Santa Ynez, CAThe student pilot's inadequate flare and loss of aircraft control during landing, which resulted in multiple bounces.Aug 16, 2014 · N10033 · Substantial damageNTSB CEN14CA322Accident · No injuriesData collectionFinal reportCessna 172S · Knox, INThe student pilot's use of excessive back pressure on the flight controls during an attempted go around that induced a stall and loss of control.Jun 25, 2014 · N1307C · Substantial damageNTSB ERA14FA283Accident · 2 fatalField investigationFinal reportCessna 172S · Daytona Beach, FLA partial loss of engine power during the initial climb after takeoff for reasons that could not be determined due to the postaccident condition of the wreckage. Contributing to the accident was the pilots' decision to turn back to the airport, which led to…Jun 10, 2014 · N5524L · DestroyedNTSB WPR14CA274Accident · No injuriesData collectionFinal reportCessna 172 - R · Buckeye, AZThe pilot's improper landing flare, which resulted in a hard landing.May 19, 2014 · N1590W · Substantial damageNTSB WPR14CA163Accident · No injuriesData collectionFinal reportCessna 172S · Everett, WAThe pilot's failure to maintain directional control during a takeoff, which resulted in the airplane veering off the runway surface and colliding with a sign.Apr 10, 2014 · N1152Z · Substantial damageNTSB CEN14CA187Accident · No injuriesData collectionFinal reportCessna 172 · Larimore, NDFailure of the pilot to attain and maintain sufficient control inputs to compensate for the crosswind. Contributing to the accident was the flight instructor's failure to adequately monitor the pilot and the flight.Apr 5, 2014 · N510ND · Substantial damageNTSB ERA14CA124Accident · No injuriesData collectionFinal reportCessna 172S · Mansfield, MAThe student pilot's failure to maintain an adequate approach glide path, which resulted in a collision with a snow bank.Feb 15, 2014 · N2143X · Substantial damageNTSB ERA14CA109Accident · No injuriesData collectionFinal reportCessna 172S · Immokalee, FLThe student pilot's improper landing flare, which resulted in a hard landing.Jan 27, 2014 · N21670 · Substantial damage