NTSB investigations: Lycoming IO-360-L2A
50 cases on aircraft whose registry engine model is Lycoming IO-360-L2A, where the defining event was Loss of control on ground. 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
| 2008 | 2 |
|---|---|
| 2009 | 5 |
| 2010 | 2 |
| 2011 | 5 |
| 2012 | 6 |
| 2013 | 2 |
| 2014 | 3 |
| 2015 | 1 |
| 2016 | 2 |
| 2017 | 1 |
| 2019 | 7 |
| 2020 | 5 |
| 2021 | 2 |
| 2023 | 4 |
| 2024 | 2 |
| 2026 | 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 ('41597')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '230'))
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 ('41597')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e."isDefiningEvent" AND e."tier2Number" = '230'))
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 CEN26LA104Accident · No injuriesClass 4 · LimitedFinal reportTextron 172S · Augusta, KSThe student pilot’s failure to maintain control during the takeoff.NTSB CEN24LA233Accident · No injuriesClass 4 · LimitedFinal reportCessna 172R · Murphysboro, ILThe pilot’s failure to maintain directional control during landing.NTSB ERA24LA145Accident · No injuriesClass 4 · LimitedFinal reportTextron 172S · Melbourne, FLThe student pilot’s failure to maintain directional control while landing in a crosswind.NTSB WPR23LA253Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Novato, CAThe pilot's failure to maintain directional control of the airplane during the landing roll for a touch and go, which resulted in a collision with terrain.NTSB CEN23LA179Accident · No injuriesClass 4 · LimitedFinal reportTextron 172S · Englewood, COThe pilot’s decision to adjust his seat during taxi, which resulted in his seat sliding aft, and subsequent loss of directional control.NTSB CEN23LA175Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Brookings, SDThe student pilot’s failure to maintain pitch and directional control during the takeoff roll. Contributing to the accident, was the student pilot’s delay in relinquishing control of the airplane and the instructor's delayed reaction before the loss of…NTSB CEN23LA102Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Limon, COThe pilot’s failure to maintain directional control during the takeoff roll.NTSB CEN21LA235Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · McAllen, TXThe student pilot’s failure to maintain directional control during landing, which resulted in a runway excursion and collision with a runway sign.NTSB CEN21LA160Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Watkins, COThe pilot’s failure to maintain directional control during takeoff and the instructor pilot’s inadequate supervision of the pilot’s takeoff.NTSB ERA21LA057Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Sanford, NCThe pilot's loss of directional control during takeoff in crosswind conditions, which resulted in a runway excursion and impact with terrain.NTSB CEN20CA205Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Lakeview, ARThe pilot’s failure to maintain control of the airplane during the takeoff.NTSB CEN20CA128Accident · No injuriesData collectionFinal reportCessna 172 · Denver, COThe pilot's incorrect right rudder application during a touch-and go-landing, which resulted in a loss of directional control, runway excursion, and a collision with a runway sign.NTSB ERA20CA141Accident · No injuriesData collectionFinal reportCessna 172 · Ocean City, MDThe pilot's failure to maintain directional control during an attempted go-around to avoid birds, which resulted in a runway excursion and subsequent nose-over.NTSB CEN20CA094Accident · No injuriesData collectionFinal reportCessna 172 · Boulder, COThe pilot's loss of directional control during the landing roll on the slush-covered runway.NTSB GAA20CA023Accident · No injuriesData collectionFinal reportCessna 172 · Louisville, KYThe student pilot's improper landing flare, which resulted in a porpoised landing, a subsequent hard landing on grass left of the runway, and a nose-over. Contributing to the accident was the student’s self-imposed pressure to land the airplaneNTSB GAA19CA368Accident · No injuriesData collectionFinal reportCessna 172 · Tulsa, OKThe pilot's failure to maintain directional control while landing in gusting crosswind conditions, which resulted in a runway excursion and impact with a taxiway sign.NTSB GAA19CA326Accident · No injuriesData collectionFinal reportCessna 172 · Orlando, FLThe student pilot's excessive rudder application during takeoff and the flight instructor's delayed remedial action, which resulted in a loss of directional control, a runway excursion, and subsequent substantial damage.NTSB GAA19CA225Accident · No injuriesData collectionFinal reportCessna 172 · Scottsdale, AZThe pilot's improper rudder inputs and failure to maintain directional control during landing with a crosswind, which resulted in a runway excursion and impact with a runway sign.NTSB CEN19LA113Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Spring, TXThe pilot’s failure to maintain airplane directional control while taxiing at an unsafe ground speed.NTSB GAA19CA137Accident · No injuriesData collectionFinal reportCessna 172 · Sanford, FLThe student pilot's failure maintain the proper pitch attitude during landing, which resulted in the airplane porpoising.NTSB GAA19CA113Accident · No injuriesData collectionFinal reportCessna 172 · Reno, NVThe student pilot's failure to maintain directional control during a rejected takeoff, which resulted in a runway excursion and impact with a ditch.NTSB GAA17CA482Accident · No injuriesData collectionFinal reportCessna 172 · Kearney, NEThe pilot’s failure to maintain directional control of the airplane during the landing roll, which resulted in a runway excursion.NTSB GAA16CA416Accident · No injuriesData collectionFinal reportCessna 172 · Palm Springs, CAThe student pilot's failure to maintain directional control during an aborted landing, which resulted in a runway excursion and a nose over in rough terrain.NTSB GAA16CA415Accident · No injuriesData collectionFinal reportCessna 172 · Kissimmee, FLThe student pilot's failure to maintain directional control during takeoff.NTSB WPR16LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172S · San Jose, CAThe pilot's failure to maintain directional control during the landing roll at night, which resulted in a runway excursion.NTSB 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.NTSB WPR15CA004Accident · Minor injuriesData collectionFinal reportCessna 172S · Sedona, AZThe pilot's failure to maintain airplane control during the landing roll out.NTSB 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.NTSB ERA14CA106Accident · No injuriesData collectionFinal reportCessna 172S · St. Augustine, FLThe student pilot’s failure to maintain directional control during the landing roll with a crosswind.NTSB WPR13LA180Accident · No injuriesLimited investigationFinal reportCessna 172 · Phoenix, AZThe student pilot's excessive directional control inputs during the takeoff roll and the flight instructor's delayed and ineffective corrective actions, which resulted in the loss of airplane control.NTSB CEN12CA510Accident · No injuriesData collectionFinal reportCessna 172S · Oshkosh, WIThe flight instructor’s loss of directional control during landing, which resulted in a collision with a runway light.NTSB WPR12CA232Accident · No injuriesData collectionFinal reportCessna 172S · Page, AZThe pilot's failure to maintain directional control during the landing flare.NTSB ERA12CA369Accident · No injuriesData collectionFinal reportCessna 172 · Gainesville, GAThe student pilot's improper use of the flight controls during the takeoff and the flight instructor's delayed remedial action. Contributing to the accident was the student pilot’s interference with the flight instructor’s attempted remedial actions.NTSB CEN12CA342Accident · No injuriesData collectionFinal reportCessna 172S · Fort Scott, KSThe student pilot’s loss of directional control during the landing roll. Contributing to the accident was the student pilot’s diverted attention to retract the flaps.NTSB ERA12CA330Accident · No injuriesData collectionFinal reportCessna 172R · Immokalee, FLThe student pilot’s failure to maintain directional control during a touch-and-go landing.NTSB WPR12CA171Accident · No injuriesData collectionFinal reportCessna 172S · Prescott, AZThe pilot's inadequate compensation for a crosswind during takeoff, which resulted in a loss of directional control.NTSB WPR12CA038Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe student pilot's inadequate directional control during takeoff.NTSB WPR11CA440Accident · No injuriesData collectionFinal reportCessna 172 · Phoenix, AZThe pilot's failure to maintain directional control during the landing roll.NTSB ERA11CA244Accident · No injuriesData collectionFinal reportCessna 172S · Saint Petersburg, FLThe failure of the student pilot to maintain directional control during a touch-and-go landing.NTSB ERA11CA132Accident · No injuriesData collectionFinal reportCessna 172S · St. Petersburg, FLThe student pilot's failure to maintain directional control while attempting to turn the airplane onto a taxiway after landing.NTSB CEN11CA171Accident · No injuriesData collectionFinal reportCessna 172R · Shreveport, LAThe student pilot's loss of directional control during the landing.NTSB 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.NTSB ERA10CA282Accident · No injuriesData collectionFinal reportCessna 172S · Jekyll Island, GAThe pilot's loss of airplane control while landing with a crosswind.NTSB CEN10CA062Accident · No injuriesData collectionFinal reportCessna 172S · Mt. Comfort, INThe pilot's failure to maintain directional control of the airplane while touching down during the landing.NTSB ERA10CA057Accident · No injuriesData collectionFinal reportCessna 172S · Summit, DEThe student pilot’s failure to maintain directional control during takeoff.NTSB CEN09CA530Accident · No injuriesData collectionFinal reportCessna 172 · Centennial, COThe pilot's failure to maintain directional control of the airplane during the landing flare in crosswind conditions.NTSB WPR09CA275Accident · No injuriesData collectionFinal reportCessna 172S · Tooele, UTThe pilot's failure to maintain directional control during landing.NTSB ERA09CA119Accident · No injuriesData collectionFinal reportCessna 172SP · Lancaster, NYThe student pilot's failure to maintain directional control during takeoff. Contributing to the accident was the student pilot's lack of solo flight experience and the snow bank located off the left side of the runway.NTSB CEN09CA002Accident · No injuriesData collectionFinal reportCessna 172 · Alton, ILThe student pilot's failure to maintain directional control during landing. A contributing factor was the presence of the sign struck during the runway excursion.NTSB CHI08CA091Accident · No injuriesData collectionFinal reportCessna 172R · Batavia, OHThe pilot's misjudgment of the landing flare and her inadequate recovery from the bounced landing.