FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN22LA369 · ICP SRL SAVANNAH S

29 Jul 2022 · Evansville, IN, United States

ICP SRL SAVANNAH S · Accident: hard landing

From University of Illinois Willard Airport (CMI) to an unrecorded destination

Report a problem

Event

NTSB case
CEN22LA369
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

ICP SRL SAVANNAH S

Aircraft type
ICP SRL SAVANNAH
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N5200S
Operator
Unknown
Onboard fatalities
Unknown
Route
From University of Illinois Willard Airport (CMI), Champaign/Urbana, ILTo not recorded
Aircraft age
About 9 years (built 2013)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that while on final approach for landing in gusting winds and about 5 ft. above the ground, the airplane “dropped” and experienced a hard landing that collapsed the nose landing gear. The airplane slid along the runway for 5 to 10 ft. and came to a stop on the runway center line. The airplane sustained substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. At the time of the accident, the airplane was landing on runway 36 with winds 360o at 10 knots with gusts to 15 knots. The pilot stated that the accident could have been prevented if he had initiated a go-around.

Probable cause

The pilot’s improper landing flare in gusting winds, which resulted in a hard landing and the nose gear collapsing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN22LA369
Event ID
20220808105690
Case number
CEN22LA369
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 53b17473cd11bd7e0038f38157ba9c7258176772778e647bf826a8d83fbe1269; retrieved 2026-09-16T15:36:09.950Z.