Narrative:

I am a licensed part 107 remote pilot. While preflight checking my aircraft I was approached by [a] police officer informing me that I was operating in a restricted area. I informed them that I was a part 107 operator in I had filed a flight plan earlier in the morning using laanc (via the airmap app). After this exchange; [the] officer spoke with [police] sgt. Whom informed me that [the] police department would have their helicopter operating in the area. I was requested at that time not to exceed 100 feet for my operation. This was in alignment with my prior FAA laanc flight plan. And as such I continued my flight confident in both my laanc approval; communication with local air traffic and while maintaining vlos (visual line of sight) on my suas (small unmanned aircraft system) at all times. After some time and completing my mission; I was approached by the officer who said that their helicopter reached out to the FAA and was unable to locate any flight plan filed. I continued to partner with [the] officer during this time and shared any part 107 license and my laanc approval through airmap (I have screenshots of this as well for review; if requested). He informed me that ZZZ tower or the FAA couldn't locate my flight plan. My concern rests in making sure other low flying aircraft in busy class B airspace (particularly police/medevac/etc) are able to get updated information on registered suas flights in the area during operations. I'm unsure of how the laanc system failed to provide this information through whatever channel the police used. I phoned ZZZ tower and spoke with an air traffic controller whom informed me that they have no way of reviewing laanc information after it is file. If this is the case; how can local law enforcement leverage reviewing the laanc system to validate legitimate authorized suas operations in the area.

Google
 

Original NASA ASRS Text

Title: Pilot of a SUAS (Small Unmanned Aircraft System) reported that while conducting a mission in controlled airspace; local law enforcement and ATC were unable to locate the filed flight plan.

Narrative: I am a licensed Part 107 remote pilot. While preflight checking my aircraft I was approached by [a] Police Officer informing me that I was operating in a restricted area. I informed them that I was a Part 107 operator in I had filed a flight plan earlier in the morning using LAANC (via the Airmap app). After this exchange; [the] officer spoke with [police] Sgt. whom informed me that [the] Police Department would have their helicopter operating in the area. I was requested at that time not to exceed 100 feet for my operation. This was in alignment with my prior FAA LAANC flight plan. And as such I continued my flight confident in both my LAANC approval; communication with local air traffic and while maintaining VLOS (Visual Line of Sight) on my SUAS (Small Unmanned Aircraft System) at all times. After some time and completing my mission; I was approached by the officer who said that their helicopter reached out to the FAA and was unable to locate any flight plan filed. I continued to partner with [the] officer during this time and shared any Part 107 license and my LAANC approval through Airmap (I have screenshots of this as well for review; if requested). He informed me that ZZZ Tower or the FAA couldn't locate my flight plan. My concern rests in making sure other low flying aircraft in busy Class B airspace (particularly police/MEDEVAC/etc) are able to get updated information on registered SUAS flights in the area during operations. I'm unsure of how the LAANC system failed to provide this information through whatever channel the police used. I phoned ZZZ Tower and spoke with an Air Traffic Controller whom informed me that they have no way of reviewing LAANC information after it is file. If this is the case; how can local law enforcement leverage reviewing the LAANC system to validate legitimate authorized SUAS operations in the area.

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.