37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1501117 |
Time | |
Date | 201712 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | LAS.Airport |
State Reference | NV |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | UAV - Unpiloted Aerial Vehicle |
Operating Under FAR Part | Other 107 |
Flight Phase | Cruise |
Person 1 | |
Function | Instructor Pilot Not Flying |
Qualification | Flight Crew Commercial Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 181 Flight Crew Total 864 Flight Crew Type 498 |
Events | |
Anomaly | Conflict NMAC Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 150 Vertical 0 |
Narrative:
The problem was a near mid air collision with small drone at 6500 MSL that appeared to be moving southerly while my airplane was flying a magnetic heading of 200 approximately. Our lateral separation was between 150-200 feet. We were in the immediate vicinity of las; almost directly above the approach end of runway 26L. The drone was yellow in color and circular; at most 3 feet in diameter; and did not appear fixed wing. It appeared to have some kind of design/camera at its center. We were receiving radar vectors from las vegas TRACON. I was scanning visually while my student was under the view limiting device. We made no evasive action; there was merely a second between the time I saw the drone and it's passing of our position. I queried las vegas approach if there was any drone activity in the area; they responded there was not; I then proceeded to describe the situation; to which they asked questions regarding the drone's altitude and flight path; and prior to our hand off they said they had made a report. This near mid air collision was no fault of las vegas approach or my own; rather the drone operator who violated the airspace.
Original NASA ASRS Text
Title: C172 flight instructor reported a NMAC with a UAV at 6500 in the vicinity of LAS airport.
Narrative: The problem was a near mid air collision with small drone at 6500 MSL that appeared to be moving southerly while my airplane was flying a magnetic heading of 200 approximately. Our lateral separation was between 150-200 feet. We were in the immediate vicinity of LAS; almost directly above the approach end of Runway 26L. The drone was yellow in color and circular; at most 3 feet in diameter; and did not appear fixed wing. It appeared to have some kind of design/camera at its center. We were receiving radar vectors from Las Vegas TRACON. I was scanning visually while my student was under the view limiting device. We made no evasive action; there was merely a second between the time I saw the drone and it's passing of our position. I queried Las Vegas Approach if there was any drone activity in the area; they responded there was not; I then proceeded to describe the situation; to which they asked questions regarding the drone's altitude and flight path; and prior to our hand off they said they had made a report. This near mid air collision was no fault of Las Vegas Approach or my own; rather the drone operator who violated the airspace.
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.