CEN12LA111 · Curtiss Wright P40M
Tri-State Warbird Museum Curtiss Wright P40M · Accident: loss of engine power (total) en route
From Clermont County Airport (I69) to Clermont County Airport (I69)
Event
- NTSB case
- CEN12LA111
- 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
Curtiss Wright P40M
- Aircraft type
- Curtiss Wright P40
- 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
- N5813
- Operator
- Tri-State Warbird Museum
- Onboard fatalities
- Unknown
- Route
- From Clermont County Airport (I69), Batavia, OHTo Clermont County Airport (I69), Batavia, OH
- Aircraft age
- Not recorded
- 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
- En route
- 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
- Loss of engine power (total)
- 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 power plant
- Aircraft › Fluids/miscellaneous hardware
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that the engine shuddered several times and that the engine oil pressure dropped to zero, followed by a complete loss of engine power. About that time, the windshield and canopy were covered with oil and coolant, which restricted forward visibility. The pilot performed a forced landing at the departure airport. However, due to excessive airspeed on approach, he was unable to stop the airplane before it departed the end of the runway and impacted the airport perimeter fence. A postaccident examination revealed that the engine oil cooler had cracked, which resulted in an engine failure due to a loss of engine oil. The oil cooler was an original World War II era component. The crack did not appear to have initiated at a previously repaired area.
Probable cause
A loss of engine power due to failure of the engine oil cooler and subsequent oil starvation to the engine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA111
- Event ID
- 20111220X20124
- Case number
- CEN12LA111
- 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. 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: df1aea4475257e4aef38228a73582eeb05591c0b4b2953711a67f30bc9bfd012; retrieved 2026-09-15T17:01:00.960Z.