20240808020179I

Incident · Minor damage

FAA incident report · Aircraft · Elgin, IL · August 8, 2024

Date
August 8, 2024 · 15:07 local
Place
Elgin, IL
Phase of flight
Hover/Holding
Damage
Minor damage
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.

On 08/08/24 at approx. 1940HRS. Rpic was conducting flight training in Elgin, IL. The rpic stated that he checked the weather and wind speed which was reported as 317 degrees at 9MPH and the sky was clear. The rpic had intended to fly the dji matrice 30T. Rpic snow utilized the dronesense application for flight authorization and conducted the preflight checklist through dronesense. The rpic noted that just prior to this flight, the UAS had a previous loss of signal from the controller which initiated an automatic return to home within the system. The rpic stated that the disconnect was due to a battery malfunction from the UAS batteries marked "1". The rpic reported to have performed a hot swap on the batteries after the UAS landed and that the drone appeared to function normally. At 2007HRS. The rpic reported that he launched the dji matirce 30T #1 from the westside driveway of the incident location and hovered at approx. 57FT AGL for approx. 30 seconds. The rpic stated that while hovering he performed an inspection of the controller to make sure everything was functioning properly, rpic reported that the UAS systems were functioning properly. The rpic ascended up to approx. 87FT AGL and flew to the front of the incident location, then descended down to approx. 17FT. AGL on the eastside of the location and came to a hover. The rpic reported that he was standing beneath and to the left of the hovering UAS. The drone was facing away from the operator and the camera's gimbal was also facing forward. The drone was in a hover approx. 30FT from a tree. The rpic reportedly looked down at the controller to focus the camera on the street for approx. 10 seconds. The rpic reportedly heard the drone moving which caused him to look up due to not having moved the flight controls and only making adjustments to the camera gimbals. The drone then made impact with a tree branch. The rpic stated that, "this happened instantaneously and I tried to fly the drone out of the tree, but it continued in the opposite direction that I tried to move it. I had no control of the drone. The drone continued into the tree then crashed on top of a parked red in color 2002 honda crv suv." The vehicle was unoccupied and parked in a residential driveway in Elgin, IL. The impact from the UAS caused damage to the top of the vehicle, breaking the windshield, and damaging the front driver's side quarter panel. The drone crashed in the driveway approx. 4 feet from the vehicle and had two broken arms. The entire flight was alleged to have been approx. 2 mins. From takeoff up to the point of impact. The rpic wanted it to be noted that he reviewed the dronesense flight data which was recorded as flight "fiulp" under the agency' head remote pilot even though the rpic involved was flying the drone. Rpic claimed that he reviewed the recorded flight and it showed the controller approx. 70FT. From the drone. Rpic snow indicated that he was approx. 30FT. From the drone when the crash occurred.

In the rpic's statement it was mentioned that there were issues with the UAS systems and iaw CFR 107.15B, no person may continue flight of the small unmanned aircraft when he or she knows or has reason to know that the small unmanned aircraft system is no longer in a condition for safe operation.

A written counselling with be drafted and issued to remind the rpic of the importance of having perfromed the correct preflight procedures and system checks.

As the FAA filed it

ON 08/08/24 AT APPROX. 1940HRS. RPIC WAS CONDUCTING FLIGHT TRAINING IN ELGIN, IL. THE RPIC STATED THAT HE CHECKED THE WEATHER AND WIND SPEED WHICH WAS REPORTED AS 317 DEGREES AT 9MPH AND THE SKY WAS CLEAR. THE RPIC HAD INTENDED TO FLY THE DJI MATRICE 30T. RPIC SNOW UTILIZED THE DRONESENSE APPLICATION FOR FLIGHT AUTHORIZATION AND CONDUCTED THE PREFLIGHT CHECKLIST THROUGH DRONESENSE. THE RPIC NOTED THAT JUST PRIOR TO THIS FLIGHT, THE UAS HAD A PREVIOUS LOSS OF SIGNAL FROM THE CONTROLLER WHICH INITIATED AN AUTOMATIC RETURN TO HOME WITHIN THE SYSTEM. THE RPIC STATED THAT THE DISCONNECT WAS DUE TO A BATTERY MALFUNCTION FROM THE UAS BATTERIES MARKED "1". THE RPIC REPORTED TO HAVE PERFORMED A HOT SWAP ON THE BATTERIES AFTER THE UAS LANDED AND THAT THE DRONE APPEARED TO FUNCTION NORMALLY. AT 2007HRS. THE RPIC REPORTED THAT HE LAUNCHED THE DJI MATIRCE 30T #1 FROM THE WESTSIDE DRIVEWAY OF THE INCIDENT LOCATION AND HOVERED AT APPROX. 57FT AGL FOR APPROX. 30 SECONDS. THE RPIC STATED THAT WHILE HOVERING HE PERFORMED AN INSPECTION OF THE CONTROLLER TO MAKE SURE EVERYTHING WAS FUNCTIONING PROPERLY, RPIC REPORTED THAT THE UAS SYSTEMS WERE FUNCTIONING PROPERLY. THE RPIC ASCENDED UP TO APPROX. 87FT AGL AND FLEW TO THE FRONT OF THE INCIDENT LOCATION, THEN DESCENDED DOWN TO APPROX. 17FT. AGL ON THE EASTSIDE OF THE LOCATION AND CAME TO A HOVER. THE RPIC REPORTED THAT HE WAS STANDING BENEATH AND TO THE LEFT OF THE HOVERING UAS. THE DRONE WAS FACING AWAY FROM THE OPERATOR AND THE CAMERA'S GIMBAL WAS ALSO FACING FORWARD. THE DRONE WAS IN A HOVER APPROX. 30FT FROM A TREE. THE RPIC REPORTEDLY LOOKED DOWN AT THE CONTROLLER TO FOCUS THE CAMERA ON THE STREET FOR APPROX. 10 SECONDS. THE RPIC REPORTEDLY HEARD THE DRONE MOVING WHICH CAUSED HIM TO LOOK UP DUE TO NOT HAVING MOVED THE FLIGHT CONTROLS AND ONLY MAKING ADJUSTMENTS TO THE CAMERA GIMBALS. THE DRONE THEN MADE IMPACT WITH A TREE BRANCH. THE RPIC STATED THAT, "THIS HAPPENED INSTANTANEOUSLY AND I TRIED TO FLY THE DRONE OUT OF THE TREE, BUT IT CONTINUED IN THE OPPOSITE DIRECTION THAT I TRIED TO MOVE IT. I HAD NO CONTROL OF THE DRONE. THE DRONE CONTINUED INTO THE TREE THEN CRASHED ON TOP OF A PARKED RED IN COLOR 2002 HONDA CRV SUV." THE VEHICLE WAS UNOCCUPIED AND PARKED IN A RESIDENTIAL DRIVEWAY IN ELGIN, IL. THE IMPACT FROM THE UAS CAUSED DAMAGE TO THE TOP OF THE VEHICLE, BREAKING THE WINDSHIELD, AND DAMAGING THE FRONT DRIVER'S SIDE QUARTER PANEL. THE DRONE CRASHED IN THE DRIVEWAY APPROX. 4 FEET FROM THE VEHICLE AND HAD TWO BROKEN ARMS. THE ENTIRE FLIGHT WAS ALLEGED TO HAVE BEEN APPROX. 2 MINS. FROM TAKEOFF UP TO THE POINT OF IMPACT. THE RPIC WANTED IT TO BE NOTED THAT HE REVIEWED THE DRONESENSE FLIGHT DATA WHICH WAS RECORDED AS FLIGHT "FIULP" UNDER THE AGENCY' HEAD REMOTE PILOT EVEN THOUGH THE RPIC INVOLVED WAS FLYING THE DRONE. RPIC CLAIMED THAT HE REVIEWED THE RECORDED FLIGHT AND IT SHOWED THE CONTROLLER APPROX. 70FT. FROM THE DRONE. RPIC SNOW INDICATED THAT HE WAS APPROX. 30FT. FROM THE DRONE WHEN THE CRASH OCCURRED.

IN THE RPIC'S STATEMENT IT WAS MENTIONED THAT THERE WERE ISSUES WITH THE UAS SYSTEMS AND IAW CFR 107.15B, NO PERSON MAY CONTINUE FLIGHT OF THE SMALL UNMANNED AIRCRAFT WHEN HE OR SHE KNOWS OR HAS REASON TO KNOW THAT THE SMALL UNMANNED AIRCRAFT SYSTEM IS NO LONGER IN A CONDITION FOR SAFE OPERATION.

A WRITTEN COUNSELLING WITH BE DRAFTED AND ISSUED TO REMIND THE RPIC OF THE IMPORTANCE OF HAVING PERFROMED THE CORRECT PREFLIGHT PROCEDURES AND SYSTEM CHECKS.