A First Officer reported a UAS passing within 10 ft of their aircraft while leveling off for cruise and reported the incident to ATC. No evasive action was taken and the aircraft continued normally.
Synopsis
A First Officer reported a UAS passing within 10 ft of their aircraft while leveling off for cruise and reported the incident to ATC. No evasive action was taken and the aircraft continued normally.
Narrative
While still in BOS Class B NE of BVY at 5;000 ft. I was getting the aircraft into a cruise configuration with the autopilot engaged. I looked up from what I was doing and happened to notice a blue drone like object out of my left periphery. It quickly passed inside of our wingtip and no more than 10 ft. over the top of the wing. I was unable to disengage the autopilot and take any meaningful action because there was very little time to react. Upon realizing that the drone passed and did not cause any damage to our aircraft; I immediately reported it to Boston Approach. I provided the controller with the same details and that it was a neon blue drone with LED lights. Once I was handed off to Portland Approach; Boston was talking to Portland over the landline for details regarding any evasive action I took and if I was planning to file a Near Miss Mid Air Collision report which I am in the process of completing. The flight continued without further incident and landed safely in ZZZ. Cause - The drone operator was flying a drone too high in airspace he or she should not have been in and ATC was not aware of the drone activity prior to the encounter.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.