# Incident 20231012019189I: Tucson, AZ, October 12, 2023

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 12, 2023, 07:30 local time
- Place: Tucson, AZ
- Damage: No damage
- Phase of flight: Maneuver
- Location: 32.2217° N, 110.9265° W: Placed by OpenAirDocs: center of Tucson, AZ, within about 9 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.2217&lon=-110.9265&mi=10
- Aircraft: NONE (not matched to a registry record)
- People aboard: 0
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20231012019189I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

UAS REGISTRATION # IS FA3CHWLFMH (INFO DOES NOT FIT IN BLOCK 13).

DESCRIPTION OF THE DEVIATION:

ON OCT. 12, 2023, AT APPROXIMATELY 07:30 LCL, A REMOTE PILOT WAS OPERATING A UAS (IFLIGHT NAZGUL EVOQUE V2) IN TUCSON MOUNTAIN PARK OVER GATE PASS RD. THE REMOTE PILOT HAS HIS OWN COMPANY AND CONTRACTING FOR ^PRIVACY DATA OMITTED^ TO EVENTUALLY FILM, “IN FLIGHT”, MITSUBISHI HEAVY EQUIPMENT. THE REMOTE PILOT WAS DOING A “DEMO RUN” TO TEST THE EQUIPMENT (UAS WAS ACQUIRED THE WEEK PRIOR) AND WOULD FLY AROUND A MOVING TRUCK DRIVING ON GATE PASS RD (THE ^PRIVACY DATA OMITTED^DRIVER OF THE TRUCK WAS WILLING TO PARTICIPATE IN THIS “DEMO RUN”).

THE REMOTE PILOT WAS ON A HILLSIDE WHERE HE COULD SEE THE WHOLE LENGTH OF THE ROAD. HE HAD A VISUAL OBSERVER NEXT TO HIM. WHILE FLYING THE UAS AROUND THE TRUCK, THE REMOTE PILOT AND OBSERVER FAILED TO SEE A SMALL BRANCH STICKING OUT OF A BUSH (BUSH LOCATED A HUNDRED YARDS AWAY OR SO). THE UAS HIT THE BRANCH AND WAS THROWN ONTO THE HOOD OF THE TRUCK, LEADING TO SCRATCHES AND DENTS. THE UAS DID NOT SUSTAIN ANY DAMAGE. NO INJURIES WERE REPORTED.

THE PILOT REPORTED THE EVENT IN ACCORDANCE WITH §107.9 THROUGH THE FAA’S DRONEZONE WEBPAGE.

CAUSAL/CONTRIBUTING FACTORS:

THE REMOTE PILOT HAD SCOUTED AND SURVEYED THE LOCATION PRIOR TO STARTING OPERATIONS. BEING THAT UAS OPERATIONS CAN TAKE PLACE IN RANDOM LOCATIONS WHERE THE ENVIRONMENT IS FLUID, AND AT TIMES, UNCONTROLLABLE (COMPARED TO AN AIRPORT, AS AN EXAMPLE), THE REMOTE PILOT (AND VISUAL OBSERVER) HAD NOT SEEN THE SMALL BRANCH OUT OF THIS BUSH. THIS UAS IS CLASSIFIED AS “SMALL” AND THEREFORE VULNERABLE TO OTHER SMALL OBJECTS IF IT COMES IN CONTACT.

THE REMOTE PILOT DELAYED HIS REPORT TO THE FAA AS HE WAS UNCERTAIN IF THE DAMAGE TO THE VEHICLE MET THE $500 COST OF REPAIR THRESHOLD. ONCE HE RECEIVED A QUOTE FROM A REPAIR SHOP, WHICH WAS GREATER THAN $500, HE REPORTED THE EVENT.

RECOMMENDATIONS FOR SYSTEMIC CORRECTIVE ACTION TO REDUCE RISK OF FUTURE OCCURRENCE:

•	THE INVESTIGATING ASI PERFORMED THE COMPLIANCE ACTION OF COUNSELING AND DISCUSSED THE APPLICABLE REGULATIONS (TO INCLUDE 14 CFR §107.23 AND §107.145), ROOT CAUSE ANALYSIS, AND MITIGATING STRATEGIES TO PREVENT REOCCURRENCE.

•	THE REMOTE PILOT PERFORMED HIS OWN RCA AND BRIEFED THE ASI.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.