Narrative:

Approximately 7-10 minutes prior to the encounter with the uav; the autopilot and oil pressure sensor began to malfunction. After joining V146 at pvd; a request was made to providence approach for deviation and landing so the problems could be addressed. After receiving the initial instruction to depart V146; descend from 8;000 to 4;000; and turn to a heading of 040; upon breaking out of a small cloud layer at approximately 7;800 ft the uav passed very closely by the left wing. It was immediately necessary to increase my rate of turn to the right to increase the distance between my plane and the uav. Given the occasional IMC while flying in and out of cloud layers; it was impossible to see and avoid the uav at any point prior. With our flight path; speed; and changing direction; it was difficult to ascertain the speed and direction at which the uav was traveling given the short duration of the encounter; but it appeared as though it may have been traveling in a southerly direction. The uav was not of a style with wings or a tail; but rather a drum-shaped version grey in color. This is clearly a case that highlights a severe deficiency in the safe operation of the NAS. There was no way for ATC or the equipment in the aircraft to sense the presence of the uav; and there was most certainly no way to see and avoid it while in IMC. Since this encounter happened at an altitude that was less than 10;000 ft above class C airspace; an operating transponder was a mandatory piece of equipment. Uav's and their operators should at least be held to the same standards for certification and required equipment as all other aircraft and pilots when operating at such altitudes.

Google
 

Original NASA ASRS Text

Title: SR22 pilot reports encountering a UAV at 7;800 FT near PVD. The UAV was of a single or coaxial rotor design.

Narrative: Approximately 7-10 minutes prior to the encounter with the UAV; the autopilot and oil pressure sensor began to malfunction. After joining V146 at PVD; a request was made to Providence Approach for deviation and landing so the problems could be addressed. After receiving the initial instruction to depart V146; descend from 8;000 to 4;000; and turn to a heading of 040; upon breaking out of a small cloud layer at approximately 7;800 FT the UAV passed very closely by the left wing. It was immediately necessary to increase my rate of turn to the right to increase the distance between my plane and the UAV. Given the occasional IMC while flying in and out of cloud layers; it was impossible to see and avoid the UAV at any point prior. With our flight path; speed; and changing direction; it was difficult to ascertain the speed and direction at which the UAV was traveling given the short duration of the encounter; but it appeared as though it may have been traveling in a southerly direction. The UAV was not of a style with wings or a tail; but rather a drum-shaped version grey in color. This is clearly a case that highlights a severe deficiency in the safe operation of the NAS. There was no way for ATC or the equipment in the aircraft to sense the presence of the UAV; and there was most certainly no way to see and avoid it while in IMC. Since this encounter happened at an altitude that was less than 10;000 FT above Class C airspace; an operating transponder was a mandatory piece of equipment. UAV's and their operators should at least be held to the same standards for certification and required equipment as all other aircraft and pilots when operating at such altitudes.

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.