Part 107 UAS pilot reported an airborne conflict with a low flying helicopter. UAS pilot landed the drone when the helicopter came into view.

Narrative

On Day 0 at approximately XA20; a mapping UAS mission was conducted nearby Interstate 95. While conducting the mission the RPIC detected what was believed to be an approaching aircraft. It was later identified to be a truck exiting I-95 with an engine brake. Shortly after the RPIC heard another possible aircraft approaching the area. The RPIC observed a helicopter travel over the bridge from south to north along the I-95 Corridor. The helicopter appeared to be at tree level. The RPIC had a clear view of the sky and area from the launch point. The helicopter did not become visible from the trees till it passed over the open area of bridge. At the time the UAS was to the west of I-95. The UAS was lowered and the mission was ended.The helicopter was not broadcasting ADSB on any commercially available applications. A FAA radio was being used to listen to BWI. The UAS was being operated at 100-120 feet which was the approximate altitude of the helicopter. The UAS was to the west of I-95 when the helicopter passed. The area was Class B (BWI) airspace and was approved for a Low Altitude Authorization and Notification Capability (LAANC) of 400 feet. The Helicopter was found to be operating in Helicopter Route 12 for the Baltimore Washington area. In this area the max ceiling is 500 feet. This directly conflicts with the LAANC grids for BWI along I-95 which are all 400 Feet. The Helicopter Route is not displayed on the standard FAA sectional charts such as skyvector or visualize it; or any UAS applications for LAANC or airspace awareness such as air aware. Additional training will be provided on helicopter routes and how to identify them. Additional operation in this area will also require a visual observer and notification to ATC of the operation in Helicopter Route 12.