CEN16LA299 · Engineering & Research 415 C
Engineering & Research 415 C · Accident: abnormal runway contact during landing
From Ogle County Airport (C55) to Ogle County Airport (C55)
Event
- NTSB case
- CEN16LA299
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
Engineering & Research 415 C
- Aircraft type
- Engineering Research 415
- 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
- N99307
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ogle County Airport (C55), Mt Morris, ILTo Ogle County Airport (C55), Mt Morris, IL
- Aircraft age
- About 70 years (built 1946)
- 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
- Abnormal runway contact
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was conducting a local personal flight, which was the airplane's first flight following its annual inspection. The pilot reported that, while on the downwind leg, he reduced power for landing and that the engine then lost power. During the subsequent forced landing, the airplane encountered a crosswind gust and then bounced twice, which caused substantial firewall damage.
An examination of the carburetor revealed no anomalies. The weather conditions at the time of the accident were conducive to the accumulation of serious carburetor icing at descent power settings. It is likely that the engine power lost power due to carburetor icing.
Probable cause
The pilot's loss of airplane control during a forced landing in gusting crosswind conditions and the airplane’s subsequent bounce on the runway following a loss of engine power. Contributing to the accident was the loss of engine power due to carburetor icing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA299
- Event ID
- 20160802X52258
- Case number
- CEN16LA299
- 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, coordinates. 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: 2c16d822fb63e22ad29bda0315df051b3abf700bac8a71a1eb07eafda63fca23; retrieved 2026-09-16T03:44:41.809Z.