Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 15, 2022 · Diamond Aircraft Ind DA 62 · N84LT

Dallas, TX

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 15, 2022
Injury Outcomes
No injuries (2 uninjured)
Location
Dallas, TX
Aircraft
Diamond Aircraft Ind DA 62 (2018)
Tail Number
N84LT
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN23LA014

While descending in preparation to fly a visual approach, the pilot lowered the landing gear and contacted the tower controller for landing clearance. During the controller’s response, the pilot reported hearing a “pop” and observed the avionics display screens lose power. A few seconds later, he observed that both engines had lost power. The pilot executed a forced landing on to a road, during which the airplane struck a power line in the descent, and after touchdown, two road signs, which resulted in substantial damage to the right wing. A postaccident examination of the airplane revealed that the electronic control unit (ECU) backup batteries were wired incorrectly (parallel versus series) and the in-line fuses for the backup ECU power system for both engines were blown. The incorrect wiring would have resulted in only 12 volts instead of 24 volts being available which would have resulted in a higher current draw and subsequent blown fuses. According to the airplane’s maintenance records, 4 new ECU battery backup batteries were installed during the annual maintenance inspection about 4 months before the accident. The 1,000 hour/12-month Concorde battery capacitance check was also completed, and the battery had 92% capacitance. It is likely that during this maintenance the batteries were incorrectly rewired in parallel. A review of the aircraft maintenance manual showed that it did not provide a procedure to verify the ECU backup batteries were functioning correctly after replacement. The last step in the ECU back-up battery installation was to run engines and verify that the electrical system operated correctly. However, this step does not verify that the ECU backup batteries were installed correctly and were ready to provide power to the ECUs. In addition, there was no ECU backup battery operational test. If there had been such a test, the improperly connected batteries would have been discovered immediately after replacement. Completing this check on a routine basis would determine if the in-line fuse has blown. Furthermore, the pilot did not have the ability to check for the proper functioning of the ECU batteries before every flight during the before-takeoff checklist. The airplane manufacturer does complete a test of the ECU back-up batteries as part of the production process. Per the airplane’s maintenance records, the main battery was a serviceable one that was installed while maintenance waited for a new battery that was on order. The battery had been installed 23 days before the accident. The airplane had flown about 15 hours from the time the serviceable battery was installed to the accident. The main battery capacitance was tested and found to be 11.04 Amperes-hours (Ah) or 81.2% of rated capacity. The battery capacitance requirement was 85% or better. The loss of main battery power most likely occurred during the landing gear extension when the hydraulic pump turned on, and simultaneous with the radio transmissions. However, during the aircraft and component testing a definitive root cause of the initial power failure could not be determined. Testing could not duplicate the conditions of the flight when the electrical system anomaly occurred or the anomaly itself. With the ECU backup batteries and the alternator relays wired incorrectly, there was no back-up power to the ECU, which resulted in the complete loss of power to both engines and the inability for the engines to restart. While multiple anomalies with the wiring and battery system were documented, a definitive root cause of the initial power failure could not be determined. An electrical system anomaly caused the aircraft electrical system to shutdown and subsequent engine shutdown due to the mis-connected ECU back-up batteries. The testing done could not duplicate the actual conditions of the flight when the electrical system anomaly occurred or the anomaly itself.

NTSB Probable Cause

A total loss of airplane electrical power for undetermined reasons, which resulted in a complete loss of engine power to both engines. Contributing was the worn main battery and the incorrectly wired ECU backup batteries.

Full Narrative

On October 15, 2022, about 1448 central daylight time, a Diamond Aircraft DA62, N84LT, was substantially damaged during a forced landing near the Dallas Executive Airport (RBD), Dallas, Texas. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. A review of ADS-B data revealed that the airplane departed Winston Field Airport (SNK), Snyder, Texas, about 1448, and climbed to a cruise altitude of 11,500 ft mean sea level (msl). On arrival, the pilot descended to fly a visual approach to Runway 13 at RBD, extended the landing gear, and contacted the tower controller for landing clearance. During the controller’s response, the pilot heard a “pop” and observed the avionics display screens lose power. A few seconds later, he observed that both engines had lost power. The pilot executed a forced landing on to a road, during which the airplane struck a power line in the descent, and after touchdown, two road signs, which resulted in substantial damage to the right wing. A review of downloaded engine and flight data indicated the airplane lost electrical power to the avionics system and both engines nearly simultaneously while at 2,000 ft msl and about 5 miles west of RBD. The airplane was equipped with two Austro Engine E4P-C liquid-cooled, in-line four-stroke four-cylinder diesel engines. All engine components are controlled by an electronic engine control unit (ECU) system. Each engine can only be operated with the engine master switch ON. Each engine has its own ECU which receives its electrical power from the alternator when at least one engine is running. When both engines are off, the ECU receives its electrical power from the main battery or the back-up ECU batteries. The engine master switch must be set to ON to activate the engine ECU. To support the alternator electrical power supply to the ECUs in case of a malfunction of the main battery, additional sealed-lead-acid batteries are connected to the left and right engine ECU buses. These batteries are designed to provide 30 minutes of engine operation in case of a complete airplane electrical failure. Both engines may stop if the 30 minutes have elapsed. Postaccident examination of the airplane revealed the backup ECU batteries for both engines had been wired in parallel, rather than in series, and the in-line fuses to the ECU batteries were blown. The main battery capacitance was tested and found to be 11.04 Amperes-hours (Ah), or 81.2% of its rated capacity. The battery capacitance requirement was 85% or better. Additionally, the alternator relays were wired such that the alternator would not disconnect the alternator power from the main electrical system. The relays would cut power to the glow plugs for the respective engines. The Garmin G1000 NXi electronic flight instrument system (EFIS) recorded data indicated that the accident flight had a duration of 1 hour 25 minutes and 49 seconds. The Austo Engine ECUs contained non-volatile memory used to store 16 channels of data signals. The right engine data contained 23 sessions of recording to include the accident flight. The left engine data contained 11 sessions to include the accident flight. However, while the right engine event flight recording had one hour 25 minutes 3 seconds of recording, the left engine data ended earlier and had only 18 minutes and 46 seconds of recording. The ECU right engine data of the event showed the right engine circuitry bus voltage was at 27 volts until 1447:41, when it suddenly dropped to 11.7 volts, after which the recording stopped. Airplane and component testing did not reveal a definitive root cause of the initial power failure. Testing could not duplicate the actual conditions of the flight when the electrical system anomaly occurred or the anomaly itself. According to the airplane’s maintenance records, as part of the annual maintenance inspection on June 24, 2022, the 12-month ECU battery backup replacement check was completed, and 4 new ECU battery backup batteries were installed. The 1000 hour/12-month Concorde battery capacitance check was also completed, and the battery had 92% capacitance. On September 21, 2022, the airplane’s main battery was replaced with a serviceable one as the maintenance facility waited for a new battery that was on order. The airplane had flown about 15 hours from the time the serviceable battery was installed to the accident. A review of the aircraft maintenance manual showed it did not provide a procedure to verify the ECU back-up batteries were functioning correctly after replacement. The last step in the ECU backup battery installation was to run engines and verify that the electrical system operated correctly. However, this step does not verify that the ECU backup batteries were installed correctly and were ready to provide power to the ECUs. In addition, there was no ECU backup battery operational test. Diamond Aircraft issued a service information letter requiring inspection of ECU backup batteries wiring installation on all DA 62 aircraft.

Flight

Event TypeAccident
Event Time14:48 CDT
Nearest AirportDallas Executive Airport (0nm)
Runway13
Runway Length7136 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftDiamond Aircraft Ind DA 62
Tail NumberN84LT
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsAustro Engines · E4P-C · Reciprocating · 180 | Austro Engines · E4P-C · Reciprocating · 180
Seats7

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 60 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind180° @ 11 kt, gusting 20 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F
Altimeter29.93 inHg
Observation Time14:53
Weather SourceWFAC

Appendix: Source Data