![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1547742 |
| Time | |
| Date | 201805 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | WVI.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Descent |
| Route In Use | Direct |
| Flight Plan | None |
| Aircraft 2 | |
| Make Model Name | UAV - Unpiloted Aerial Vehicle |
| Operating Under FAR Part | Other 107 |
| Flight Phase | Cruise |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Commercial Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 25 Flight Crew Total 2500 Flight Crew Type 1500 |
| Events | |
| Anomaly | Conflict NMAC |
| Miss Distance | Horizontal 50 Vertical 100 |
Narrative:
While flying to wvi and still talking to norcal after exiting sfo class B; a silver drone passed about 50 feet left of my plane and about 100 feet below. I was at 4;500 feet on a heading of about 140. I reported the incident to the norcal controller who then asked a series of questions with lots of interruptions to talk to other traffic. He was still getting information from me when I entered the pattern at wvi. There was considerable traffic at wvi including parachute jumpers and a meridian with minimum fuel. I didn't switch to the wvi unicom until after I had entered a right downwind for runway 20 because I was still providing drone information to the controller. I mistakenly entered a right downwind instead of a standard left downwind pattern. It didn't create any conflicts; but was not correct. I should have stayed at cruising altitude and completed my involvement with the controller before entering the pattern. I allowed myself to be very distracted and was way behind the plane. The illegal drone and near miss was the primary contributing factor. There has to be a way to control the drone operators.
Original NASA ASRS Text
Title: Pilot reported having a NMAC with a drone and subsequently being distracted during the entry to traffic pattern at WVI.
Narrative: While flying to WVI and still talking to NorCal after exiting SFO Class B; a silver drone passed about 50 feet left of my plane and about 100 feet below. I was at 4;500 feet on a heading of about 140. I reported the incident to the NorCal Controller who then asked a series of questions with lots of interruptions to talk to other traffic. He was still getting information from me when I entered the pattern at WVI. There was considerable traffic at WVI including parachute jumpers and a Meridian with minimum fuel. I didn't switch to the WVI UNICOM until after I had entered a right downwind for Runway 20 because I was still providing drone information to the controller. I mistakenly entered a right downwind instead of a standard left downwind pattern. It didn't create any conflicts; but was not correct. I should have stayed at cruising altitude and completed my involvement with the controller before entering the pattern. I allowed myself to be very distracted and was way behind the plane. The illegal drone and near miss was the primary contributing factor. There has to be a way to control the drone operators.
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.