CEN24LA308 · Cirrus Design Corp SR22T
Cirrus Design Corp SR22T · Incident: fire/smoke (non-impact) while standing
From Tulsa Riverside Airport (RVS) to an unrecorded destination
Event
- NTSB case
- CEN24LA308
- 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
- Incident
- 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
Cirrus Design Corp SR22T
- Aircraft type
- Cirrus SR22
- 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
- N825JC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tulsa Riverside Airport (RVS), Tulsa, OKTo not recorded
- Aircraft age
- About 10 years (built 2014)
- 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
- Standing · engine(s) not operating
- 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
- Fire/smoke (non-impact)
- 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 systems
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
An airframe and powerplant mechanic removed and replaced the airplane’s engine, which included rewiring the two alternators, and performed an engine run-up without incident. A pilot then performed a short ferry flight, also without incident. After parking the airplane at the destination airport and shutting down the engine, the pilot saw smoke coming from the engine compartment. The pilot exited the airplane, looked into the louvered vents under the engine compartment, and saw electrical arcing and smoke, but did not see any fire. The airplane battery and associated wiring sustained thermal damage. The airplane’s composite firewall sustained substantial damage due to thermal damage. The mechanic who performed the engine replacement took a photograph of the alternator wire connections before removing the original engine, which he used as a reference when rewiring the alternator following the engine replacement. The photograph showed the correct wire connections, but those connections were different than those at the time of the accident. Postincident examination of the airplane revealed that the alternator wire connections were not done in accordance with the airplane manufacturer’s maintenance manual, which resulted in electrical arcing and substantial thermal damage to the airplane.
Probable cause
The mechanic’s improper installation of the alternator wiring connections, which resulted in electrical arcing and thermal damage to the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA308
- Event ID
- 20240808194873
- Case number
- CEN24LA308
- 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: ee5091fffd3a5c7eeecbbf938d58a8bdbaa75a6b5aa629e2e5c721bd9a1520a3; retrieved 2026-09-16T19:08:47.488Z.