Prior to the UAS flight, the airspace and weather were checked and preflight checklists were completed using a commercially available 3rd party mobile app. The app indicated BRD [airport] was nearby but did not show the Class E airspace boundary or indicate a LAANC approval was required.  

After the flight was completed, I, the UAS Operator, went to log the flight in the 3rd party app and the app stopped working and restarted. Once the app restarted it showed the UAS operation area was at the very edge of a 400 ft. LAANC required airspace. I assumed the flight area was in Class G airspace as no LAANC boundary was initially displayed in the 3rd party mobile app. I should have verified the airspace class prior to UAS operations and not relied solely on the mobile app to show airspace boundaries.  

I assumed the airport was a non 24 hour Class E airport that reverted to Class G during non scheduled times. While the airport is non 24 hour Class E airspace, the UAS flight was conducted when the Class E airspace was active. No manned aircraft were observed during the entire duration of the UAS flight activity. In the future I will not solely rely on the graphic depiction of Class E airspace on 3rd party apps to verify airspace prior to flights near airports. The active hours of the airspace will be verified prior to flights.