IAD00LA062 · Boeing Stearman E75-N1
Boeing Stearman E75-N1 · Accident: total loss of engine power (mechanical failure) en route
From OH (no airport) to an unrecorded destination
Event
- NTSB case
- IAD00LA062
- 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
- 0
- 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
Boeing Stearman E75-N1
- Aircraft type
- Boeing Stearman E75
- 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
- N75647
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From OH (no airport)To not recorded
- 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
- First occurrenceThe 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
- Total loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Engine assembly, crankshaft › Fractured
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed his private airstrip for a pleasure flight. He leveled the airplane off at 2,500 feet and set the engine power to cruise RPM. About 15 minutes into the flight, the pilot felt a vibration in the engine and decided to return to his airstrip. As the airplane turned back to the airstrip, the vibrations got worse and engine RPM decreased. The pilot elected to land at closer airstrip, but as he lined up with the airport the engine stopped producing power. The pilot was unable to make the airport, landed short, and collided with trees. Examination of the engine revealed a fractured crankshaft. The total time on the crankshaft was not determined. This was the first flight after the metal propeller was removed and the wooden propeller was installed.
Probable cause
Loss of total engine power due to a fractured crankshaft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD00LA062
- Event ID
- 20001212X21487
- Case number
- IAD00LA062
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 5ed70b3b6e45866b399fcc90fe92776bda53a90325eef952ba20c44e6f6c6e5b; retrieved 2026-09-22T12:40:34.738Z.