20230330007369A

Accident · Destroyed

FAA accident report · Aircraft · Detroit, MI · March 30, 2023

Date
March 30, 2023 · 16:10 local
Place
Detroit, MI
Phase of flight
Cruise/Level Flight
Damage
Destroyed
Aircraft
NONE
People aboard
0
Fatal injuries
0
Other injuries
0

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

•UAS fa registration number. FA3RTCRY4W

•UAS make: dji

•UAS model: matrice 300RTK

•UAS serial number: 1ZNBK5900C007L

•Remote pilot certificate number. privacy data omitted

•Frequency being used by the operator (5.7 ghz, & 2.4 ghz optimized)

•UAS weight 7.2KG as equiped with zenmuse L1 lidar imu/camera

•Operator was performing part 107 flight over construction site for the purpose of autonomous grid mapping and photo imagery. Altitude of 170’ AGL set for autonomous flight. Vo lost vlos and operator lost vlos. UAS had return to home function set in case of lost link to climb to 300’ AGL then return direct to home. UAS did not perform lost link return to home. Operator tried manual flight procedures but UAS did not respond. Operator control station tracked UAS to final resting location at privacy data omitted. Operator located on outer drive west approximately 850 feet northeast from accident site.

•UAS does track UAS flight hours but UAS destroyed in accident and no data retrivable.

•Accident damage: property damage was greater than $500, licensed contractor gave (UAS owner) estimate to repair damaged roof of $4600.00 usd.

•Operator during phone interview said in his opinion that he thought an internal circuit board failed as control station continued to show UAS location but did not respond to lost link setting or operator input.

Statement below from accident report details reference number: uasa-2023-00009

"Initial flight mission preparation was normal. Equipment setup and initialization went as standard procedure calls. The "drone pre-flight check list" that ohm advisors uses to correctly setup all flights was completed. This was the 2nd area in which this suas was used on March 30th, 2023. Both areas had separate ohm advisors check lists completed. The suas was placed in an open and clear area and started. Prior to taking off, all manufacturer checklist items were completed without issues. If one of these fields is invalid, it will not allow the suas to takeoff. Over the course of this day, the manufacturer check list was successfully completed 5 times. This fight was the final flight of the day and was to take 25 minutes to complete. 15 minutes into the flight the suas vlos was lost by the vo. The vo called out to the operator asking if they had vlos and they did not. Concurrent, the operator stated the remote controller lost connection with the suas. Both the operator and vo proceeded to the last known location of the suas. The remote controller tracks the suas for the duration of the flight and uses a map to show position over the ground. Arriving at the last known location, a home owner was holding the suas airframe which was confirmed to be the lost aircraft. The Detroit police department's 6th precinct was contacted and responded. They deemed it was on private property and thus a civil matter. No police report was made due to this reason. The event was catalogued by the officer as #202308903315. The suas impacted the home owner's roof causing damage. Extent of damage is currently under evaluation. (UAS owner) is investigating the incident to determine possible causes of failure and corrective measures to be implemented on further flights."

As the FAA filed it

•UAS FA REGISTRATION NUMBER. FA3RTCRY4W

•UAS MAKE: DJI

•UAS MODEL: MATRICE 300RTK

•UAS SERIAL NUMBER: 1ZNBK5900C007L

•REMOTE PILOT CERTIFICATE NUMBER. ^PRIVACY DATA OMITTED^

•FREQUENCY BEING USED BY THE OPERATOR (5.7 GHZ, & 2.4 GHZ OPTIMIZED)

•UAS WEIGHT 7.2KG AS EQUIPED WITH ZENMUSE L1 LIDAR IMU/CAMERA

•OPERATOR WAS PERFORMING PART 107 FLIGHT OVER CONSTRUCTION SITE FOR THE PURPOSE OF AUTONOMOUS GRID MAPPING AND PHOTO IMAGERY. ALTITUDE OF 170’ AGL SET FOR AUTONOMOUS FLIGHT. VO LOST VLOS AND OPERATOR LOST VLOS. UAS HAD RETURN TO HOME FUNCTION SET IN CASE OF LOST LINK TO CLIMB TO 300’ AGL THEN RETURN DIRECT TO HOME. UAS DID NOT PERFORM LOST LINK RETURN TO HOME. OPERATOR TRIED MANUAL FLIGHT PROCEDURES BUT UAS DID NOT RESPOND. OPERATOR CONTROL STATION TRACKED UAS TO FINAL RESTING LOCATION AT ^PRIVACY DATA OMITTED^. OPERATOR LOCATED ON OUTER DRIVE WEST APPROXIMATELY 850 FEET NORTHEAST FROM ACCIDENT SITE.

•UAS DOES TRACK UAS FLIGHT HOURS BUT UAS DESTROYED IN ACCIDENT AND NO DATA RETRIVABLE.

•ACCIDENT DAMAGE: PROPERTY DAMAGE WAS GREATER THAN $500, LICENSED CONTRACTOR GAVE (UAS OWNER) ESTIMATE TO REPAIR DAMAGED ROOF OF $4600.00 USD.

•OPERATOR DURING PHONE INTERVIEW SAID IN HIS OPINION THAT HE THOUGHT AN INTERNAL CIRCUIT BOARD FAILED AS CONTROL STATION CONTINUED TO SHOW UAS LOCATION BUT DID NOT RESPOND TO LOST LINK SETTING OR OPERATOR INPUT.

STATEMENT BELOW FROM ACCIDENT REPORT DETAILS REFERENCE NUMBER: UASA-2023-00009

"INITIAL FLIGHT MISSION PREPARATION WAS NORMAL. EQUIPMENT SETUP AND INITIALIZATION WENT AS STANDARD PROCEDURE CALLS. THE "DRONE PRE-FLIGHT CHECK LIST" THAT OHM ADVISORS USES TO CORRECTLY SETUP ALL FLIGHTS WAS COMPLETED. THIS WAS THE 2ND AREA IN WHICH THIS SUAS WAS USED ON MARCH 30TH, 2023. BOTH AREAS HAD SEPARATE OHM ADVISORS CHECK LISTS COMPLETED. THE SUAS WAS PLACED IN AN OPEN AND CLEAR AREA AND STARTED. PRIOR TO TAKING OFF, ALL MANUFACTURER CHECKLIST ITEMS WERE COMPLETED WITHOUT ISSUES. IF ONE OF THESE FIELDS IS INVALID, IT WILL NOT ALLOW THE SUAS TO TAKEOFF. OVER THE COURSE OF THIS DAY, THE MANUFACTURER CHECK LIST WAS SUCCESSFULLY COMPLETED 5 TIMES. THIS FIGHT WAS THE FINAL FLIGHT OF THE DAY AND WAS TO TAKE 25 MINUTES TO COMPLETE. 15 MINUTES INTO THE FLIGHT THE SUAS VLOS WAS LOST BY THE VO. THE VO CALLED OUT TO THE OPERATOR ASKING IF THEY HAD VLOS AND THEY DID NOT. CONCURRENT, THE OPERATOR STATED THE REMOTE CONTROLLER LOST CONNECTION WITH THE SUAS. BOTH THE OPERATOR AND VO PROCEEDED TO THE LAST KNOWN LOCATION OF THE SUAS. THE REMOTE CONTROLLER TRACKS THE SUAS FOR THE DURATION OF THE FLIGHT AND USES A MAP TO SHOW POSITION OVER THE GROUND. ARRIVING AT THE LAST KNOWN LOCATION, A HOME OWNER WAS HOLDING THE SUAS AIRFRAME WHICH WAS CONFIRMED TO BE THE LOST AIRCRAFT. THE DETROIT POLICE DEPARTMENT'S 6TH PRECINCT WAS CONTACTED AND RESPONDED. THEY DEEMED IT WAS ON PRIVATE PROPERTY AND THUS A CIVIL MATTER. NO POLICE REPORT WAS MADE DUE TO THIS REASON. THE EVENT WAS CATALOGUED BY THE OFFICER AS #202308903315. THE SUAS IMPACTED THE HOME OWNER'S ROOF CAUSING DAMAGE. EXTENT OF DAMAGE IS CURRENTLY UNDER EVALUATION. (UAS OWNER) IS INVESTIGATING THE INCIDENT TO DETERMINE POSSIBLE CAUSES OF FAILURE AND CORRECTIVE MEASURES TO BE IMPLEMENTED ON FURTHER FLIGHTS."