37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1744052 |
Time | |
Date | 202005 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | DPA.Airport |
State Reference | IL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Other VFR Traffic Pattern |
Route In Use | None |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | UAV - Unpiloted Aerial Vehicle |
Person 1 | |
Function | Local Trainee |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Inflight Event / Encounter Other / Unknown |
Narrative:
Aircraft X was on short final when they reported a possible uas at about 1000 feet; 200 to 300 feet over the train tracks on approach end of the runway. The pilot did not report proximity; but did not sound concerned and continued in the pattern. A P28A following was given an advisory about the reported uas; but could not confirm a sighting. Both aircraft were switched to a different runway to prevent them from overflying the area until police could investigate. Notify authorities immediately; especially when in close proximity to a critical phase of flight; such as approach or departure. From notification by the pilot until the controller in charge called was about 10 to 15 minutes due to trying to get a visual sighting of the uas.
Original NASA ASRS Text
Title: A Tower Local Control trainee reported an aircraft reported sighting a drone in the Tower airspace.
Narrative: Aircraft X was on short final when they reported a possible UAS at about 1000 feet; 200 to 300 feet over the train tracks on approach end of the runway. The pilot did not report proximity; but did not sound concerned and continued in the pattern. A P28A following was given an advisory about the reported UAS; but could not confirm a sighting. Both aircraft were switched to a different runway to prevent them from overflying the area until police could investigate. Notify authorities immediately; especially when in close proximity to a critical phase of flight; such as approach or departure. From notification by the pilot until the Controller in Charge called was about 10 to 15 minutes due to trying to get a visual sighting of the UAS.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.