ERA18LA190 · Glasair SH2
Glasair SH2 · Accident: loss of engine power (total) en route
From Lincoln Regional Airport (LRG) to Lincoln Regional Airport (LRG)
Event
- NTSB case
- ERA18LA190
- 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
Glasair SH2
- Aircraft type
- Glasair SH2
- 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
- N352GL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lincoln Regional Airport (LRG), Lincoln, METo Lincoln Regional Airport (LRG), Lincoln, ME
- Aircraft age
- About 23 years (built 1995)
- 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
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While in cruise flight, the experimental, amateur-built airplane's engine started to run "rough" and lost partial power. The pilot checked the engine gauges, noted no irregularities, and unsuccessfully attempted to restore engine power by turning the fuel boost pump on. Within about 30 seconds of the initial power loss, the engine lost total power and the propeller stopped. The pilot performed a forced landing to a bog and the airplane came to rest inverted, resulting in substantial damage to the empennage.
Disassembly and examination of the engine revealed that the crankshaft had fractured at the No. 4 cylinder journal. Further examination of the fracture surface revealed fatigue striations consistent with fatigue crack propagation. These striations were finely spaced and exhibited changing or erratic thicknesses on different areas of the fracture surface, consistent with propagation through high-cycle fatigue. The reason for the crack initiation could not be determined. According to the engine maintenance log, the engine experienced a propeller strike during a landing incident about 5 years and 368 flight hours before the accident. The pilot elected not to have the propeller strike or sudden stoppage inspection performed, since it was not mandatory for non-certificated engines.
Probable cause
A total loss of engine power due to a fatigue fracture of the crankshaft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA18LA190
- Event ID
- 20180712X80157
- Case number
- ERA18LA190
- 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: 784d87718ce3b0b68c4912227b06926a00892b63a2d0a5e9efd75b4f5be3c8a9; retrieved 2026-09-16T07:50:18.829Z.