CEN25LA079 · Piper PA-24-250
Piper PA-24-250 · Accident: electrical system malfunction/failure during initial climb
From an unrecorded airport to Fort Worth Meacham International Airport (FTW)
Event
- NTSB case
- CEN25LA079
- 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
Piper PA-24-250
- Aircraft type
- Piper PA-24
- 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
- N8051P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Fort Worth Meacham International Airport (FTW), Fort Worth, TX
- 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
- Initial climb
- 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
- Electrical system malfunction/failure
- 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 › 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 pilot reported that just before the accident flight, the airplane’s battery was not charged, and the airplane was connected to a truck using jumper cables to start the engine. The pilot then proceeded with the flight and shortly after departure he noted sparks and smoke emanating from behind the instrument panel. He turned off the generator and the sparking stopped. He turned the electrical power back on a few times to notify air traffic control and to attempt to lower the landing gear. He believed that the landing gear was down and locked based on position of the gear itself and by noting the position of the emergency extension handle, but upon landing the airplane’s landing gear collapsed which resulted in substantial damage to the fuselage. The pilot noted that before the landing he did not physically grab the emergency landing gear extension handle to verify that it was fully forward (down and locked). Postaccident examination of the airplane by a mechanic revealed several marked and unmarked circuit breakers that were tripped. Testing of those circuits revealed that resetting the breakers and applying power to the aircraft electrical system resulted in the breakers tripping again. Further testing revealed that removal of the protected devices resulted in some of the protected circuits drawing excessive current and continuing to trip while others showed no further current draw and did not trip. It was found that many of the devices removed had internal damage and excessive current draw. One item tested, the Garmin GMA340 Audio Panel, would produce smoke from the rear of the unit when power was applied and the smoke continued for several seconds after power was removed. The mechanic did not test the airplane’s generator or voltage regulator. Investigators were unable to test the generator or voltage regulator as the wreckage was disposed of before the testing could take place. Based on the postaccident testing, the smoke reported by the pilot was likely from the internally compromised audio panel. The internal damage to the audio panel and other avionics components was consistent with a power surge due to a faulty voltage regulator, but since the generator and voltage regulator were not tested the definitive reason could not be determined. During the event the pilot attempted to lower the landing gear, and he believed it was down but the collapse upon landing is consistent with it not having reached the fully down and locked position.
Probable cause
An electrical system surge for a reason that could not be determined that resulted in an overvoltage event, internal damage to electronics equipment, smoke in the cockpit, and a gear up landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA079
- Event ID
- 20250116199557
- Case number
- CEN25LA079
- 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: 12db1aca09d842345e4810cca6720605c543944cdd1892436c72442a18dec7fe; retrieved 2026-09-16T19:36:15.012Z.