NTSB investigations: Lycoming IO-360-L2A, 2010

20 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, 2010 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\") = 2010
    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 ERA11LA100Accident · No injuriesLimited investigationFinal reportCessna 172 · St. ThomasThe pilot's failure to maintain an adequate visual lookout while taxiing.Dec 13, 2010 · N1348L · Substantial damageNTSB CEN11CA100Accident · No injuriesData collectionFinal reportCessna 172S · Lawrence, KSThe student pilot’s non-stabilized approach and improper landing flare, which resulted in a hard landing.Dec 7, 2010 · N99HV · Substantial damageNTSB WPR11CA037Accident · No injuriesData collectionFinal reportCessna 172S · Port Townsend, WAThe pilot's improper flare/touchdown while landing, resulting in a loss of directional control and a runway excursion.Nov 4, 2010 · N14511 · Substantial damageNTSB ERA11LA015Accident · No injuriesLimited investigationFinal reportCessna 172SP · Boynton Beach, FLThe loss of engine power for undetermined reasons.Oct 10, 2010 · N423FT · Substantial damageNTSB ERA10CA505Accident · No injuriesData collectionFinal reportCessna 172S · Franconia, NHThe pilot’s delay in initiating a go-around, which resulted in an in-flight collision with a fence.Sep 25, 2010 · N5295Y · Substantial damageNTSB CEN10LA563Accident · No injuriesLimited investigationFinal reportCessna 172S · Longmont, COThe pilot's inadequate landing flare and improper recovery from a bounced landing.Sep 22, 2010 · N2459K · Substantial damageNTSB ERA10CA468Accident · No injuriesData collectionFinal reportCessna 172S · Frederick, MDUndetermined.Aug 25, 2010 · N387AF · Substantial damageNTSB ERA10CA398Accident · No injuriesData collectionFinal reportCessna 172 · White Plains, NYThe student pilot's improper landing flare and the flight instructor's delayed remedial action resulting in a bounced landing.Jul 24, 2010 · N1166W · Substantial damageNTSB ERA10CA363Accident · No injuriesData collectionFinal reportCessna 172S · Chesapeake, VAA hard landing by person(s)unknown.Jun 30, 2010 · N6064R · Substantial damageNTSB CEN10CA325Accident · No injuriesData collectionFinal reportCessna 172 · Traverse City, MIDamage to the firewall for undetermined reasons.Jun 15, 2010 · N52519 · Substantial damageNTSB ERA10CA326Accident · No injuriesData collectionFinal reportCessna 172 · New Smyrna Beach, FLThe student pilot’s improper landing flare, and the flight instructor's delayed remedial action.Jun 9, 2010 · N62568 · Substantial damageNTSB CEN10CA289Accident · No injuriesData collectionFinal reportCessna 172S · Greenfield, INThe pilot's improper landing flare and recovery from a bounced landing.Jun 1, 2010 · N1448Z · Substantial damageNTSB ERA10CA278Accident · No injuriesData collectionFinal reportCessna 172S · East Haddam, CTThe pilot's delayed decision to attempt a go-around, and his subsequent failure to maintain directional control while landing.May 24, 2010 · N169ER · Substantial damageNTSB ERA10CA282Accident · No injuriesData collectionFinal reportCessna 172S · Jekyll Island, GAThe pilot's loss of airplane control while landing with a crosswind.May 16, 2010 · N53039 · Substantial damageNTSB WPR10CA238Accident · No injuriesData collectionFinal reportCessna 172S · Corvallis, ORThe pilot's improper use of the flight and engine controls, resulting in a bounced landing.May 13, 2010 · N66083 · Substantial damageNTSB ERA10CA512Accident · No injuriesData collectionFinal reportCessna 172R · Hampton, VAThe student pilot's inadequate landing flare and improper recovery from a bounced landing. Contributing to the accident was the student’s decision to land with a tailwind.Apr 30, 2010 · N429FF · Substantial damageNTSB ERA10CA200Accident · No injuriesData collectionFinal reportCessna 172 · Sarasota, FLThe student pilot's inadequate recovery from a bounced landing.Mar 30, 2010 · N21394 · Substantial damageNTSB CEN10CA176Accident · No injuriesData collectionFinal reportCessna 172S · Mckinney, TXThe student pilot's loss of directional control while landing with a crosswind.Mar 26, 2010 · N18563 · Substantial damageNTSB CEN10CA163Accident · No injuriesData collectionFinal reportCessna 172S · Lawrence, KSThe student pilot's failure to maintain an appropriate glide path during approach. Contributing to the accident was the student pilot's decision to continue the approach instead of going around.Mar 10, 2010 · N99HV · Substantial damageNTSB ERA10LA105Accident · 1 fatalLimited investigationFinal reportCessna 172S · Greenbush, METhe pilot's improper decision to attempt a transoceanic flight in turbulent, icing conditions, with an overweight airplane that was not approved for moderate turbulence and not equipped with deicing systems. Contributing to the accident was the pilot's…Jan 4, 2010 · N5118J · Substantial damage