ERA23LA063 · Hagerty Glasair Super IIS-TD
Hagerty Glasair Super IIS-TD · Accident: system/component malfunction/failure (non-power) en route
From an unrecorded airport to Western Carolina Regional Airport (RHP)
Event
- NTSB case
- ERA23LA063
- 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
- Event fatalities
- Unknown
- 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
Hagerty Glasair Super IIS-TD
- Aircraft type
- Hagerty GLASAIR SUPER IIS-TD
- 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
- N430JV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Western Carolina Regional Airport (RHP), Andrews, NC
- Aircraft age
- About 26 years (built 1996)
- 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
- System/component malfunction/failure (non-power)
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during the climb, about 4,500 ft mean sea level, the engine began to run rough, and shortly thereafter lost all power. The pilot immediately turned back toward the departure airport, which was about 5 miles from his position. He began troubleshooting the loss of power, but power was not restored. The pilot was able to glide to the airport; however, in a right turn to align with the runway, the pilot felt the onset of an aerodynamic stall. He leveled the wings, the airplane overshot the runway, descended abruptly, and impacted a grass area hard next to the runway. The left wing and fuselage sustained substantial damage. A postaccident test run of the engine revealed it produced normal power with the electric fuel pump on, but would not operate with only the engine-driven fuel pump. Further examination and disassembly of the engine-driven fuel pump revealed no anomalies that would have explained its inability to pump fuel. The pilot reported that in the climb he turned off the electric fuel pump and, after the loss of power, he did not turn the pump back on, despite the owner’s manual instructing pilots to use the electric fuel pump following a loss of engine power. Had the pilot turned the electric fuel pump on, power likely would have been restored.
Probable cause
The loss of engine power due to the failure of the engine-driven fuel pump and the pilot’s failure to use the electric fuel pump, which resulted in a forced, hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA063
- Event ID
- 20221117106305
- Case number
- ERA23LA063
- 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, cause areas. 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: aee489457a35f1811ef3bf8600a716f8432d1b66302d4ae8c699e91802482666; retrieved 2026-09-16T16:24:02.333Z.