CEN23LA390 · Zlin Aviation S R O SAVAGE NORDEN
Zlin Aviation S R O SAVAGE NORDEN · Accident: system/component malfunction/failure (non-power) on approach
From North Little Rock Municipal Airport (ORK) to an unrecorded destination
Event
- NTSB case
- CEN23LA390
- 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
Zlin Aviation S R O SAVAGE NORDEN
- Aircraft type
- Zlin SAVAGE NORDEN
- 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
- N7373
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From North Little Rock Municipal Airport (ORK), North Little Rock, ARTo not recorded
- Aircraft age
- About 1 year (built 2022)
- 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
- Approach · VFR pattern final
- 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
- Aircraft › Aircraft systems
- Organizational issues › Development
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor and pilot receiving instruction, who was also the airplane owner, were performing takeoffs and landings as part of a tailwheel training flight. After an uneventful landing, they departed, remained in the traffic pattern, and were on final approach when the engine lost all power. The flight instructor took control of the airplane and conducted a forced landing to a field. The airplane impacted a fence and sustained substantial damage to both wings and the fuselage. The flight instructor noticed a small fire in the engine compartment after the accident that continued for about 30 seconds. Postaccident examination revealed that the wiring for the electric fuel pumps was thermally damaged and rested on the turbine section of the turbocharger and near the exhaust system. The fuel pumps would not function when tested with airframe controls. However, they functioned normally after the thermally damaged wires were bypassed. Examination of the remaining systems revealed no mechanical anomalies that would have precluded normal operations. The engine control unit (ECU) data confirmed that the engine functioned normally for the majority of the flight but exhibited a total loss of power during the final approach. The data illustrated that the pilot increased the throttle position but the engine did not respond. Examination of an exemplar airplane revealed that the fuel pump’s wiring harness was routed near the firewall and not next to the turbocharger and exhaust, as observed on the accident airplane. According to the airplane manufacturer’s sole U.S. distributor, there is currently no standardization for placement of the fuel pump wiring during the manufacturing process. It is most likely that the engine lost power due to the thermally-damaged fuel pump wiring.
Probable cause
The airplane manufacturer’s routing of the fuel pump wiring next to the engine’s turbocharger and exhaust, which thermally damaged the wiring and resulted in a malfunction of the fuel delivery system and a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA390
- Event ID
- 20230831192973
- Case number
- CEN23LA390
- 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, 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: bb58bdef658e5c445fa70f17e444c60bf6dbe6036f676e9676ed3c24bd96f10a; retrieved 2026-09-16T18:04:09.402Z.