37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1685953 |
Time | |
Date | 201909 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | CAK.TRACON |
State Reference | OH |
Aircraft 1 | |
Make Model Name | Amateur/Home Built/Experimental |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | UAV - Unpiloted Aerial Vehicle |
Flight Phase | Cruise |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Commercial Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 37 Flight Crew Total 1291 Flight Crew Type 715 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 150 Vertical 50 |
Narrative:
I was flying at approximately 5;500 feet at about 80 knots airspeed. I was using VFR flight following; was in contact with akron-canton (cak) approach control on 125.50 mhz; and was squawking an assigned transponder code.I passed an object that appeared to be an unmanned aircraft vehicle (uav). The uav was generally spherical in shape and about six to twelve inches in diameter. The uav also appeared to have protrusions or extensions; that could have been rotors and rotor mounts. The uav was generally black; with other color(s). The uav passed less than two hundred feet to my right; and less than fifty feet below. It passed generally parallel to my track of flight. The uav may have been traveling in the same or opposite direction as my track of flight; or it may have been nearly stationary. I did not perceive any relative lateral motion. The total time of observation was less than two seconds.within ten seconds I keyed my microphone; and said 'akron approach; light experimental [tail number];' or nearly identical words to the same effect. There was some delay in establishing communication with the controller who initially repeated my assigned transponder code. I advised the controller that I was already using VFR flight following. When the controller asked the purpose of my transmission; I stated I wished to report being nearly struck by a drone. Subsequently; a controller asked that I telephone [number removed]. I agreed and the rest of the flight proceeded without further incident. After parking the aircraft; I made a few notes; called the number; and made an (audio recorded) report with cak approach control.
Original NASA ASRS Text
Title: Experimental aircraft pilot reported an NMAC with a UAV.
Narrative: I was flying at approximately 5;500 feet at about 80 knots airspeed. I was using VFR Flight Following; was in contact with Akron-Canton (CAK) approach control on 125.50 MHz; and was squawking an assigned transponder code.I passed an object that appeared to be an Unmanned Aircraft Vehicle (UAV). The UAV was generally spherical in shape and about six to twelve inches in diameter. The UAV also appeared to have protrusions or extensions; that could have been rotors and rotor mounts. The UAV was generally black; with other color(s). The UAV passed less than two hundred feet to my right; and less than fifty feet below. It passed generally parallel to my track of flight. The UAV may have been traveling in the same or opposite direction as my track of flight; or it may have been nearly stationary. I did not perceive any relative lateral motion. The total time of observation was less than two seconds.Within ten seconds I keyed my microphone; and said 'Akron Approach; light experimental [tail number];' or nearly identical words to the same effect. There was some delay in establishing communication with the controller who initially repeated my assigned transponder code. I advised the Controller that I was already using VFR flight following. When the Controller asked the purpose of my transmission; I stated I wished to report being nearly struck by a drone. Subsequently; a Controller asked that I telephone [number removed]. I agreed and the rest of the flight proceeded without further incident. After parking the aircraft; I made a few notes; called the number; and made an (audio recorded) report with CAK Approach Control.
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.