# Incident 20160426003759I: Pittsburgh, PA, April 26, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 26, 2016, 20:00 local time
- Place: Pittsburgh, PA
- Damage: No damage
- Phase of flight: Landing: Approach
- Location: 40.4406° N, 79.9959° W: Placed by OpenAirDocs: center of Pittsburgh, PA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.4406&lon=-79.9959&mi=10
- Aircraft: NONE (not matched to a registry record)
- Reported engine: N/A N/A
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot flight hours: 30 total, 30 in this make and model, 2 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160426003759I

## Narrative

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

ON WEDNESDAY, APRIL 27, 2016 AT 1017 HOURS S/C BERNARDING WAS DISPATCHED TO BEELER ST TO MEET A PITTSBURGH BUREAU OF POLICE OFFICER REGARDING A DRONE/UAS THAT WAS RECOVERED IN A YARD.

OFFICER ^PRIVACY DATA OMITTED^ RESPONDED TO ^PRIVACY DATA OMITTED^ AND MET OFFICER WHITE WHO STATED THAT HE WAS CALLED TO THE HOME FOR A FOUND DRONE. THE HOME OWNER WAS NOT HOME AT THE TIME THE POLICE ARRIVED. OFFICER ^PRIVACY DATA OMITTED^ TOOK THE DRONE/UAS TO THE CARNEGIE MELLON UNIVERSITY ROBOTICS LAB AT GATES HALL. THE STUDENTS SAID IT WAS NOT THEIR AIRCRAFT.

THE DRONE/UAS HAD A FAA IDENTIFICATION NUMBER LOCATED ON THE UNIT. THE NUMBER IS ^PRIVACY DATA OMITTED^.

THE OWNER WAS IDENTIFIED AS ^PRIVACY DATA OMITTED^.

I CALLED ^PRIVACY DATA OMITTED^ ON THE PHONE TO DISCUSS THE INCIDENT THAT OCCURRED ON APRIL 27, 2016 AT 8:00PM LOCAL TIME. ^PRIVACY DATA OMITTED^ STATED THAT HE IS RECREATIONAL DRONE/UAS PILOT AND DOES NOT HOLD AN AIRMAN CERTIFICATE. HOWEVER, HE HAS HOLDS A SMALL UAS CERTIFICATE OF REGISTRATION, THE NUMBER IS ^PRIVACY DATA OMITTED^ AND EXPIRES 01/09/2019.

^PRIVACY DATA OMITTED^ STATED THAT HE WAS FLYING THE  TRICOPTER AT 15 METERS IN THE AIR AND THE REMOTE CONTROL WAS CONTROLLING THE UAS PROPERLY. ABOUT ONE MINUTE LATER, THE UAS WAS CARRIED AWAY BY THE WIND AT THE SAME ALTITUDE AND NO CHANGES APPLIED TO THE CONTROLLER WERE EFFECTIVE. THE UAS CONTINUED TO FLY ON A SOUTHERLY HEADING OUT OF SIGHT. ^PRIVACY DATA OMITTED^ STATED THAT HE LOOKED FOR THE UAS FOR HOURS AND COULD NOT LOCATE IT.

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.