# Accident 20240831011519A: Tempe, AZ, August 31, 2024

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 31, 2024, 09:30 local time
- Place: Tempe, AZ
- Damage: Destroyed
- Phase of flight: Hover/Holding
- Location: 33.4148° N, 111.9093° W: Placed by OpenAirDocs: center of Tempe, AZ, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.4148&lon=-111.9093&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/20240831011519A

## Narrative

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

DESCRIPTION OF ACCIDENT:

ON AUGUST 31, 2024, AT APPROXIMATELY 09:30 LCL, A REMOTE PILOT WAS OPERATING AN AQUILINE DRONES UAS PERFORMING A WINDOW WASHING OPERATION OF A 9-STORY BUILDING LOCATED AT 1033 W. ROOSEVELT WAY, TEMPE, AZ, 85288. THE REMOTE PILOT WAS “MANUALLY FLYING” THE UAS AND HAD A VISUAL OBSERVER.

AFTER THE UAS BEING AIRBORNE “FOR APPROXIMATELY 18-20 MINUTES”, THE REMOTE PILOT STARTED HIS DESCENT TO LAND HAVING A VOLTAGE OF “43.5+”. THE UAS SUDDENLY STOPPED RESPONDING TO THE REMOTE PILOT’S COMMANDS AND FLEW DIRECTLY INTO A WINDOW OF THE 7TH FLOOR OF THE BUILDING, BREAKING THE ARMS AND THE PROPELLERS. THE UAS DROPPED ONTO A METAL PANEL LOCATED NEAR THE 3RD FLOOR, LIGHTLY DENTING THE PANEL, BEFORE CRASHING DOWN TO THE GROUND. THIS CAUSED “A COMPLETE LOSS OF [THE] DRONE” ACCORDING TO THE REMOTE PILOT’S REPORT.

AFTER INTERVIEWING THE REMOTE PILOT, HE STATED THE EXTENT OF THE PROPERTY DAMAGE (THE METAL PANEL) WAS JUST UNDER $10,000 (HE STATED HE THINKS IT WOULD BE MOSTLY LABOR COST).

CAUSAL/CONTRIBUTING FACTORS:

DURING THE INTERVIEW, THE REMOTE PILOT STATED THIS UAS STARTS FLIGHT OPERATIONS WITH THE BATTERY AT ABOUT 51V. HIS PROCEDURE IS TO LAND THE UAS AT 44V. THE RTL (RETURN TO LAND) MODE ACTIVATES AROUND 42V, AND THE UAS GOES INTO “CRITICAL MODE” AT 41V.

THE PILOT STATED THE BATTERY LASTS “AT LEAST 25 MINUTES”.

THE REMOTE PILOT STATED THE UAS WAS SENT BACK TO THE MANUFACTURER TO DOWNLOAD FLIGHT DATA AND DETERMINE IF THERE WERE ANY SOFTWARE ISSUES WITH THE UAS. AT THIS TIME, THE ISSUE APPEARS TO BE WITH THE UAS BUT THERE IS NOT ENOUGH INFORMATION AVAILABLE TO DETERMINE THE CAUSE OF THE ACCIDENT. NO FURTHER ACTIONS ARE RECOMMENDED. THIS REPORT WILL BE UPDATED IF FURTHER INFORMATION IS RECEIVED FROM THE MANUFACTURER OR REMOTE PILOT.

UAS REGISTRATION #: FA33KCMM4Y. UAS MAKE/MODEL: ^PRIVACY DATA OMITTED^; SERIAL #: AD2505-10023. REMOTE PILOT CERT. #: ^PRIVACY DATA OMITTED^

## NTSB investigation

None matched to this report by aircraft and date. Search the NTSB's own records: https://data.ntsb.gov/carol-main-public/basic-search

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.