ERA10LA175 · Smith Edward I LANCAIR IV-P
Smith Edward I LANCAIR IV-P · Accident: powerplant system/component malfunction/failure en route
From Orlando Executive Airport (ORL) to Hampton Roads Executive Airport (PVG)
Event
- NTSB case
- ERA10LA175
- 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
- 1 · all aircraft and ground
- Ground fatalities
- 1
- 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
Smith Edward I LANCAIR IV-P
- Aircraft type
- Smith Edward LANCAIR IV-P
- 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
- N9JE
- Operator
- Smith Edward I
- Onboard fatalities
- Unknown
- Route
- From Orlando Executive Airport (ORL), Orlando, FLTo Hampton Roads Executive Airport (PVG), Norfolk, VA
- 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 · cruise
- 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
- Powerplant system/component malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft power plant
- Aircraft › Aircraft propeller/rotor
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
**This report was modified on 8/8/13. Please see the docket for this accident to view the original report.**
The pilot stated that while in cruise flight he observed the instrument panel begin to vibrate heavily and oil begin to cover the wind screen before hearing a loud "bang." The engine then lost power as oil continued to obscure the wind screen. The pilot had no forward visibility and could not maintain the airplane's altitude. He elected to make an emergency landing on a nearby beach and during the landing the airplane struck and killed a pedestrian. Examination of the airplane revealed that the propeller assembly separated from the crankshaft and was missing. The propeller assembly and propeller flange were not recovered. An examination by the NTSB Materials Laboratory of the crankshaft revealed that the aft face of the fracture contained crack arrest marks. The fracture of the crankshaft was caused by multiple-origin fatigue cracks that emanated at the aft relief radius for the propeller flange. The records for this engine and airplane do not show an entry of a propeller strike. However, multiple-origin fatigue cracks that extend nearly 50% around the circumference of the aft relief radius for the propeller flange suggest that the propeller had struck an object prior to fracture of the crankshaft. In the absence of material anomalies, the fatigue cracking appears likely to have been caused by external impact stress, such as a propeller strike.
Probable cause
A loss of engine power due to the failure of the crankshaft as a result of a previous propeller strike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10LA175
- Event ID
- 20100315X02419
- Case number
- ERA10LA175
- 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: fe9cc72f1c47e472ae4fd01c51c12d25f607a0a977d30e9689e4405edd950d95; retrieved 2026-09-13T18:00:54.383Z.